Booking check-in: catch the people who meant to book and didn't
Someone tells your setter they're interested. Your setter sends the booking link. Then nothing.
Most of the time that isn't a no. They opened the link, got distracted, put the phone down, and the moment passed. You never find out, because a booking shows up in your calendar and a non-booking shows up nowhere at all.
The booking check-in closes that gap. A few minutes after your setter sends the link, it circles back with one short question: did you manage to get a time booked in?
01Turning it on
Automations → Follow-ups → Check in after the booking link.
Pick how long to wait: 15, 20, 30 or 60 minutes. Off is the default, so nothing changes until you choose a number.
Twenty minutes is a good starting point. It's long enough that someone who's booking right now isn't interrupted mid-form, and short enough that you're still in their head.
Why 15 minutes is the shortest option
Follow-ups run on a cycle that ticks every few minutes. If we let you set five minutes, the message would still land closer to ten and the number on your screen would be a lie. Fifteen is the shortest delay we can actually keep.
02What they get
One line, in your voice, with tappable buttons:
did you manage to grab a time?
>
[ Booked it ] [ Not yet ] [ Resend the link ]
A tap is just a reply. Your setter reads it and carries on the conversation normally, so "Not yet" turns into a real exchange about what got in the way rather than a dead end. Nobody is forced to use the buttons; typing works exactly as it always did.
03Who actually gets asked
This is deliberately narrow. It only goes to someone who:
never chased this way. A check-in belongs in a conversation, not on top of a cold opener.
already mid-conversation and won't talk over itself.
- has been talking to you. People who never replied to a first message are
- went quiet after getting the link. If they replied to it, your setter is
- hasn't booked, opted out, or been taken over by you.
- hasn't already been asked. Once per person, ever.
It also never fires during quiet hours. A 20-minute check-in that arrives at 7am the next morning isn't a check-in, so we skip it rather than delay it.
04What it costs
The check-in uses one of the two automated messages each lead can receive per day, the same budget your normal follow-ups draw from. It does not use up one of the three follow-up nudges, so a lead who doesn't book still gets the full follow-up sequence afterwards.
05Getting the most out of it
check-in triggers off that link going out, whether your setter sent it during a conversation or a flow sent it.
people who did book can still get asked. See Confirming booked calls. This is the single biggest thing you can do to make the check-in feel sharp instead of clumsy.
("no times that work", "couldn't find my timezone"), that's a calendar problem, not a follow-up problem.
- Make sure your booking link is the one in your setter's settings. The
- Wire up your booked-calls webhook. Without it we can't tell who booked, so
- Watch what "Not yet" tells you. If the same reason keeps coming back