WhatsApp for Recruitment Agencies — Interview Reminders and Document Collection via API

Recruitment agencies live and die by candidate response rate. A screening call nobody picks up, an interview reminder buried in a spam folder, a CV request that sits unread in an inbox for three days — each one is a placement that slips. Email open rates for this kind of transactional message hover around 20-30%. WhatsApp read rates are routinely reported north of 90%, and candidates reply within minutes rather than days.

The catch: agencies typically message hundreds of candidates a week, often with near-identical text ("Hi {name}, your interview is confirmed for..."). Sent carelessly, that's exactly the pattern WhatsApp's anti-spam systems are built to catch. Here's how to build interview and document workflows that scale without getting your number throttled or banned.

Why WhatsApp fits the recruitment workflow

Three moments in a placement cycle are naturally message-shaped:

• Interview scheduling and reminders — confirm the slot, remind 24h and 1h before, handle reschedules.
• Document collection — CV, ID, references, signed contracts, all as attachments.
• Status updates — "your application moved to round 2," "the client wants a second interview," "you got the offer."

All three are transactional, not marketing, which matters both legally (opt-in requirements are lighter for service messages tied to an active application) and practically (transactional messages aren't subject to WhatsApp's quiet-hours deferral the way bulk sends are).

Interview reminders that don't trip the broadcast filter

TextMeFlow's anti-spam pipeline flags identical message bodies sent to more than 5 recipients within 10 minutes and throttles the account. A recruiter sending "Reminder: your interview is tomorrow at 10:00" to twenty candidates in one batch is a textbook match for that pattern.

The fix is cheap: interpolate something unique into every message — candidate name, role title, interviewer name, time slot. You need those fields anyway to make the reminder useful, so this isn't extra work, just don't template the whole string statically:

$body = "Hi {$candidate['first_name']}, reminder: your interview for "
      . "{$role['title']} with {$interviewer['name']} is tomorrow at "
      . "{$slot['time']}. Reply STOP to opt out of reminders.";

file_get_contents(
  "https://api.textmeflow.eu/send.php?recipient={$candidate['phone']}"
  . "&apikey={$apikey}&text=" . urlencode($body)
);

That single-recipient call goes out immediately — TextMeFlow's pacing delay only applies between consecutive sends from the same account, so the first message in a batch is never held back. If you're building against the newer REST API instead of the /send.php compat endpoint, the equivalent is a POST /v1/messages with to and text in the body, returning a 202 with a message_id you can poll or track via webhook.

Collecting CVs, ID and signed contracts

Document collection is the other half of the workflow, and it's where WhatsApp genuinely beats email: candidates can photograph a passport or forward a CV PDF from their phone in one motion instead of switching to a laptop to attach a file. Media messages are supported up to 100 MB, which comfortably covers CVs, scanned ID documents and signed contracts — see the media handling docs for the upload flow and supported formats.

Practical tip: ask for one document per message rather than "send your CV, ID and references," and confirm receipt on each one. Silent multi-document requests are where candidates drop off — a quick "Got your CV, thanks — now your ID please" keeps the flow moving and gives you a natural point to catch a missing or unreadable file.

Respecting quiet hours and opt-outs

Candidates are in different timezones more often than agencies expect, especially for remote or cross-border roles. TextMeFlow automatically defers non-urgent messages sent between 22:00 and 08:00 in the recipient's local time (inferred from their country code) to the next morning — you don't need to build timezone logic yourself, and messages are never dropped, only delayed. Reserve the urgent flag for genuinely time-critical sends, like "the client wants to move your interview to right now" — using it routinely defeats the point of the shaping.

STOP requests are honored automatically and immediately, which matters here specifically: a candidate who withdraws their application and texts STOP shouldn't keep getting reminder messages for a role they've already dropped out of. Build your CRM's opt-out sync against that behavior rather than reimplementing it. For the legal side of consent and retention around candidate data, see our GDPR checklist for sending WhatsApp messages — candidate data is personal data, and application records often need to be deleted on a shorter timeline than customer records once a role is filled or a candidate is rejected.

Disclaimer: the above is general information, not legal advice for your specific hiring process — check with counsel on retention periods for rejected-candidate data in your jurisdiction.

Sizing the plan to agency volume

A small agency running one recruiter through one WhatsApp number rarely needs more than Starter (500 messages/month, €5/mo) if messaging stays reminder-and-confirmation focused. Agencies running multiple recruiters or high-volume seasonal hiring (retail, hospitality, events) typically outgrow that fast — Business (25,000 messages/month, 3 devices, €29/mo) lets each recruiter pair their own number instead of funneling every candidate through one shared line, which also spreads risk: one recruiter's high volume doesn't threaten another's number.

Get started

TextMeFlow starts free — 50 messages/month, no time limit, one WhatsApp number — enough to pilot an interview-reminder workflow before committing budget. Every plan includes the anti-spam pipeline described above, EU hosting (Paris), and an automatic DPA on paid plans. Try it free and connect your first number in a few minutes.