Who owes whom
It knows whether the last move was yours or theirs, so it never chases someone who is waiting on you.
How to Automate Email Follow-Ups Without Being Annoying
How-to — — by Mahmoud Zalt
Automate email follow-ups with an AI Employee that watches threads for silence, drafts a specific nudge, and stops the moment someone replies.
Most deals do not die from a no. They die from silence. You send the quote, they say let me check with the team, and then nothing. Nine days later you think about it in the shower, decide it is now too late to chase, and quietly let it go. That thread was worth money and it died of neglect, not rejection.
Following up is not hard work, it is remembering work, and remembering across forty open threads is the thing humans are worst at. On **Sistava** you hire an AI Employee that holds all of them at once. It knows what you asked, when you asked it, what they said back, and how long the silence has run. When a thread crosses your line, it writes the nudge and puts it in front of you.
At a Glance
- Every thread
- Tracked for silence, not just the ones you remember
- Stops on reply
- The chase ends the second they respond
- 50/mo
- Entry plan with credits bundled in
- You approve
- Anything about price or contracts waits for you
What does automating follow-ups actually mean?
It means the tracking is automatic and the message is specific. The AI Employee keeps a live list of every thread where the ball is in someone else's court, counts the days of silence on each, and when one passes your threshold it writes a follow up that mentions the actual subject: the quote number, the file you sent, the question they never answered.
It does not mean a drip sequence. A sequence fires message two on day three whether or not message one landed badly, and it will happily send a checking in note to someone who replied an hour ago on a different thread. This is the opposite: one thread, one context, one nudge, and it stops the moment there is a response anywhere in the conversation.
Benefits
The age of the silence
Days since the last reply on each open thread, measured per thread rather than per contact.
What was being discussed
The quote, the file, the unanswered question, so the nudge is specific rather than a generic bump.
When to stop
A cap you set. After the last nudge it marks the thread closed and stops rather than nagging forever.
How does it know a thread has actually gone quiet?
It reads the last message and works out whose turn it is. If the last thing in the thread is you asking a question, sending a proposal, or promising to hear back, the ball is theirs and the clock starts. If the last thing is them asking you something, the thread is on your list to answer, not on the chase list.
That distinction sounds small and it is the whole thing. A calendar reminder cannot make it, which is why reminder based follow up systems constantly nudge people who are politely waiting on you. Reading the thread is what stops the embarrassing chase.
It also spots the soft close. When someone says circle back after the holidays or let me raise it at Monday's meeting, that is a date hiding in a sentence. The AI Employee picks it up and starts the clock from there rather than from the message date, so the nudge lands when they said it would be useful.
How many follow-ups should you send, and how far apart?
Three is the number most people settle on, spaced roughly three days, then a week, then two weeks. The first is a light nudge, the second adds something useful, and the third is a clean close: I will assume the timing is not right, happy to pick this up whenever. That last one gets more replies than the two before it combined, because it is easy to answer.
The cadence should differ by thread type, and you say so in plain English. A customer with a broken product gets chased in a day. A quote gets the three step rhythm. An introduction from someone you barely know gets one nudge and then nothing, because a second one from a stranger is just noise.
| Thread type | First nudge | How many total | Auto send or draft |
|---|---|---|---|
| Quote or proposal sent | 3 days | 3 | Draft only, you approve |
| Customer waiting on a fix | 1 day | Until resolved | Auto send once proven |
| Scheduling a meeting | 2 days | 2 | Auto send once proven |
| Invoice unpaid | On due date | 3, then flag to you | Draft only, you approve |
| Cold introduction | 5 days | 1 | Draft only, you approve |
| Waiting on a document | 3 days | 3 | Auto send once proven |
What does this look like in a real business?
Kwame installs audio visual systems for offices and meeting rooms. He sends about fifteen quotes a week, each between four and thirty thousand euros. His close rate was fine when he chased and terrible when he was on site, which was most of the time. He estimated he was losing four or five live deals a month to nothing more than his own silence.
He hired an AI Employee and gave it one instruction set: track every thread where I sent a quote, nudge at three days, seven days, and twenty one days, stop the moment they reply anything at all, and never mention the price or offer a discount. All three nudges came to him as drafts.
The drafts were specific, which was the part that surprised him. Not a bump, but a line referencing the room count and the ceiling speaker option they had asked about. He approved most of them in a second each from his phone between jobs.
Over three months, 61 quotes went quiet. The three step chase brought 23 of them back into conversation and 9 of those closed. Two of the nine had gone silent for over four weeks and he would never have chased them himself. He also got a handful of clear noes, which he counted as a win, because a no lets him stop thinking about it.
How do you set it up?
Under an hour, and there is no sequence builder involved. You hire the role, connect your mail, describe which threads to watch and how patient to be, and decide what it may never say. Most people get this wrong in one direction only: they set the cadence too aggressive on the first attempt and then relax it after week one.
Five steps to follow-ups that happen without you
- Hire the inbox AI Employee — Pick the pre built inbox role in your workspace. No sequence builder, no conditions, no scripting.
- Connect your email — Authorize your account in a couple of clicks. Access is scoped to your workspace and you can narrow or revoke it any time.
- Say which threads to watch — Quotes, invoices, documents you are waiting on, meetings you are trying to book. Plain sentences, not filters.
- Set the rhythm and the stop — How many days before the first nudge, how many nudges total, and when to give up and close the thread quietly.
- Name what it may never say — No discounting, no new deadlines, no commitments on your behalf. Price and contract nudges stay on draft only.
Comparison
| Dimension | Traditional | With Sista |
|---|---|---|
| What triggers the next message | A timer, regardless of what happened | Reading the thread to see whose turn it is |
| What the message says | A template with a first name merged in | The actual quote, file, or question at issue |
| Someone replies elsewhere | The sequence keeps firing anyway | It stops immediately across the conversation |
| Soft dates like after the holidays | Ignored, it only knows the calendar you set | Picked out of the sentence and used as the clock |
| Risk of embarrassment | High, everyone has sent the wrong bump | Low, and sensitive threads wait for your approval |
What should you never hand over?
Never let it negotiate. A follow up may remind, summarize, and ask, but it must not offer a discount, invent a deadline, or commit you to anything. Say that explicitly at setup. The same goes for chasing anyone who has already been difficult: those threads should come to you as a draft with the history, because the right move there is often to pick up the phone instead.
And be honest that some threads deserve to die. A follow up cannot rescue a deal that was never real, and a fourth nudge to someone who has ignored three is not persistence, it is a reputation cost. The stop rule matters more than the cadence. Set it, and let the quiet ones go.
Frequently asked questions
FAQ
How many follow-up emails should I send before giving up?
Three is the usual sweet spot for a quote or a proposal, spaced about three days, a week, then two weeks apart. The third should be a clean close rather than another chase, because a message that is easy to answer with one line gets far more replies than another nudge.
Will it keep chasing someone who already replied?
No. Any reply anywhere in the conversation stops the chase immediately. This is the main failure of timer based sequences and the reason the AI Employee reads the thread rather than counting days from a send date.
Can it follow up on unpaid invoices?
Yes, and money threads should stay on draft only. It tracks the due date, drafts the reminder with the invoice number and amount, and hands it to you. You press send, because the tone of a payment chase is a business decision, not a template.
Does it work on old threads that already went cold?
Yes. On the first sweep it finds every conversation where someone owes you a reply, including ones months old, and gives you a list. You decide which are worth reviving. That first list is usually where the surprising wins are.
What if someone says they will get back to me next quarter?
It reads that as a date and starts the clock from there instead of nudging in three days. Soft commitments hidden in sentences are exactly the thing calendars miss and a reader catches.
How much does automated follow-up cost?
Sistava starts at 50 per month with credits bundled into the plan, covering an AI Employee that watches your threads continuously. There is no per contact or per sequence charge, so tracking more threads does not raise the price.
The whole value of automated follow-ups sits in one boring fact: the messages that make you money are usually the ones you forgot to send. Track every thread where the ball is theirs, nudge with something specific rather than a bump, stop the second they reply, set a hard limit so you never become the person who sends a fourth one, and keep price and contract chases under your own hand.