60% Fewer No-Shows with Automated Interview Reminders: How Sarah Rebuilt Her Reminder Workflow Using Keap and Make.com™

Interview no-shows are not a candidate problem. They are a process problem — and they are almost entirely preventable. Sarah, an HR director at a regional healthcare organization, was losing two to three interview slots every week to candidates who simply forgot, got confused about the time, or never received a confirmation. Her team was sending reminders manually, which meant reminders went out when someone remembered to send them, not when the candidate needed them.

After rebuilding her reminder workflow with Keap and Make.com™, Sarah cut no-shows by 60% and reclaimed six hours per week — time her team now uses for actual recruiting work. This case study breaks down exactly what she built, where it broke first, and what the workflow looks like running at full speed.

This satellite drills into one specific execution layer of the broader recruiting automation strategy covered in our complete guide to integrating Make.com™ and Keap for recruiting automation. If you are new to the Keap-Make.com™ stack, start there.

Snapshot: Sarah’s Interview Reminder Transformation

Context and Baseline: What Was Breaking

Sarah’s team was scheduling 15 to 25 interviews per week across three hiring managers and two HR coordinators. Every scheduled interview required someone to manually send a confirmation email at booking, a reminder the day before, and a same-day reminder on the morning of the interview. With no standardized template, reminder quality varied. With no tracking system, reminders were sometimes skipped entirely during busy weeks.

The result was predictable. SHRM research consistently links poor candidate communication to higher drop-off rates and worse offer acceptance outcomes. In Sarah’s case, the impact was concrete: two to three missed interview slots per week, wasted hiring manager time, and a candidate experience that felt disorganized even when the hiring process itself was well-designed.

The deeper issue was cognitive load. UC Irvine research on task-switching found that interruptions — including the mental overhead of remembering to send a reminder — cost workers an average of 23 minutes of refocus time per disruption. Multiplied across a team of three sending reminders ad hoc throughout the day, the drag was real.

Sarah’s constraint: Keap was the system of record and was not going away. Any solution had to work within Keap, not replace it.

Approach: Build the Sequence Before Adding Anything Else

The decision was to build a fully deterministic reminder sequence — no AI, no dynamic personalization, no conditional branching based on candidate behavior — until the base workflow was stable. This matches the principle underlying our recruiting automation pillar: structured sequence first, intelligence layers second.

The target workflow:

1. Candidate books an interview via Keap appointment page.
2. Make.com™ detects the new appointment and pulls contact data.
3. Date and time values are parsed and formatted correctly.
4. A 24-hour reminder email fires via Keap.
5. A 1-hour reminder email fires via Keap.
6. A Keap tag — “Reminders Sent” — is applied to the contact record after both reminders are delivered.

No SMS in phase one. No personalization tokens beyond first name and interview time. The goal was a workflow that ran without human intervention and produced a consistent, auditable output every time.

Implementation: Module by Module

Module 1 — Keap: Watch Appointments

The Make.com™ scenario opens with a Keap “Watch Appointments” module configured to fire whenever a new appointment is created. Sarah’s team used Keap’s native appointment booking page for all interview scheduling, which made this trigger clean — no tag workarounds required.

Critical data pulled from this module: candidate first name, candidate email address, appointment start date and time, appointment type (to distinguish interviews from other meeting types), and a custom field containing the hiring manager’s name. Filtering at this module level — limiting the scenario to appointments of type “Interview” — prevents the workflow from firing for internal team meetings booked through the same Keap system.

Module 2 — Make.com™ Tools: Parse and Format Date-Time

This is where most builds fail. Keap returns appointment timestamps in ISO 8601 format, which Make.com™ handles natively — but calculating a trigger time 24 hours before the appointment requires explicit subtraction, and the output needs to match whatever format Keap’s email scheduling or the downstream delay module expects.

Sarah’s build used Make.com™’s built-in date and time functions to calculate two values: appointmentTime minus 24 hours and appointmentTime minus 1 hour. Both values were stored as variables before any reminder logic ran. This single module absorbed all the formatting complexity so downstream modules could reference clean, pre-validated timestamps.

This step also handled time zone conversion. Sarah’s organization operates across two time zones. Without explicit zone handling, a 9:00 AM interview in one location would generate a reminder timed for 9:00 AM in the other. The fix — explicit UTC normalization followed by local zone conversion — took 20 minutes to configure and eliminated an entire class of potential errors. For more on avoiding these configuration pitfalls, see our breakdown of common Make.com™ Keap integration errors.

Module 3 — Make.com™: Sleep / Delay to 24-Hour Mark

Make.com™’s “Sleep” module pauses scenario execution until the calculated 24-hour-before timestamp. This is the mechanism that makes the timing deterministic — the scenario does not rely on a recruiter’s calendar or memory. It fires at the exact moment calculated in Module 2, regardless of what else is happening in the office.

