Use when a sent opener got no reply and the row needs its next touch in the sequence.
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.
Run this when a sent opener got no reply and the row needs its next touch. The row must be marked sent by the user; if it is not, ask rather than treating the opener as delivered.
The target-list row, the earlier touches with dates, and any new public fact about the person or company since.
Eight touches, multi-channel, over three to four weeks, front-loaded: days 1, 3, 5, 7, 10, then spaced a week apart. Never stop before attempt five. Rotate the channel per touch — email, call, social — with a new angle on the same pain each time. Touch two lowers the door with a smaller ask; middle touches add a useful link or a referral ask; the last touch closes clean with a graceful no-pressure goodbye, then the row recycles to the nurture pool for a 60-to-90-day revisit. Any reply at any point ends the sequence.
Say the send date on each draft. Each touch holds the no-invented-facts rule and the user's voice. Each touch is shorter than the last; late touches run two sentences. No emoji, no exclamation points, none of the banned openers.
Show the draft in chat with one line on which touch it is and why this angle. Mark the row with next_step, record the draft as pending, and save. Leave last_touch_on alone and log no outreach touch until the user confirms the send — writing either from an unsent draft puts false state in the CRM and shifts every later cadence date.
The unsent follow-up draft with its touch number, plus the row update.
Nothing new to say: say so and suggest waiting for a trigger instead of burning the row. A reply that arrived mid-sequence: stop and switch to Handle a reply.
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.