Slash No-Shows: Build Automated Reminders with Make.com™

No-shows cost recruiting teams more than rescheduling time. Each missed interview slot represents a wasted interviewer hour, a delayed hire, and in competitive markets, a candidate who accepted an offer elsewhere while you were waiting for them to show up. As part of a broader strategy of recruiting automation with Make.com™, a structured reminder sequence is one of the highest-ROI workflows you can build — and one of the fastest to deploy.

This guide walks through every step: auditing your baseline, mapping your tools, building each reminder module, adding conditional logic, and verifying the workflow is working. By the end, you will have a live scenario that fires automatically on every new booking without any recruiter intervention.

Before You Start

Gather these before opening Make.com™ so the build goes in one sitting.

• Scheduling tool access: Calendly, Acuity Scheduling, HubSpot Meetings, Google Calendar, or any tool that fires a webhook on new bookings. You need admin access to configure the trigger.
• Email platform credentials: Gmail, Outlook, or a transactional email service — whichever your team uses for candidate-facing messages.
• SMS provider account: Twilio or a comparable provider with a Make.com™ native module. Have your account SID, auth token, and sender number ready.
• Make.com™ account: Any paid plan works. Estimate your monthly operations: four reminder messages × average monthly interview volume = minimum operations needed.
• 90 days of interview data: Pull no-show counts by stage. This is your baseline. You cannot measure improvement without it.
• Time estimate: 90–120 minutes for a clean first build. Add 30 minutes for testing.
• Risk note: Test with real but non-live bookings before activating. A misconfigured delay field can send reminders at the wrong time. Catch that in testing, not in production.

Step 1 — Audit Your No-Show Baseline

Before building anything, establish what you are solving. Pull 90 days of interview data and calculate your no-show rate by stage: phone screen, first-round, technical, final. Most teams discover the highest no-show rate is at phone screen — the lowest-commitment stage with the least time between booking and interview. That is where a four-touch sequence delivers the most immediate impact.

Document these numbers:

• Total interviews scheduled per stage
• No-shows per stage
• Average days between booking and interview date (your lead time shapes the reminder cadence)
• Current reminder method (manual email, single automated email, nothing)

Based on our testing, teams with zero automation or single-confirmation-only workflows consistently show no-show rates two to four times higher than teams running structured multi-touch sequences. McKinsey Global Institute research on workflow automation confirms that structured, rules-based processes eliminate the variability that causes service failures — including missed appointments. Your baseline gives you the before data you will use to demonstrate impact after the workflow is live.

Step 2 — Map Your Tool Stack and Choose Your Modules

Identify which Make.com™ modules you will use at each point in the scenario. The core stack is simple: one trigger module and four action modules.

If your scheduling tool has a native Make.com™ module, use it — the data mapping is cleaner. If not, configure a webhook trigger in Make.com™ and point your scheduling tool’s outgoing webhook at it. Either path delivers the same candidate data fields into the scenario.

Step 3 — Build the Booking Confirmation Module

The confirmation message fires immediately when a new booking is detected. This is the most important message in the sequence — it anchors the appointment in the candidate’s calendar and sets the tone for your communication.

1. Add your scheduling tool’s trigger module to a new Make.com™ scenario and authenticate it.
2. Run the trigger once with a test booking to capture the data bundle — you need to see the field names before you can map them.
3. Add an Email — Send a Message module directly after the trigger.
4. Map these fields from the trigger data bundle into the email module:
   • To: candidate email field
   • Subject: “Your interview is confirmed — [Job Title] at [Company Name]”
   • Body: Candidate first name, interview date, interview time (include timezone), interviewer name, location or video link, and a one-click add-to-calendar link if your scheduling tool generates one.
5. Send a test email to yourself. Verify every variable renders correctly before moving to the next module.

Keep the confirmation factual and short. The candidate just booked — they do not need encouragement copy. They need the logistics.

Step 4 — Configure the 7-Day Email Reminder