Module 4 — Keap: Send Email (24-Hour Reminder)

The first reminder email pulls the candidate’s first name, the appointment date and time formatted for human readability, the hiring manager’s name, and a static calendar link or video conference URL stored in a Keap custom field. The email template was written once and locked. Every candidate receives the same structure, which means every candidate gets the same information — a significant improvement over the ad hoc messages the team was previously writing on the fly.

Module 5 — Make.com™: Sleep / Delay to 1-Hour Mark

Identical logic to Module 3, but targeting the 1-hour-before timestamp. The scenario resumes at that point and proceeds to the same-day reminder.

Module 6 — Keap: Send Email (1-Hour Reminder)

The same-day reminder is shorter than the 24-hour version — confirmation of time, location or video link, and a single sentence inviting the candidate to reply if they need to reschedule. The brevity is intentional: a lengthy email 60 minutes before an interview creates friction, not confidence.

Module 7 — Keap: Apply Tag (“Reminders Sent”)

After both reminders fire, Make.com™ applies a “Reminders Sent” tag to the Keap contact record. This tag serves two purposes: it creates an audit trail that managers can review in Keap without opening Make.com™, and it acts as a de-duplication guard. A filter at the start of the scenario checks for this tag — if it is already present, the scenario terminates without firing a second set of reminders. For teams managing Keap tags and fields with Make.com™, this pattern applies broadly across any workflow that needs to prevent repeat execution.

Results: Before and After

The 60% reduction in no-shows is significant, but the more durable outcome is the scalability. When Sarah’s organization opened a second hiring surge six weeks after launch — interview volume roughly doubled — the workflow handled the increase without modification. No one on the HR team did anything differently. The scenario fired more often; the recruiters did not.

McKinsey Global Institute research on automation value consistently points to this pattern: the ROI of a well-built workflow compounds with volume rather than degrading. Sarah’s team experienced exactly that.

Lessons Learned

What Worked Better Than Expected

The audit tag was underestimated at the design stage. Sarah’s team initially treated it as a nice-to-have. Within two weeks, it became a routine check — hiring managers scanning Keap contact records before interviews to confirm reminders had gone out. That visibility reduced pre-interview anxiety for the hiring team and eliminated a class of “did the candidate get a reminder?” questions that previously bounced through the team’s inbox.

The filtering by appointment type also proved more valuable than anticipated. Before filtering was added, a test scenario accidentally triggered a reminder for an internal HR meeting. Adding the appointment-type filter at Module 1 solved this permanently and made the scenario safe to run across all Keap appointment types without risk of misfires.

What We Would Do Differently

The original build did not account for rescheduled interviews. If a candidate rescheduled after the reminder sequence started, the original appointment’s reminders would still fire — for an interview that was no longer happening. The fix — watching for appointment cancellations and applying a “Reschedule Detected” tag that kills the original reminder thread — was added in a second sprint. It should have been in the initial build.

SMS was deprioritized in phase one for simplicity. In hindsight, adding a text message reminder alongside the 1-hour email would have been straightforward given the data was already flowing correctly. If you are building this from scratch, wire in SMS from the start rather than retrofitting it later. Our guide to automated interview scheduling with Keap and Make.com™ covers the calendar and communications integration in more depth.

Time zone handling should be designed before anything else, not discovered mid-build. Sarah’s team operated across two time zones. If that constraint had been mapped at the outset, the formatting module would have been built correctly the first time rather than requiring a rebuild after the first cross-zone reminder misfired.

What to Build Next

Sarah’s reminder workflow is now one node in a larger automation pipeline. The next logical additions:

• Post-interview feedback collection — a Make.com™ scenario triggered by the appointment end time that sends hiring manager rating forms automatically. See our guide on automating candidate feedback with Make.com™.
• Candidate status update triggers — connecting the interview outcome tag in Keap to next-stage communications, so candidates advance or receive a decision notice without recruiter intervention. Our guide to automating candidate experience with Make.com™ and Keap covers this layer.
• Reporting pipeline — logging each reminder event to a Google Sheet for weekly no-show rate tracking and process improvement data.

Each of these builds on the same Keap-Make.com™ foundation Sarah already has in place. The incremental effort is low; the compounding value is high.

For the full architecture connecting all of these workflows, return to the complete Keap and Make.com™ recruiting automation guide. If you are ready to map your own automation opportunities, our Keap CRM automation for HR and recruiting case study shows how teams identify and prioritize the highest-value workflows before writing a single module. And if your goal is reducing time-to-hire across the full pipeline — not just the reminder step — see our breakdown of slashing time-to-hire with Keap and Make.com™.