A candidate saying “please stop calling” should trigger the organization's approved communication-preference process. The agent should not argue, interpret the request as a hiring decision, or continue a scheduled call sequence because another system still considers it active.
Define opt-out scope with appropriate legal and operational review. Calls about one vacancy, automated outreach, all recruitment contact, and a request to use another channel may require different handling. This article describes implementation controls, not jurisdiction-specific legal advice.
Capture the candidate's intended preference
Use a brief clarification only when necessary to apply the request accurately. Record the stated preference, source time, relevant candidate and vacancy context if verified, and the action taken. Avoid collecting a personal explanation for opting out.
Apply the preference before scheduling another automated interaction. Downstream dialers, callback queues, and recruiter tools need a shared or synchronized state. A note hidden in the ATS may not stop a separate outreach system.
Work through a fictional channel change
A candidate asks not to receive automated phone calls but wants the recruiter to email about the current interview. The agent records that specific preference under the approved process and routes any ambiguous scope to staff.
It does not mark the candidate rejected or remove every application. Pending automated calls should be reviewed against the new preference before execution, while permitted human follow-up uses the approved channel.
| Preference case | Required handling |
|---|---|
| Stop automated calls | Relevant queue suppression |
| Prefer another channel | Approved channel update |
| One vacancy only | Scope preserved |
| Identity unresolved | Safe pending process without unnecessary outreach |
| Downstream update fails | Visible exception and owner |
Verify propagation and recovery
Track each system update and its outcome. If one destination fails, maintain an operational block or staff review according to policy rather than silently resuming contact. Repeated opt-out events should not create contradictory preferences.
Central preference management reduces inconsistency but requires integration work. Separate local flags are faster to add while risking stale queues. Test a preference change immediately before a scheduled callback and after a retry.
Review candidate contact confirmation for keeping administrative communication decisions outside suitability evaluation.
Questions about candidate opt-outs
Should opting out reject an application?
Do not infer that from a communication request. Follow the organization's separately approved application process.
Can the agent ask the candidate to reconsider?
Use the approved respectful process and apply the request. Do not pressure the candidate to continue automated contact.
What should staff see?
The requested scope, effective time, affected queues, permitted channel if stated, update results, and owner for any unresolved synchronization.