Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.