The 7-day reminder exists to re-anchor the appointment before the candidate’s week fills up. It is less urgent in tone than later reminders and can include light context — what to expect, who they will meet, whether there is anything to prepare.

1. After the confirmation email module, add a Tools — Sleep module (or use Make.com™’s built-in scheduling logic). Set the delay to fire seven days before the appointment date — this requires calculating the offset from the booking date using a date formula referencing the appointment date field from your trigger.
2. Add a second Email — Send a Message module after the delay.
3. Map candidate name, interview date, time, and a brief agenda or prep note into the template.
4. Subject line example: “Reminder: Your interview next week — [Job Title]”
5. Include a calendar link and any logistics the candidate needs (parking, video link, interview format).

Date formula note: Make.com™ handles date arithmetic natively. Subtract 7 days from the appointment date field using the addDays(appointmentDate, -7) function in the Sleep module’s target datetime field. Test this with a booking that is exactly 10 days out so the 7-day delay fires within your test window.

Step 5 — Configure the 3-Day SMS Reminder

SMS is the channel that cuts through. Asana’s Anatomy of Work research consistently shows workers are overwhelmed by email volume — a well-timed SMS reaches the candidate in a different cognitive space. Three days before the interview is the right moment: far enough to reschedule if needed, close enough to feel real.

1. Add another Tools — Sleep module set to three days before the appointment date.
2. Add your SMS provider module (e.g., Twilio — Send a Message).
3. Authenticate your Twilio account using your account SID and auth token.
4. Map the candidate’s phone number from the trigger data bundle. Confirm the number field is formatted in E.164 format (+1XXXXXXXXXX) — clean this with a text formula if your scheduling tool stores numbers without country code.
5. Write a short message: “Hi [First Name], a quick reminder — your interview for [Job Title] is on [Date] at [Time]. Reply CONFIRM to confirm or call us to reschedule. [Company Name]”
6. Keep SMS under 160 characters to avoid message splitting.

The CONFIRM reply pattern is optional but valuable — you can set up a separate Make.com™ scenario to watch for inbound SMS replies and log confirmations to your ATS or CRM.

Step 6 — Build the Day-Of Reminder (Email + SMS)

The day-of reminder is the last line of defense. Send it 2–3 hours before the interview start time — close enough that the candidate is already thinking about the day ahead, far enough that a recruiter can fill the slot if the candidate drops.

1. Add a Tools — Sleep module set to the appointment datetime minus 2.5 hours.
2. Add an Email — Send a Message module with a concise, logistics-only message. No new information — just date, time, location or video link, and a recruiter contact number.
3. Add an SMS module immediately after. Mirror the email content in SMS format: “Your [Company Name] interview starts in ~2 hours — [Time], [Location/Link]. Questions? Call [Phone]. See you soon.”
4. Send both. Do not choose one. The candidate may not check email in the morning but will see the SMS.

Based on our testing, the day-of message is the single highest-impact reminder in the sequence for reducing same-day no-shows. Candidates who genuinely forgot get a timely nudge. Candidates who planned to ghost get one last prompt that occasionally changes their decision.

Step 7 — Add Conditional Logic for Confirmations and Cancellations

A reminder sequence that fires even after a candidate cancels creates a terrible candidate experience and generates complaints. Add a router to handle both scenarios cleanly.

1. After the confirmation email module, add a Router module that splits the scenario into two paths.
2. Path A — Active reminder sequence: Continues through the 7-day, 3-day, and day-of modules. Apply a filter that only allows this path to proceed if no cancellation event has been received for this booking ID.
3. Path B — Cancellation handler: Triggered when your scheduling tool fires a cancellation or reschedule event for the same booking ID. This path halts the reminder sequence and optionally triggers your automated candidate rescheduling workflow.
4. To detect cancellations, set up a second Make.com™ scenario that watches your scheduling tool for cancellation events and writes a “cancelled” flag to a shared Google Sheet, Airtable base, or your ATS via API.
5. In your reminder sequence router, add a filter on Path A that checks this shared data source: if the booking ID has a “cancelled” flag, stop processing.

