How Staffing Agencies Automate Candidate Follow-Up With AI

Map the points where candidates go quiet (after applying, before interviews, after interviews, before a first shift, during assignments and as assignments end), then trigger a message from your ATS or an automation tool at each. AI personalises the wording and sorts the replies; a recruiter handles anything that needs judgement.

Agencies often start with the easiest message, the application acknowledgement, because it's simple to set up. The money is elsewhere. A temp who doesn't turn up for a Saturday shift costs you the margin, the client's goodwill and a frantic morning. A contractor whose assignment ends without anyone checking their availability is a placement you hand to a competitor. Automate in order of what silence costs, not what's easiest to build.

Follow me on Instagram@sagnikteaches

Seven moments where silence costs placements

An eighth, lower-priority sequence is worth adding later: a monthly check-in with dormant candidates who haven't worked through you in three months, asking if they're available and whether their skills or preferences have changed.

Connect on LinkedInSagnik Bhattacharya

Pace that sequence rather than sending it in one batch. An agency with 400 candidates who haven't worked in three months would, sending all at once, get dozens of replies within the hour ("yes, available now", "weekends only", "I've moved, can you update my address") and a recruiter who can't keep up. Spread across the month, 400 is about 20 a working day, so replies arrive at a pace someone can act on. Ask one question per message ("Are you available for work in the next month? Reply YES, NOT NOW or STOP") so the reply sorting described below has an easy job, and have NOT NOW push the next check-in back three months rather than one.

Subscribe on YouTube@codingliquids

Which follow-up to automate first on your desk

For a temp or shift desk, start with moment 5, then 7. Shift confirmations turn no-shows into late cancellations you can cover, and assignment-end checks keep good workers busy with you. For a permanent desk, start with moments 2 and 4. Candidates who never hear back after applying or interviewing talk about it, and the post-interview window is when offers are won or lost.

Measure one number before and after each: no-shows per 100 shifts for moment 5, the share of finishing temps redeployed within a week for moment 7, and candidate complaints or reviews mentioning "never heard back" for moment 2. Without a baseline you'll never know whether the automation helped or just made noise.

Where to build it: your ATS or an automation tool

Look inside your ATS first. Bullhorn Automation (formerly Herefish) is built for exactly these sequences, including start-date reminders, redeployment prompts and re-engagement of existing candidates. Recruit CRM includes automated email sequencing on its Business and Enterprise plans. Manatal adds workflow automation from its Enterprise plan, $35 a user a month billed annually or $39 monthly. Native automation reads your live data, so a reminder knows whether the interview was rescheduled.

Trigger timing needs a test of its own. "Same afternoon" for moment 4 sounds simple until a recruiter books a 4pm video interview and the automation, set to fire at 3pm, asks the candidate how it went an hour before it starts. Time the trigger from the interview's scheduled end, say two hours after, and add a condition that the status is still "booked" or "attended" rather than "rescheduled" or "cancelled". Reminders have the reverse trap: a 2-hour reminder for an 8am interview lands at 6am, inside the quiet hours set out further down. Decide whether it counts as critical, or send it the evening before instead.

Use Zapier or Make for the gaps: connecting your ATS to a texting service, or adding an AI step your ATS lacks. Watch the pricing model. Zapier counts every successful action step as a task; triggers and filters are free, and an AI step uses 1, 3 or 5 tasks per run depending on the model tier. Make runs on credits, starting at about $9 a month. At high message volumes, per-task pricing adds up quickly, as the worked example below shows. If you're weighing up whether your ATS can carry this at all, evaluating the AI features in your recruitment software has the questions to ask.

Templates with a personal line, and when the personal line goes wrong

The most reliable pattern is a fixed template with one AI-written line. The template carries the facts, so they're always right; the AI line makes it feel like it came from someone who knows the candidate. A shift confirmation for a temp booked with an events company client:

Hi {first_name}, you're booked with {client} on {day} {date},
{start}-{end}, at {venue}. {personal_line}
Please reply YES to confirm, or NO if you can't make it and
we'll find cover.

AI instruction for {personal_line}:
Write one short, friendly sentence (under 20 words) using ONLY
recruiter notes from the last 14 days and the client's site
notes. If nothing relevant, return an empty line.
Never mention pay, health, or anything the candidate told us
in confidence.

Illustrative outputs, and what a recruiter would change:

Candidate A: "Last time you said parking was tricky: the
  client says staff can use the car park behind the hall."
Candidate B: "Welcome back after your holiday, hope it was
  great!"
Candidate C: ""

A is the ideal: specific, helpful, based on a recent note. C is fine; an empty line is better than filler. B is the failure. The holiday note was four months old, from before the 14-day rule was added, and the candidate had since worked six shifts. "Welcome back" read as if nobody had noticed. It's harmless on its own, but repeated across a desk, stale personal lines make automated messages feel more automated, not less. Keep the date limit on notes, and spot-check a dozen personal lines each week.

