Cutting no-shows and rebooking
The records exist and the sending does not. That distinction decides whether this is useful to you today, so it is the first thing on the page.
- Meeting records today
- Automatic reminders on the roadmap
- Outcome recorded either way
The short answer
- Available today: bookings arrive from Calendly, become meeting records, and can be marked with an outcome including a no-show. A task or an email cadence can follow, sent by a person.
- On the roadmap: reminders that send themselves at 24 hours and 2 hours, a reschedule link, and no-show recovery that fires without anyone remembering.
- The measurement works now even though the sending does not. Once no-shows are recorded as outcomes rather than as gaps in a calendar, you can see the rate before you spend anything on fixing it.
Trigger to logged
Which parts run and which parts wait.
- 1
Trigger: a booking is made
Calendly's webhook creates a meeting and matches or creates the contact, with the source recorded. Available today, with a reconcile job for failed deliveries.
- 2
The reminder window opens
Twenty-four hours out, then two hours out. Sending those automatically by SMS and email is on the roadmap; today it is a task somebody works.
- 3
The human sees the day's list
Meetings with their contacts and any notes. meeting_list returns the same rows to an agent under a scoped token.
- 4
The meeting happens, or it does not
The outcome is recorded either way. meeting_outcomes reads the rates back, which is the number worth arguing about.
- 5
Recovery starts
A no-show can enter a follow-up cadence over email today. Automatic recovery with a reschedule link is on the roadmap.
- 6
What gets logged
The booking and its source, the outcome, and every touch afterwards on the contact timeline. That history is what makes a rate believable.
What gets configured
Half of this is a plan, and the column says which half.
| Object | What you set | Status |
|---|---|---|
| Calendly webhook | Booking created, cancelled and rescheduled events | Available |
| Meeting record | Attendee, time, source, notes | Available |
| Meeting outcome | Held, cancelled or no-show | Available |
| Follow-up cadence | Email steps after a no-show | Available |
| Reminder at 24 hours and 2 hours | The message and the channel | On the roadmap |
| Reschedule link in the reminder | A one-click rebooking path | On the roadmap |
| Automatic no-show recovery | Fires without a person remembering | On the roadmap |
| Round-robin pools | Who a booking is assigned to | On the roadmap |
Where it stops and a human starts
Today it stops at sending. Somebody has to send the reminder, and if that person is busy the reminder does not go. Being clear about that is more useful than a page implying the problem is already solved.
When reminders ship they are planned to stop early too. A reminder confirms or reschedules; it does not renegotiate the meeting. Any message to a consumer mobile carries consent obligations under the TCPA that belong to you, and this page is not legal advice.
What is genuinely available now is honesty about the rate. Recording outcomes turns no-shows into a measured number rather than a shared impression, and that alone often changes what a team does about them.
Questions
- Do reminders send automatically today?
- No. Meetings and reminder records exist; sending them by SMS and email is on the roadmap along with the rest of the phone pack.
- Can I run recovery over email in the meantime?
- Yes. Email cadences work today, so a no-show can enter a short sequence. What is missing is the automatic trigger and the SMS channel.
- What is a good no-show rate?
- It varies enough by industry that a single benchmark would mislead you. Measure your own for a month, then decide whether the gap is worth spending on.