This architecture keeps the reminder sequence and the cancellation handler decoupled — each runs independently and communicates through a shared data store. It is more resilient than trying to manage both states in a single scenario.

Step 8 — Test with Sample Data and Activate

Never activate an untested automation that sends external-facing messages. A broken reminder sequence at scale can send dozens of misfired emails before you notice.

1. Create a test booking in your scheduling tool using a personal email address and phone number you control.
2. Run the scenario manually in Make.com™ using the “Run once” button. Watch each module execute in sequence.
3. Verify in Make.com™’s execution log that every module shows a green checkmark and the output data is correct — confirm variable substitution worked in every message.
4. Check your test email inbox and phone for each reminder message. Confirm they arrived with the right content and formatting.
5. Test the cancellation path: cancel the test booking and verify the router correctly halts the sequence.
6. If all modules pass, activate the scenario. Make.com™ will now process every new booking automatically.
7. Set up error notification: add an error handler route that sends you a Slack message or email if any module fails. This gives you real-time visibility without monitoring the execution log manually.

How to Know It Worked

Return to your baseline data 30 days after activation. Compare:

• No-show rate by stage (before vs. after)
• Percentage of candidates who confirmed ahead of time
• Recruiter time previously spent on manual reminder calls and follow-ups
• Make.com™ execution log: scenario success rate (target 98%+ successful runs)

Based on our testing, teams implementing a four-touch multi-channel sequence see no-show rates fall meaningfully within the first two to three hiring cycles. The improvement compounds as the workflow runs on every booking without exception — something manual processes cannot guarantee. SHRM research on hiring process quality consistently links candidate communication reliability to both no-show rates and candidate experience scores.

If your no-show rate does not move, check two things first: (1) Are the delay timers firing at the right time relative to the appointment date? Pull the execution log and spot-check the timestamp each module fires. (2) Is your candidate phone number field populated reliably in the scheduling tool? SMS reminders only work if the number field is required at booking.

Common Mistakes and How to Avoid Them

Sending reminders after a cancellation

This is the most common complaint teams receive after launching reminder automation. Fix it with the router and shared cancellation flag described in Step 7. Do not skip this step to save build time.

Using a single channel

Email-only reminder sequences have meaningfully lower effectiveness than multi-channel sequences. Gartner research on employee and customer communication consistently finds that message format and channel preferences vary — building for one channel assumes everyone behaves the same way. They do not. Add SMS.

Sending reminders without personalization

Generic “Your interview is tomorrow” messages read as automated and low-effort. Map candidate name, role, and interviewer name into every template. The marginal effort is zero once the variable is mapped — it just requires setting it up correctly in the build.

Incorrect date arithmetic

A 7-day reminder that fires 7 days after the booking rather than 7 days before the interview is worse than no reminder. Test your date formulas explicitly with bookings at known lead times. This is the most common technical error in first builds.

No error handling

Make.com™ scenarios fail silently if you do not configure error routes. An unauthenticated email module or a Twilio balance that ran out will stop the sequence without alerting anyone. Build error notifications from day one. Parseur’s Manual Data Entry Report notes that silent process failures in automated workflows are among the leading causes of data quality degradation — the same principle applies to communication automation.

Extend the Workflow

Once this sequence is live, the same architecture supports adjacent automation. The automated interview scheduling workflow feeds directly into this reminder sequence — scheduling automation creates the booking, reminder automation handles everything after. Pair both with automated candidate follow-up sequences post-interview to close the communication loop without any recruiter action.

For teams ready to build the full hiring workflow, automated offer letter generation and end-to-end workflows to cut time-to-hire are the natural next builds. Each scenario connects to the others through shared data — your scheduling tool, your ATS, and your communication platforms all feed a unified recruiting process that runs faster and more consistently than any manual equivalent.

The complete campaign map lives in the parent guide on recruiting automation with Make.com™. Build the reminder sequence first — it is the highest-impact, lowest-complexity entry point — then use that foundation to automate the rest of your hiring process systematically.