Outcome messages candidates don't resent

Moment 2 is where a permanent desk's reputation is made or lost, and it's the one message that should always wait for a recruiter's approval. The standard version most candidates receive, if they hear anything at all:

Before: "Thank you for your application. Unfortunately you have not been successful on this occasion. We will keep your details on file."

Give the AI the role, the recruiter's one-line reason and the candidate's strongest relevant skill, and ask for a short, specific message with a next step. Illustrative draft after the recruiter's edit:

After: "Thanks for applying for the payroll administrator role with our client, a software reseller. They're interviewing people who've run month-end payroll for 100+ staff, which is a step beyond your current role. Your customer-facing admin experience is strong, and two roles we're filling this week suit it well: [links]. Reply YES if you'd like us to put you forward for either."

The recruiter's approval step exists for two reasons. The reason given must be true and must not reveal anything the client asked to keep private, such as salary bands or internal candidates. And the suggested roles must genuinely fit; offering unsuitable jobs to soften a rejection is worse than offering none. It takes about thirty seconds per message, and it's the difference between a candidate who re-applies and one who tells friends to avoid you.

Assignment-end messages that point to the right next job

At moment 7 the AI does more than word a message: it picks which open roles to mention. Give it the candidate's preference fields as well as their skills, or it will match on skills alone. An illustrative run for a warehouse temp finishing a six-week assignment:

Inputs
  Skills: counterbalance forklift, pick and pack, RF scanner
  Preferences: days only, max 30 min travel
  Note (3 weeks ago): "left [client X] after dispute with
  supervisor"
Open roles
  1) Night picker, [client Y], 10pm-6am
  2) Goods-in operative, [client Z], 7am-3pm, 20 min away
  3) Forklift driver, [client X], days

Output
"Your assignment ends on Friday. Great news: we have forklift
work at [client X] starting Monday, plus a night picking role
at [client Y]. Reply 1 or 2 if you're interested."

The model led with the strongest skills match and ignored everything else. The night role breaks "days only", and client X is where the dispute happened; only role 2 fits, and it wasn't offered. Two changes stop this. Filter open roles against the preference fields before the AI sees them, so it can only choose from suitable jobs. And turn notes like "left after dispute" into an exclusion the automation applies, not context the AI is left to weigh. Recruiters still call their best temps personally; this message is for the rest of the finishing list, and it's only worth sending if the roles in it are ones the candidate might accept.

Letting AI sort the replies

Sending is the easy half. The recruiter's time goes on reading replies, and that's where an AI step pays for itself. Classify every reply and route by category:

Classify this reply to a shift confirmation text.
Categories:
CONFIRMED - clear yes
CANCELLED - clear no or can't attend
UNSURE - anything conditional, vague or mixed
QUESTION - asks something (pay, directions, times)
ISSUE - complaint, safety or wellbeing concern, or distress
OPT_OUT - asks to stop messages
Return the category and, for UNSURE/QUESTION/ISSUE, a one-line
summary. If in doubt between two, choose the one that sends it
to a person.

Reply: [text]

Only CONFIRMED and OPT_OUT should be handled automatically (mark the booking confirmed; stop messages). Everything else goes to a recruiter, with CANCELLED and ISSUE flagged urgent. An illustrative batch from one evening:

"YES see you Saturday"            -> CONFIRMED
"cant do it sorry my kid is ill"  -> CANCELLED (urgent)
"yeah should be ok"               -> CONFIRMED   [wrong]
"is it the same entrance as last time?" -> QUESTION
"stop texting me"                 -> OPT_OUT

The third line is the classic mistake. "Should be ok" is a hedge, and a temp who hedges on Thursday is the one who texts at 6am on Saturday. It should be UNSURE. Adding two examples of hedged replies to the prompt ("should be fine", "hopefully", "probably") and the "if in doubt, send it to a person" rule fixes most of these. Check a sample of CONFIRMED labels weekly for the first month.

ISSUE replies need a named owner and a time limit, because they often arrive tucked inside routine messages. Suppose a cleaner on a four-week office contract answers the weekly timesheet reminder with: "done, sent it. also the supervisor keeps shouting at us, not sure i want to go back monday." The classifier rightly returns ISSUE, summarised as "timesheet sent; says supervisor shouts at staff; may not return". Nothing automatic should follow, not even a sympathetic auto-reply, which reads as the agency filing a complaint under "noted". What works: ISSUE flags reach the candidate's own recruiter by text as well as in the ATS, the recruiter calls the same day, logs what was said and agrees with the account manager whether to raise it with the client. And because the reply also said the timesheet was sent, check the timesheet gets marked as received, or the candidate is chased for it the next morning on top of everything else.

