Define both failures in one line
No show: a session was booked, the client did not arrive, and no message came either. No response: you sent something that needed a reply and none arrived within the window you set. Write both definitions down, including the window, because vagueness is what stops you acting on them.
Two definitions also stop the problems blurring together. A no-show needs warmth and another date, while a silence usually needs a shorter, plainer message. With the definitions written, you can build each path without reopening the question every time.
Build the no-show path
Send a reminder before the session: date, time, place, and what to bring. Follow with a short message after the missed session that asks one question and offers another date, without guilt. Two messages, a couple of days apart, then a stop if there is no reply.
People miss sessions for ordinary reasons, and a calm second message recovers more of them than an explanation of your policy ever will. Keep the reply short enough to answer in one line on a phone: one question, one offer, no lecture.
Build the no-response path
Start the clock at the message that needed a reply. The second message adds something new rather than nudging; the third makes the ask smaller; the fourth is a plain close that leaves the door open. Three touches is usually enough to prove the person is not coming.
Never resend the same message twice, because if the first did not land, the second must give them a new reason to open it. Move the lead out of your active list at the end, so your pipeline shows reality rather than hope.
Automate it, then read the logs
This is the part worth automating, because it is the part that always slips. In QwikSol, an automation starts from a trigger, waits, checks a condition and sends across email, SMS and voicemail. Triggers include a stage change, a no-response on a drip or scheduling, a training completion and reminders.
Event reminders handle the session before it happens, and no-response campaigns handle the silence after. Read what went out and what was delivered, then adjust the timing and the wording. Automation does not remove the judgement; it removes the forgetting.
- Write down what a no-show and a silence each mean, including the window.
- Two calm messages recover more no-shows than a policy explanation.
- Automate the reminders and the silence, then read the logs and adjust.