Back to Blog
Automation
WhatsApp
Candidate Experience
Document Collection

Automated Candidate Reminders That Actually Get Replies

Michael··7 min read·Updated
Automated Candidate Reminders That Actually Get Replies

What makes automated candidate reminders work: timing, channel, tone and asking only for what is missing, plus example sequences to adapt for your agency.

Every recruiter knows the feeling. You sent a candidate a polite request for three documents on Monday. On Wednesday you sent a reminder. On Friday you sent another, slightly less polite. Nothing. Then the following Tuesday the candidate replies, "Sorry, what did you need again?" and sends a photo of the wrong document.

The problem is rarely that candidates do not care. They are busy, they are juggling other applications, and your messages land in a crowded inbox at the wrong moment. Automated candidate reminders can fix that, but only if they are designed well. Badly designed automation just sends the same ignored message more often, and candidates learn to tune it out even faster.

This is part 2 of our Stop Chasing: Recruitment Automation Playbook series. In this guide we look at what actually makes a reminder work: timing, channel, tone and, above all, asking only for what is still missing. We finish with example sequences you can adapt for your own agency.

Why most candidate reminders get ignored

Before fixing reminders, it helps to know why they fail. Look at your own sent folder and you will probably spot a few of these patterns.

They repeat the whole list every time

A candidate who has already sent two out of four documents gets a reminder listing all four. It feels like nobody read their reply, so they assume the system is broken or the recruiter is not paying attention. Worse, they may resend documents you already have and still forget the ones you need.

They are vague

"Just a reminder to send your documents" makes the candidate do the work of remembering what was needed. Specific requests ("We still need the back of your driving licence") get acted on; vague ones get postponed.

They arrive on the wrong channel at the wrong time

An email sent at 9pm on a Friday to a candidate who mainly lives on WhatsApp is unlikely to get a quick reply. Equally, a stream of WhatsApp messages at 7am will irritate rather than prompt.

They sound like a machine

Reminders that read like system notifications ("Action required: outstanding items") feel impersonal and easy to ignore. Candidates respond to people and to the agency they signed up with.

The four ingredients of reminders that get replies

1. Timing

Good candidate follow up automation spaces reminders sensibly. The first reminder should come soon enough that the original request is still fresh, typically a day or two later. After that, gaps can widen a little. Avoid unsociable hours, and think about your candidates' working patterns: shift workers might reply after a shift, office-based candidates might reply at lunchtime.

Also think about urgency. A candidate due to start on Monday needs a tighter sequence than one being registered for future work.

2. Channel

Most candidates reply fastest on the channel they use every day. For many, that is WhatsApp. Email still matters, especially for candidates who prefer it and for formal requests, and recruitment reminder emails sent from your agency's own domain are far more likely to be opened than messages from an unknown address. The best approach uses both, consistently, rather than switching randomly.

3. Tone

Write reminders the way your best consultant would. Friendly, clear, short and in your agency's voice. Thank the candidate for anything already sent. Explain briefly why the document matters ("so we can confirm your start date"). Make it easy to reply ("just send a photo here").

4. Ask only for what is still missing

This is the single biggest improvement most agencies can make. Every reminder should reflect the current state of the candidate's file: what has been received and accepted, what was rejected and why, and what is still outstanding. When a candidate sends a blurred photo, the next message should say exactly that and ask for a clearer one, rather than repeating the original request.

Example reminder sequences

Here are two sample sequences. Adapt the timing and wording to your candidates and your agency's voice.

Sequence A: Candidate starting soon

WhenChannelMessage focus
Day 0WhatsApp and emailClear list of what is needed and why
Day 1WhatsAppFriendly nudge naming outstanding items
Day 2EmailOutstanding items only, with start date mentioned
Day 3WhatsAppShort, specific: "Just your certificate left"
Day 4ConsultantPersonal call if still incomplete

Sequence B: Candidate registering for future work

WhenChannelMessage focus
Day 0WhatsApp and emailWelcome and full list
Day 2WhatsAppOutstanding items only
Day 5EmailOutstanding items, why they matter
Day 9WhatsAppFinal friendly nudge
Day 14ConsultantReview: call or pause

Example wording

First reminder:

Hi Priya, thanks for sending your passport, that is all sorted. We just need two more things: your first aid certificate and proof of address. You can send photos here whenever suits.

After a rejected document:

Thanks Priya. The proof of address came through a bit blurry and the bottom of the page is cut off. Could you send another photo with the whole page in view? That is the last thing we need.

Final nudge:

Hi Priya, just your first aid certificate left and you are all set for Monday. Send it over when you can.

Notice what these have in common: they are short, they acknowledge progress and they name exactly what is missing.

When to stop chasing and hand over to a person

Automation is excellent at persistence, but it should not chase forever. Build a clear handover point into every sequence. When a candidate has not responded after several reminders, or has replied with a question the automation cannot answer, a consultant should step in.

That personal call is often what unlocks a stuck candidate. Perhaps they do not have the document, or they misunderstood the request, or they have taken another job. A consultant can find out in two minutes what ten more reminders would never reveal.

The goal of chasing candidates with automation is not to remove people. It is to make sure consultants only spend time on the conversations that genuinely need them.

How GettingDocs handles automated candidate reminders

Amy, the GettingDocs AI assistant, is built around these principles. Amy chases candidates on WhatsApp and on email sent from your agency's own domain, with requests written in your agency's voice. When a document arrives, Amy checks it is readable and the right document; blurred photos, cut-off pages and wrong documents are rejected and the candidate is chased again for a usable copy.

Accepted documents are filed onto the candidate's record in your ATS (Recruit CRM, Crelate, Zoho Recruit and JobAdder today), matched by record ID, email or phone, never by name. And because GettingDocs charges a per-candidate fee only when all requested documents are complete, you are not paying for candidates who never submit. See the full feature set on the GettingDocs homepage.

Key takeaways

  • Reminders fail when they repeat the whole list, are vague, arrive at the wrong time or sound robotic.
  • Timing, channel, tone and specificity are the four ingredients that get replies.
  • Ask only for what is still missing, and explain clearly why a document was rejected.
  • Use WhatsApp and email together, from your agency's own domain and in your voice.
  • Hand over to a consultant at a set point, so nobody is chased forever.

If you want reminders that candidates actually answer, without your consultants writing every one, book a call with GettingDocs and see Amy in action.

Related reading: Candidates Not Sending Documents? 7 Fixes That Work.


Please note: this article is general information, not legal advice, and was correct at the time of writing (October 2026). Rules and guidance change, so please check the latest official guidance in the markets you recruit in before relying on it.

Written by

Michael