WhatsApp Meeting Confirmation and No-Show Recovery

The workflow

Play 18

WhatsApp Meeting Confirmation and No-Show Recovery

1A meeting gets booked

Meeting booked on your calendarPhone field optional

Gate1

They gave a mobile and opted in

The booking form asks for a number for reminders only.

× No opt-inemail reminders only

2Pick the channel they actually read

WhatsAppMost countries

An approved reminder template from the business number.

Send

WhatsAppTwilio

SMSUS and Canada

A plain text where WhatsApp is not the default app.

Send

Twilio

3Remind with something useful

ConfirmationAt booking

Time in their time zone, the link, and one line on what the call will cover.

Reminder1 hour before

One short message. A reply of 1 confirms, 2 asks to move it.

Day of

4Recover the no-show the same day

“Looks like today did not work. Want to grab one of these two times instead?”

Rebooked

New time goes straight onto the calendar and the CRM.

Book

Cal.com

Log

HubSpot

No reply in 48 hours

One email from the host, then the deal waits for a new signal.

Send

Gmail

Fewer empty calendar slots, more meetings held

The stackCal.comWhatsAppTwilioHubSpotGmail

Oriel · GTM plays library

Open full size

The diagram as text

1. 1

   A meeting gets booked

   Meeting booked on your calendar (phone field optional): Tool: Cal.com.

   Gate 1: They gave a mobile and opted in. The booking form asks for a number for reminders only. Rejected: No opt-in, email reminders only. Tools: Cal.com.

2. 2

   Pick the channel they actually read

   WhatsApp (most countries): An approved reminder template from the business number. Send: WhatsApp and Twilio. Tool: WhatsApp.

   SMS (us and canada): A plain text where WhatsApp is not the default app. Send: Twilio. Tool: Twilio.

3. 3

   Remind with something useful

   Confirmation (at booking): Time in their time zone, the link, and one line on what the call will cover..

   Reminder (1 hour before): One short message. A reply of 1 confirms, 2 asks to move it..

   Labeled connection: Day of.

4. 4

   Recover the no-show the same day

   “Looks like today did not work. Want to grab one of these two times instead?”: Tool: WhatsApp.

   Rebooked: New time goes straight onto the calendar and the CRM. Book: Cal.com. Log: HubSpot.

   No reply in 48 hours: One email from the host, then the deal waits for a new signal. Send: Gmail.

   Outcome: Fewer empty calendar slots, more meetings held. Tools: HubSpot.

The stack: Cal.com, WhatsApp, Twilio, HubSpot and Gmail.

Open the diagram full size (1180 px wide)

The play in four steps

1. 01

   Step 1: Ask for a number on the booking form

   A reminder on the app people actually check does more for show rate than any email.

   • Add an optional mobile field to the Cal.com booking form, labelled "for reminders about this meeting".
   • Store the opt-in with the booking. No opt-in means email reminders only.
   • Never reuse that number for marketing. It was given for this meeting.
2. 02

   Step 2: Pick the channel they read

   WhatsApp is the default in most of the world, SMS still wins in the US and Canada.

   • Route by country code: WhatsApp through the Business API (via Twilio), SMS for US and Canadian numbers.
   • Get the reminder and recovery templates approved on WhatsApp before launch.
   • Send from a named person, never a no-reply brand.
3. 03

   Step 3: Remind with something useful

   A reminder that adds context gets read. One that only repeats the time gets muted.

   • At booking: the time in their time zone, the meeting link and one line on what will be covered.
   • One hour before: a single short message. Reply 1 to confirm, 2 to move it.
   • A reply of 2 sends two new times automatically.
4. 04

   Step 4: Recover no-shows the same day

   Most no-shows are a clash, not a no. A same-day offer to rebook recovers many of them.

   • Fifteen minutes after a missed start, send one friendly message with two new times.
   • Rebooked: the new time goes onto the calendar and the HubSpot deal.
   • No reply in 48 hours: one email from the host, then stop.
   • Report show rate weekly by channel and by meeting source.

Tools used

The five tools this play names. Each links to the other plays that use it.

Cal.comWhatsAppTwilioHubSpotGmail

Related plays

Play 19

Meeting Prep and Follow-Up

1Pull tomorrow's meetings

Booked meetings with an external attendeeDaily run

2Research the company, the people, the history

Company

NewsHiringFunding

Searched inside an absolute date window.

CRM history

Deal stageOwnerLast emails

Falls back to attendee email when no deal is linked.

Past calls

NotesOpen items

What they already said, so nobody asks twice.

3Around the call

The briefDay before

Who is coming, what changed, what is still open, a suggested agenda.

Write

Claude

Post

Slack

Save

HubSpotlink on the deal

