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.
Use when a prospect writes back and the user needs the triage and the next draft.
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 prospect writes back. Start from the reply text or thread, plus the target-list row behind it.
Inbound replies jump the queue with a five-minute speed-to-lead target. Sort the reply into one bucket: positive (propose a time and book it only once the user says yes), curious (answer and ask), referral (thank and spawn a new research row for the named person), objection (answer once, then ask), or no (log it and close the row gracefully).
One line showing you heard them, the answer or the ask, and one dated next step. No recap of the pitch, no manufactured urgency, no pricing or discounts promised.
Replied with the date, meeting when booked, qualified when it earns a deal sheet, no or on hold when closed. Referrals spawn a fresh row at new with the source noted.
The bucket verdict, the unsent response draft, and the row updates. Log the reply and its bucket in the outreach log.
An ambiguous reply means you label it UNKNOWN, give the two most likely reads, and draft to the likelier one. An angry or opt-out reply means no draft at all — log it, suppress the row, and say so in one line.
Drafts only, nothing sends 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.