Consent, opt-outs and quiet hours

• Record consent at registration for each channel you'll use: text, email, WhatsApp. Candidates who registered for email alerts haven't agreed to texts.
• Honour STOP immediately and across every sequence, not just the one they replied to.
• Quiet hours: no messages between 8pm and 8am except shift-critical ones, such as a same-day change.
• Frequency caps: no more than one non-critical message a day and three a week per candidate. Several sequences running at once is how agencies end up sending five texts in a day.
• Keep sensitive details out of messages. No health, pay disputes or disciplinary matters by automated text.
• WhatsApp has its own rules. On the WhatsApp Business Platform, messages you start outside a 24-hour window after the candidate last messaged you must use pre-approved templates. From 1 October 2026, replies inside that window are charged too once a number passes 1,000 service messages a month, and utility templates such as shift confirmations are charged even inside it, so check Meta's current rates before moving confirmations there. WhatsApp Business app vs API explains which set-up you need.

Testing each sequence on a dummy candidate before launch

Create a test candidate record with a recruiter's own mobile number and email, then walk it through every sequence before a real candidate receives anything. Five checks catch most problems:

1. Book a test shift and confirm both reminders arrive at the right times, with the venue and start time filled in.
2. Change the start time after the first reminder, and check the second one shows the new time. A reminder quoting the old time means the sequence stored the value when it started instead of reading the live field.
3. Cancel the shift, and check no further reminders arrive.
4. Reply with a hedge ("should be ok") and with a question, and check both reach a recruiter rather than being marked confirmed.
5. Reply STOP, and check that every sequence for that record ends, including the ones you didn't reply to.

Allow about an hour per sequence. Repeat the relevant checks whenever someone edits a sequence or the ATS renames a field, which is the usual reason reminders suddenly go out with a blank where the venue should be.

A temp desk filling 120 shifts a week

To make the costs concrete, take an agency desk supplying event staff and warehouse temps to about a dozen clients, filling around 120 shifts a week. Before automation, a recruiter texts or calls every booked temp twice to confirm, at about a minute and a half each: six hours a week, plus the time chasing people who don't reply.

With moment 5 automated, the recruiter reads only replies classed CANCELLED, UNSURE, QUESTION or ISSUE, perhaps 25 to 35 a week, at about two minutes each: roughly an hour. That's around five hours a week returned on one desk, and cancellations arrive earlier, when cover is still findable.

Now the pricing trap. Built in Zapier, each shift uses about two sends, one AI classification at 1 to 5 tasks, and one ATS update: call it five tasks per shift, or about 2,600 a month. That's past the 2,000 tasks in Zapier's Team plan ($69 a month billed annually) before you add a single other workflow. At this volume, your ATS's native automation or a credits-based tool is usually the cheaper home, with Zapier kept for low-volume gaps. Run that sum for your own shift numbers before choosing where to build.

The no-show number is the one to watch. Count no-shows per 100 shifts for the four weeks before and the four weeks after; if it doesn't move, look at when the 48-hour message lands and whether UNSURE replies are being called quickly enough. The wider patterns behind reminders are in reducing no-shows with AI reminders, and how much time AI saves a recruitment agency per role puts this alongside the other time savings on a desk.

Signs your follow-ups are annoying candidates

• Opt-outs rising month on month, especially from your regular temps.
• "Who is this?" replies, which mean messages arrive from a number or sender name candidates don't recognise. Use a consistent sender name and introduce the number at registration.
• Reply rates falling on confirmations. Candidates stop reading messages that arrive too often or say too little.
• Complaints about wrong details: a reminder for a shift that was cancelled, or a start time that changed. That's a data problem, usually a sequence reading a stale field.
• Recruiters switching sequences off quietly because they're embarrassed by them. Ask them monthly which message they'd change.

A monthly fifteen-minute review of these five signals, plus a read of twenty random messages as a candidate would see them, keeps the whole system sounding like your agency rather than a machine.

Further reads

• How Recruiters Use AI to Write Candidate Summaries Clients Read — Summaries that turn follow-up answers into client-ready updates.
• AI Screening: Bolt It Onto Your ATS or Switch Systems? — Whether your ATS can carry this or you need another system.
• How to Read AI Software Pricing: Seats, Credits, and Usage Fees — Tasks, credits and seats: how automation pricing adds up.
• Is It Safe to Let AI Reply to Customers on WhatsApp? — The risks of letting AI reply on messaging apps.
• AI CV Screening for Recruitment Agencies: Setup and Safeguards — The screening step that comes before these messages.
• AI for Recruitment Business Development: Winning New Clients — The client side of the desk: winning the jobs to fill.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Bullhorn Automation product pages; Recruit CRM and Manatal pricing pages; Zapier pricing and task-counting help pages; Make pricing. Checked September 2026.