A follow-up assistant that remembers what you’re waiting on
An AI follow-up assistant tracks the messages you’ve sent that need a reply and drafts the next nudge when a thread goes quiet past the window you set. It covers the gap between sending something and remembering to check back, which is where most proposals, quotes and requests die.
You tell your operator what to track once. It keeps a running list and checks each thread against its deadline every day.
What you hand off
A follow-up instruction usually covers:
- Specific threads you flag, or a standing category like every proposal, quote or introduction you send
- A follow-up window per thread, such as 5 business days for a proposal or 2 days for a time-sensitive ask
- A short nudge that references the original message
- A cap on how many times it follows up before handing the thread back to you
- Automatic removal from tracking once a reply comes in
- A running status list of everything still open
A follow-up, worked through
Say Sam sends a proposal to Acme Inc on a Monday and tells their operator: “Track this, and if I haven’t heard back in 5 business days, follow up once.”
The operator logs the thread and checks it daily. It notes the send date, the follow-up window and a short summary of the proposal, so it doesn’t re-read the whole thread on every check. By the following Monday there is still no reply, so it drafts a two-line note in Sam’s usual tone that references the proposal and asks whether Acme had a chance to look at it. The draft waits for Sam’s approval, since it goes out in Sam’s name. Sam reviews it on their phone at 9 a.m., approves it without changes, and it sends.
Acme replies three days later with a question about pricing. The reply takes the thread off the tracked list, and it moves to Sam’s regular inbox handling. Had Acme stayed silent, the operator would have handed the thread back to Sam after the one follow-up, with no second nudge.
The same week, Sam has a quote out to Thornquist Ventures and an introduction request waiting on a contact at Brackenwold Studio. Both run under the same standing rule, each on its own clock. Sam’s morning brief lists all three: one closed by Acme’s reply, one due for its follow-up in two days, one still inside its window.
What stays with you
Tracking a thread, checking its deadline and drafting the next message need no sign-off, since none of it changes anything outside your operator’s workspace. Sending the follow-up waits for you by default, because it puts a message in front of someone else in your name.
If you follow up on the same thing often, like weekly check-ins with one client, you can pre-approve that follow-up so it sends without a review. A pre-approved rule covers only the case you named, and you can set it back to “always ask” at any time.
You also decide what counts as a reply. A one-line “got it, will look this week” from Acme counts and takes the thread off the list, since your operator checks whether the person responded, not whether the answer was good enough.
Setting it up
- Connect the channel the threads live in, such as email or a messaging channel.
- Tell it what to track: specific threads, or a standing rule like every proposal or quote you send.
- Set the follow-up window and how many nudges to send before it hands a thread back to you.
- Set your approval rules: each follow-up waits for your OK, or a specific repeatable case is pre-approved.
If the second nudge should sound different from the first, say more direct, put that in the standing order and your operator drafts it that way.