Before the day starts, the system finds the people who've gone quiet and writes each one a personal email about their last conversation.
/ The problem
After a call that doesn't close, people go cold in two different ways. Some go quiet for weeks with no clear next step. Others stay interested but never quite book the next call.
Following up well means sitting down, remembering that exact conversation, and writing something that doesn't read like a form email. Across a whole team and hundreds of people, that doesn't happen. People who were genuinely interested just fade out, because nobody got back to them with anything worth reading.
/ What we did
Each weekday morning, before anyone is at their desk, the system finds the people who've gone quiet, and separately the ones still warm but not booked. It finds the recording of their original call and reads what was said, writes one short email about something real from that conversation, a goal they mentioned or the thing they're stuck on, and signs it from their salesperson to send from that person's inbox.
Anyone already paying for a service is skipped, and so is anyone who already has an email waiting.
A second job runs twice a day, every day including weekends, looking for replies. The moment someone answers or books, they come out of the sequence.
A summary posts to the team's chat every morning: who was added, who was skipped and why, and whether anything failed.
Automation, no interface · every weekday morning
went quiet
call back
one email
the records
Hey , you said the hard part wasn't , it was . Did the framing we sketched hold up?
written from their own call, not a template
/ What changed
Follow-up that used to depend on someone remembering now happens every weekday, for everyone who qualifies.
Two tracks run at the same time, at different speeds: a slower one for people who went fully quiet, a faster one for people still warm.
Replies are caught twice a day including weekends, so someone who answers on a Saturday isn't chased again on Monday.
/ Decisions worth explaining
This system only writes, marking each draft ready in the customer records. The team's existing tool owns the sending, the timing, and the inbox it goes from. So a bug here can draft a bad email, but it can't actually mail one.
Scanning for replies is cheap; reading a call recording and drafting from it is not. Splitting them means the cheap half can run often enough to matter. Before that, a weekend reply sat unnoticed until Monday.
Someone left out for being an active client is marked differently from someone left out for having no call recording. Nobody gets looked at twice, and anyone can see exactly why a person wasn't contacted.
If someone gets flagged for follow-up again after already being added once, a second check catches it. Nobody receives the same email twice because of a stray click.