Use when a sales call wrapped up with no firm next step, a live deal has stopped answering, or a won deal has to pass cleanly to closing or implementation.
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 when a call ended with nothing anyone could put in a calendar, a moving deal went silent, or a signed deal must land with the team that closes or implements it. Work from how the last call ended, what both sides agreed, the deal sheet, and who receives any handoff.
A real next step passes four tests: it has a date, it has a time, it sits on both calendars, and the buyer has homework due before it. Name every test it fails. Then find the point in the transcript where the rep should have locked it in, quote it, and write the one or two sentences that would have closed it there, finishing on a specific ask.
Lead with a subject line. The body is four to six sentences, in this order: the problem as the buyer described it, in their own words; the agreement you reached; your deliverables and when they land; the buyer's deliverables; and a single ask pinned to a day and an hour. Keep your pitch out, and include nothing the buyer did not actually agree to; an invented deadline costs more trust than a thin email.
For a deal already gone quiet, write a short re-open instead: the last thing they said mattered, one fresh reason tied to their business to talk now, and one proposed date.
Buyer outcome, key contacts with roles, what was promised (quoted, never paraphrased into more), open loops with owners and dates, and the top risk. Reconcile every open commitment across the deal sheet, mail, and notes so no promise leaks. Show the draft or packet in chat, then save it dated.
The four-test verdict with the better line, plus whichever the moment needs: the follow-up, the re-open, or the handoff packet.
No agreement at all means you open by saying so, then write the re-open instead of recapping a thread that never existed. A handoff with open loops nobody owns means you name the gaps and ask who takes each before the packet ships.
Drafts only, nothing sends and no handoff ships without your explicit yes.
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.
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.
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.