Prompt Library

Run a follow-up sequence that stops the moment they reply

Every day, Sai checks which contacts are due their next follow-up, drafts a touch that adds a new angle rather than repeating the last one, and stops the whole sequence the moment someone replies.

The PROMPTS
Copy prompt
Run my follow-up sequence from the Google Sheet at [sheet URL], tab [tab name]. Check it every day. The sheet has one row per contact with: Name, Company, Email, First Touch Date, Last Touch Date, Touch Number, Status. We sell [product, one line] to [audience], and the repetitive work it removes is [task]. The sequence is four touches: Touch 1 on day 0, Touch 2 after [3] days, Touch 3 after [8] days, Touch 4 after [16] days from the first touch. Each day, find every row where Status is Active and the gap since Last Touch Date has been reached. For each one, draft the next touch under [90] words. Each touch must add something the previous one did not — Touch 2 adds a concrete example for a team like theirs, Touch 3 opens a different use case entirely, Touch 4 closes the loop and makes not replying an easy answer. Never write "just bumping this", "circling back", or "following up on my last email". If you cannot find a genuinely new angle for a touch, skip that touch and say so rather than sending a reminder. Stop immediately when a contact replies, books a meeting, or asks to be removed: set Status to Replied, Meeting booked, or Opted out and draft nothing further. After Touch 4, set Status to Sequence complete. Write each draft into the row's Draft column with Status left at Draft and send nothing. Tell me each day who is due, who was skipped, and who replied.
Run this TaskView Demo

Platforms this prompt works across

Most deals that die in outbound die in the gap between the first email and the second. The first one is written carefully; the follow-up is written at 6pm on a Thursday, says "just circling back", and teaches the recipient that ignoring you costs nothing. The sequence is not the problem — sending a reminder instead of a reason is. And the part that fails in practice is not the writing at all, it is remembering who is due, on which day, and stopping the whole thing the moment someone replies.

What this recurring task does

Sai checks your sheet every day, finds the contacts whose next touch is due, and drafts it. Each touch is written to add something the previous one did not, based on the company's own public information rather than a template. The moment a contact replies, books, or opts out, their sequence ends and no further drafts are written. Nothing is sent without your approval.

What a four-touch sequence actually contains

Spacing matters less than substance. A touch that carries a new reason to reply can land on day three; a touch that carries nothing is unwelcome on any day.

★ A FOUR-TOUCH SEQUENCE THAT ADDS SOMETHING EACH TIME

TouchWhen it goesWhat it adds that the last one did not
Touch 1Day 0The original reason for writing, tied to something that changed at their company
Touch 2Day 3–4One concrete example of the same team shape doing the same repetitive task
Touch 3Day 8–10A different angle entirely — a second use case, not the first one restated
Touch 4Day 16–18A short close-the-loop note that makes not replying a comfortable answer
Stop earlyAny reply, meeting booked, or opt-outThe sequence ends immediately and the row is marked Replied or Opted out
Never sentNo new angle available for that touchThe touch is skipped rather than padded with a bump message

What lands in your sheet

The columns you already have plus Touch Number, Last Touch Date, Draft, and Status. Status is the control surface: Active, Replied, Meeting booked, Opted out, Sequence complete, and Paused. Setting a row to Paused stops it without ending it, which is the column most sequence tools do not give you — it is how you handle "not this quarter" without losing the thread.

What happens on the second run

Only rows that are Active and due are picked up, so a daily run is cheap and nothing is drafted twice. Anything marked Replied or Opted out is permanently excluded, including in future sequences, so an opt-out is honoured once rather than every time. Contacts you pause stay paused until you set them back to Active, and Touch Number always reflects what was actually sent, not what was scheduled.

Where this fits with the rest of your outbound

This task owns everything after the first email. The first one comes from cold emails to founders who just raised, the contacts come from your weekly prospect list, and who is worth a four-touch sequence at all is decided by your weighted lead scoring rubric — C-tier leads rarely deserve four touches. When someone replies on LinkedIn instead of email, that thread is picked up by your daily DM pass. Every sequence you run must honour the CAN-SPAM opt-out requirements, which is why Opted out is a terminal status here.

Stop doing repetitive tasks. Let Sai handle them for you.

Sai is your AI computer use agent — it operates your apps, automates your workflows, and gets work done while you focus on what matters.

Try Sai