Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Use this to prepare a receivables review and message drafts. The owner approves all customer contact.
For each open invoice, collect the invoice record, customer, currency, issued
date, due date, original amount, credits, payments, open balance, last contact,
dispute status, and account owner. Check payment records through the stated
cutoff time. If the due date or balance cannot be proved, mark the item status unconfirmed rather than overdue.
Calculate days past due from the supplied due date and cutoff date. Keep part-payments, credits, disputes, and promised payment dates visible.
Group items as:
Within each group, sort by age and open balance, then note any named customer or contract rule that changes the handling. Do not invent a credit policy.
Each draft should state the invoice number, issue and due dates, open balance, currency, and the requested next step. Keep the tone calm. Ask whether payment has been made or whether a record is missing. For a dispute, acknowledge the stated issue and route it to the owner; do not argue the contract.
Prepare a contact log row with draft stage, evidence cutoff, owner, approval state, and next review date. Drafts must not claim a late fee, service stop, collection action, or legal consequence unless an approved policy and owner instruction support it.
Never send a message, call a customer, apply a fee, stop service, change an invoice, or threaten collection. Never expose another customer's data. Route disputes, hardship, insolvency, legal threats, sanctions, and material customer risk to the finance owner or counsel.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write ad variants that each test one idea, within platform limits and supported claims.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.