Post: How to Build a Candidate Communication SLA That Stops Ghosting
Build a candidate communication SLA by mapping every status a candidate can hold, assigning a message and a deadline to each, naming one owner, and automating the sends on top of your ATS. The SLA turns ghosting from a default into a violation the system catches. Here is how to design and enforce it.
Related reading: Why Your Hiring Process Is Breaking · 8 Candidate Communication Templates for Recruiters in 2026 · What Is Candidate Ghosting? Causes and Fixes for HR Teams.
Before You Start
You need an ATS with status flags and notification capability, plus a set of pre-written templates for each status. Assign a single process owner accountable for every candidate’s communication. Review the pillar on fixing broken hiring for how the SLA layer fits the full system.
Step 1: Map every candidate status
List the states a candidate can occupy: screened, shortlisted, on hold, frozen, advanced, declined, offer. Each one is a moment a candidate is waiting for word. The map is the skeleton of your SLA.
Step 2: Assign a message and deadline to each
Write the rule: for example, a status update within 48 hours of any change, and a decision communicated within five business days of a final round. The deadline is what makes the SLA enforceable rather than aspirational.
Step 3: Name the owner
One person owns communication for every candidate. Diffuse responsibility is the root cause of ghosting — when everyone owns it, no one does. A single owner closes the gap.
Step 4: Automate the sends
Build the notification layer on the ATS so updates fire on status change without anyone remembering. When a coordinator sets a hold flag, the hold message sends inside the SLA window automatically. Make.com connects the ATS to your messaging so the hard messages — freeze, rescind — never depend on human reluctance.
Step 5: Add SLA timers and escalation
Set timers that flag any candidate stalled past the deadline and escalate to the owner. This makes a missed update visible instead of silent.
How to Know It Worked
Track candidate NPS and the percentage of status changes that triggered a message within the SLA window. A working SLA pushes both toward the top of their range and drives negative “they ghosted me” reviews toward zero.
Common Mistakes
The first mistake is writing an SLA with no automation, so it depends on memory and fails under volume. The second is no single owner, which recreates the diffuse-responsibility gap. The third is leaving the hard messages manual, since those are exactly the ones teams avoid sending.
Expert Take
A communication SLA that lives in a policy document and not in your ATS is worthless. The whole point is to remove human reluctance from the hard messages, and you only do that by automating the trigger. When the freeze notice sends itself the instant the flag is set, nobody has to summon the will to write bad news. That is the difference between an SLA that ends ghosting and one that just documents it.
RELATED POST
