Confirmations, reminders, and calendar invites all used to depend on someone remembering. Now every booking gets all three, timed right and sent from the rep's own inbox, with no one lifting a finger.
/ The problem
Every booked call depended on a salesperson remembering to send three things: a confirmation, personal enough to read like a person wrote it; a reminder, right before the call; and a nudge to accept the calendar invite.
Each one had to land at the right moment. Across a team running dozens of calls a day, that isn't something that happens every time.
What it cost was people not showing up, because nobody nudged them. What made it hard to fix was that nobody could see it. There was no count of how many booked calls quietly fell apart, never confirmed, never rescheduled.
/ What we did
The moment someone books, the system picks it up and works out whether this is a call worth confirming at all. Existing clients, bookings from countries the service doesn't cover, and calls already being handled elsewhere are set aside.
For everyone else, it writes a confirmation using that person's own answers from the booking form, in their salesperson's voice, and holds it until about a day before the call, staying out of the evening. A short reminder follows just before the call, then a nudge to accept the invite. All of it goes from the salesperson's own inbox.
The system doesn't do the sending. It writes the draft into the customer records and marks it ready, and the tool the team already uses sends it from there.
A check each day sweeps up anything the live handoff missed, clears out calls the salesperson never accepted and offers those people a new time instead, and posts a short summary to the team's chat.
Automation, no interface · one booking, start to finish
confirming?
a day out
just before
Hey ,
You mentioned . That's exactly what we'll dig into tomorrow.
written from their own answers · sent from the rep's inbox · held out of the evening
/ What changed
Nobody sends any of it by hand, and no one's confirmation depends on how busy their salesperson was that afternoon.
People who reply to their confirmation show up about 60% of the time. People who never engage with it at all show up about 30% of the time. That gap doesn't prove the email made people show up. People who are already more interested are also more likely to reply, so some of that gap was always going to be there. But a reply is still worth acting on, and silence is still worth a nudge.
The calendar stopped filling up with calls nobody was going to run, because the ones the salesperson never accepted get cleared and offered a new time instead of sitting there.
The daily sweep produced something nobody expected: a running count of how many booked calls actually survive to happen, and why the rest didn't. That number had never existed.
/ Decisions worth explaining
Before touching an unaccepted call, the system checks whether that person has emailed in. If they have, it backs off and leaves it for a human.
If we can't tell someone's country, or can't tell whether they're already a client, we send the confirmation anyway. Skipping a real lead by mistake costs far more than sending one extra email. But the check that stops a booking from being confirmed twice works the other way: if it's unsure, it blocks the message instead.
It writes the draft and flips a switch; the existing system owns the actual sending and which inbox it comes from. A bug in the writing step can't mail anybody.
More than a day passes between a booking and its first email. That wait is held in something built to survive updates and outages, not a scheduled job that has to work out where it left off.