Reminder to the attendeeDay of

A short note with the time and the link, sent to the number they gave when booking.

Text

WhatsAppTwiliobooked meetings only

The transcriptAfter

A webhook fires when processing ends. Poll until it has sentences.

Fetch

Fathom

The call

4One meeting, one record

Gate1

Same meeting id

A repeat webhook for one transcript is dropped.

× Repeat webhook

Gate2

Same client, title and date

Several recorders in one call make several transcripts with different ids.

× Duplicate recording

5Recap, route, follow up

Recap

Decisions and open questions, posted to the account channel.

Post

Slack

Action items

Each one goes to the person who committed to it, else the owner.

Extract

Claude

CRM and follow-up

Next step on the deal. The email is drafted, a human sends it.

Log

HubSpot

Draft

Gmail

Text

WhatsAppexisting chats only

Every call prepped the day before, followed up the same day

The stackGoogle CalendarExaHubSpotFathomClaudeSlackWhatsAppTwilioGmail

Oriel · GTM plays library

Play 19Inbound · Outbound

Meeting Prep and Follow-Up

6 steps · Email, CRM, WhatsApp, SMS

+3 more

Play 13

Speed-to-Lead with AI Voice and SMS

1Catch the request the second it lands

Demo or contact form submittedConsent box ticked

What the form already tells you

NameWork emailMobileCompanyWhat they asked for

The consent line on the form covers calls and texts about this request, and nothing else.

2Qualify before anyone dials

Enrich the company and the person

HeadcountIndustryRoleSeniority

With

ClayApollo

Verify

Twilioline type lookup, mobile or landline

Gate1

Inside the ICP, real company, real person

Students, vendors and competitors are filtered out here.

× Not a fitpolite email, no call

3Respond inside five minutes

AI voice callMinute 1

Confirms the request, asks two qualifying questions and offers two times from the live calendar.

Call

Retell AI

Book

Cal.com

SMS follow-upMinute 3

One plain text from a named person with a booking link. No marketing copy.

Send

Twilio

If no answer

4Hand the conversation to a human

Booked

The call transcript and answers go onto the contact before the meeting.

Log

HubSpot

Alert

Slack

Asked for a person

The owner gets a Slack alert and calls back the same hour.

Alert

Slack

Call

Nooks

No response

A short email sequence takes over. No more calls.

Send

Smartlead

Every inbound request answered in minutes

The stackHubSpotClaudeClayApolloTwilioRetell AICal.comSlackNooksSmartlead

Oriel · GTM plays library

Play 13Inbound

Speed-to-Lead with AI Voice and SMS

5 steps · Website, Call, SMS, Email, CRM

+4 more

Play 15

Meeting Form Orchestration

1Catch the request the second it is sent

Meeting form submitted on the website

Webhook into ClayPer submission

Full nameWork emailCompanyDomain

Four fields on the form, no more. Every extra field costs you submissions, and enrichment fills the rest.

2Fill the gaps, then check they are still true

Enrich what the form skipped

LinkedIn URLJob titleSeniorityFirmographics

With

ClayBetterContact

Freshness checkBefore any send

Confirm the title on LinkedIn matches the form and re-verify the email. A typo in the address is the most common silent failure.

Job

LinkedIn

Verify

ZeroBounce

3Ask HubSpot what it already knows

Company lookupBy domain

Is this account already in the CRM, and does it have an owner?

Contact lookupBy email

Is this person already a contact, or in an open deal?

Lookup resultPath

Company exists in HubSpot→Persona check

Company not found→ICP check, then create records

4Qualify each path its own way

Known accountPersona fit

TitleDepartmentSeniority

The account is already approved. The only question is whether this person is worth a meeting.

Check

Clay

New accountICP fit

IndustrySizeTech stackMarket

Unknown company. Claude scores the fit in Clay, then the company and contact are created.

Score

ClayClaude

Create

HubSpot

Not a fit: a polite reply with a useful resource, no rep time spent

Owner found or assigned, rep alerted in SlackWith context

5Follow up on more than one channel

EmailAuto

Confirms the request and offers times, written from the rep who owns the account.

Send

Smartlead

LinkedInAuto

A connection request from the same rep, so the name is familiar before the call.

Send

HeyReach

WhatsApp confirmationConsent

Only when the form had an opt-in box ticked. A short note with the booking link.

Send

WhatsApp

Every request routed to its owner

The stackTallyClayBetterContactLinkedInZeroBounceHubSpotClaudeSlackSmartleadHeyReachWhatsApp

Oriel · GTM plays library

Play 15Inbound · Outbound

Meeting Form Orchestration

8 steps · Website, Email, LinkedIn, CRM, WhatsApp

+5 more

All GTM plays