A candidate who misses Discovery Day has not walked away. They showed up through your application process, reviewed the FDD, completed franchisee validation calls, and committed to a date. That is not someone who changed their mind — that is someone who had a morning go sideways. How you respond in the next 90 minutes determines whether you reschedule or start over.
Most franchise development teams handle this the same way: a rep eventually notices the candidate never joined, sends a quick email, and hopes for the best. By the time that happens, the candidate has moved on mentally. The window to re-engage at full warmth is already closing.
The fix is not a better email. It is an SMS escalation sequence that fires automatically the moment the no-show signal fires — without waiting for a rep to notice anything.
The No-Show Signal Is the Trigger, Not the Rep's Inbox
Every automated recovery sequence starts with a trigger. For a missed Discovery Day, that trigger is a no-show signal — a CRM stage change, a button click in your platform, a webhook from your conferencing tool, or any notification your system can send.
The key word is any. There is no canonical CRM stage for "candidate did not join the Discovery Day call." But that does not mean you cannot automate a response. If your team clicks a button in your CRM when they pull up the call and the candidate is absent, that button is the trigger. If your conferencing platform sends a webhook when an attendee never joins, that webhook is the trigger. Whatever signal you can send, a stage-specific agent can receive — and respond to immediately.
The moment that signal fires, the missed meeting agent should send the first message. Not within the hour. Not when a rep gets around to it. Immediately. The candidate who missed a 9am Discovery Day and receives a text at 9:07am is a candidate you still have.
The Three-Step Escalation Structure
The sequence escalates in pressure and directness. Each step does one thing: offer a specific path back.
Step 1 — Low-pressure check-in (send immediately at no-show signal)
The first message assumes good faith. The candidate had a conflict. You are not accusing them of ghosting — you are opening the door.
The message should: acknowledge they missed the call without making it a confrontation, signal that the spot is still available, and offer 2–3 specific available times directly in the text thread. No booking link. No form to fill. Options in the thread, reply with a number.
Something like: "Hey [First Name] — looks like we missed each other for this morning's Discovery Day. Completely understand if something came up. I have a few open slots this week: Tuesday at 10am, Wednesday at 2pm, or Thursday at 11am. Reply with whichever works and I will get it on the calendar."
Step 2 — Direct re-book offer (send at 4 hours if no reply)
If the candidate did not reply to the first message, escalate the directness. This message is shorter. It assumes they saw the first one. It gives them a single easy action.
The message should: reference the missed morning, offer one specific time (the nearest available slot on your calendar), and make the reply as frictionless as possible.
Something like: "Still want to connect about [Brand]? My next open Discovery Day slot is Thursday at 11am. Reply YES and I will hold it for you."
Step 3 — Last-chance message (send at 48 hours if no reply)
This is the message that creates urgency without manufacturing a false deadline. Discovery Day cohorts fill. Slots that go unclaimed go to other candidates. That is true, and it is worth saying plainly.
The message should: be honest that the next available slot is limited, give them a clear way to respond, and leave the door open without chasing further after this point.
Something like: "Hi [First Name] — wanted to reach out one more time about your Discovery Day. Next available spot is [Date]. After that, slots fill quickly and we would need to push to the following month. If you are still interested, just reply here and I will lock it in. No pressure either way."
After step 3 without a reply, the sequence ends. A rep can review the thread and decide whether to continue. The automated sequence has done its job.
"44% of franchise brands never send a personal reply to a new lead — just an automated acknowledgment or nothing at all." — FranFunnel Franchise Lead Response Time Study · 530 brands · fielded March–April 2025
Why SMS, Not Email
An email sits in an inbox. A text lands on a lock screen. That distinction matters most at the moment of recovery, when speed is what determines whether you get a response at all.
A candidate who missed a Discovery Day is already slightly embarrassed. An email that arrives hours later — sandwiched between other messages — is easy to defer. A text that arrives within minutes of the missed call is immediate, personal, and requires a decision: reply or ignore. Most people reply.
The sequence works in SMS for a second reason: you can embed the specific available times directly in the message. The candidate does not click out to a booking page, open a form on their phone, scroll through a calendar widget, and complete a confirmation flow. They reply with a number. The system books it and sends the invite on the rep's behalf. Friction removed at every step.
In-Thread Booking Is What Makes Recovery Sequences Work
The difference between a recovery sequence that reschedules a Discovery Day and one that generates polite replies with no outcome is whether booking happens in the thread.
When a candidate replies "Tuesday works," the system should immediately confirm the time, send a calendar invite to both parties, update the CRM record, and close the loop — without a rep doing anything. If the candidate comes back and needs to change the time, the same conversation handles the reschedule.
This is why the sequence needs to be connected to your calendar, not just to your messaging platform. A text sequence that asks "when works for you?" and then routes the reply to a rep's inbox to handle manually is not a recovery sequence — it is a digital game of telephone. Calendar connection is what turns a text conversation into a booked meeting.
The Rep's Role: Override When Needed, Not Monitor by Default
The missed meeting agent handles the recovery automatically. But a rep can step in at any moment. The mechanic is straightforward: the moment a rep sends a manual message into the thread, the automated agent for that stage shuts off. The rep drives the conversation from that point. When the candidate moves to the next CRM stage — Discovery Day rescheduled, application active, whatever the next milestone is — the appropriate agent activates.
This is not a binary choice between automation and human judgment. The automation handles every no-show immediately, without anyone needing to notice it. The rep intervenes when the situation warrants it — a candidate who responds with concerns, a late-stage deal that needs a personal touch, a specific question the agent should not try to answer. Otherwise, the sequence runs. The rep shows up to a rescheduled Discovery Day, not to a missed call they just noticed three hours later.
FAQ
How quickly should a no-show follow-up message go out after a missed Discovery Day? The first message should go out within the first 10 minutes of the missed call — ideally immediately when the no-show signal fires. Discovery Day candidates are late-stage and warm; every hour that passes without contact reduces the likelihood of a reschedule. Immediate outreach signals that the seat still matters and gives the candidate a fast path back before they mentally close the door.
What should the first text say to a candidate who missed Discovery Day? The first message should assume good faith — something came up, not that they ghosted you. Acknowledge the missed call briefly, keep the tone warm and low-pressure, and give them 2–3 specific available times directly in the message. The goal is a reply, not a confrontation. Do not send a booking link in the first message; embed the times so the candidate can reply with a single number.
How many follow-up messages should a no-show recovery sequence include? Three messages is the right structure for a missed Discovery Day: an immediate check-in with available times, a direct re-book offer at the 4-hour mark if no reply, and a last-chance message at 48 hours if still no reply. After three unanswered messages, the automated sequence ends and the thread surfaces to a rep for review. More messages past that point tend to damage the candidate relationship rather than recover it.
What is the right trigger for a Discovery Day no-show automation? Any signal your system can send works as a trigger — a CRM stage change, a button click, a webhook from your conferencing platform, or an inbound notification. The key is that the signal fires as close to real time as possible. If your ops team manually marks a no-show in the CRM, that mark should trigger the sequence immediately. If your conferencing tool can send a webhook when an attendee never joins, that is even better.
Can the automated recovery sequence actually book a rescheduled Discovery Day without a rep? Yes, when the sequence is connected to your calendar. When the candidate replies with their preferred time, a calendar-connected system books the meeting, sends the invite on the rep's behalf, and updates the CRM record — all inside the text thread. The rep does not need to be involved until they show up to the rescheduled call with full conversation context already logged.
Should the no-show recovery sequence be different from the standard pre-Discovery Day sequence? Yes, meaningfully different. The pre-Discovery Day sequence is about confirmation, logistics, and building anticipation. The no-show recovery sequence is about re-opening a door without pressure, offering a specific path back, and escalating urgency only gradually. Using the same tone for both signals that your follow-up is generic — exactly what late-stage candidates notice and respond to poorly.
What happens if the candidate replies with a concern or objection instead of booking a time? The rep should step in. The automated sequence is built to handle logistics — rescheduling, time offers, confirmations. When a candidate surfaces a real objection (cold feet, financial questions, timeline concerns), that is a rep conversation. The mechanic is simple: the moment the rep sends a manual message into the thread, the automated agent shuts off. The rep handles the conversation. The next agent activates when the candidate moves to the next CRM stage.
Is a missed Discovery Day different from a missed intro call, and should the sequence be different? Yes, and the tone should reflect it. A missed intro call involves an early-stage candidate who may have submitted to multiple brands simultaneously; recovery is about earning their attention. A missed Discovery Day involves a late-stage candidate who has already committed significant time to your process — the sequence should acknowledge that investment, not treat them like a cold lead. The escalation structure is similar, but the language should reflect the depth of the relationship.
How does a no-show recovery sequence interact with the existing Discovery Day pipeline stage in the CRM? The missed meeting agent operates in parallel with the pipeline stage — it does not replace or change the stage on its own. When the candidate reschedules and confirms, that confirmation is the signal to update the CRM stage back to active Discovery Day. The stage transition then activates the standard Discovery Day agent (reminders, logistics, pre-call questions). The no-show sequence is a bridge back to the main track, not a parallel track.
What if we do not have a formal no-show stage in our CRM — can we still automate this? Yes. The trigger does not need to be a formal CRM stage. A button in your platform that a rep or admin clicks when they pull up the call and the candidate is absent works just as well. A webhook from your video conferencing tool, a custom field update, a tagged note — any signal you can send can trigger the sequence. The agent does not care about the source; it cares about the signal.
What is the risk of not automating Discovery Day no-show recovery? The risk is that recovery depends on a rep noticing the absence and following up quickly enough for it to matter. In practice, reps are often in other calls, managing other candidates, or simply unaware that someone did not join. By the time manual follow-up happens — hours later, often by email — the candidate has moved on mentally. Automated recovery sequences remove the dependency on someone noticing and respond in minutes, when the candidate is still in the moment and most recoverable.
A missed Discovery Day is not a lost deal. It is a deal that needs a faster response than your team can deliver manually. See how FranFunnel's missed meeting agent fires the moment the no-show signal hits and books the rescheduled call before your rep finishes their next meeting. Book a demo at franfunnel.com.