Skip to content
All posts
Messaging· 5 min read· Apex ATS Team

Message templates that don't sound like templates

Templates save hours, but candidates can smell a form letter. How to write saved messages that read like a person wrote them, because one did.

A recruiter handling 60 open conversations cannot write every message from scratch, and should not try. Templates are the right tool. The problem is that most template libraries were written by someone imagining a brochure, not a text thread, and candidates can tell. "Dear Applicant, we are pleased to inform you" reads like a rejection even when it is an interview invite. This post is about writing templates that do the work of a template while sounding like the person sending them.

Why templates sound like templates

It is rarely the fact of the template that gives it away. It is a handful of habits that show up over and over:

  • Corporate register. "We are pleased to inform you that your application has been reviewed" is not how anyone talks.
  • Explaining the company instead of the next step. The candidate applied. They know who you are. They want to know what happens now.
  • Length. A text that scrolls is a text that gets skimmed.
  • Fake warmth. "We hope this message finds you well!" is filler that signals nobody is on the other end.
  • Merge fields used as decoration. Inserting the candidate's first name three times does not make it personal. It makes it creepy.

Write for one person, then save it

The best templates start as real messages. Next time you write something good to one candidate, save it. Strip out the specifics that will change, keep the voice. Some principles that hold up:

  1. 01Open with who you are and why you are writing, in one line. "Hi Jordan, Sam from Northgate here about your warehouse application."
  2. 02Say the one thing. Interview time, missing document, next step, whatever it is. One message, one purpose.
  3. 03End with a question or a clear action. "Does Thursday at 2 work?" gets a reply. "Please let us know your availability at your earliest convenience" gets silence.
  4. 04Use contractions. You use them when you talk. Use them when you write.
  5. 05Read it out loud. If you would not say it to someone standing in front of you, cut it.

Merge fields that earn their place

Apex ATS templates can pull anything from the applicant record and the job: first name, job title, location, interview time, recruiter name, the self-scheduling link. The useful ones are the ones that change what the message means, not the ones that add sparkle. First name, once, at the top. Job title, so a candidate who applied to four of your jobs knows which one this is. The specific date, time and place. The recruiter's actual name and number. That is usually the full list.

One caution: a merge field that might be empty will produce a message like "Hi , thanks for applying to ." Set fallbacks for every field, and preview before bulk sending. A single bad send to 200 people undoes a lot of careful writing.

Before and after

Before: "Dear {{first_name}}, Thank you for your interest in the {{job_title}} position with {{company}}. We have reviewed your application and would like to invite you to participate in a phone screening interview. Please reply to this message with your availability over the next several business days so that we may schedule a mutually convenient time. We look forward to speaking with you. Best regards, The {{company}} Recruiting Team."

After: "Hi {{first_name}}, this is {{recruiter_name}} with {{company}}. I read your application for the {{job_title}} role and I'd like to set up a 15-minute call. Pick any time that works here: {{schedule_link}}. Questions before then, just text me back."

Same information, 40 percent of the words, and it invites a reply instead of an availability essay. The self-scheduling link also removes the back-and-forth entirely. The candidate picks a slot, it lands on the recruiter's calendar, and the confirmation goes out automatically.

The test I use is simple. Would I be embarrassed if the candidate saw the template name at the top? If the answer is yes, the template is not finished.

Recruiting team lead, illustrative

Keep the library small

A team with 80 templates uses 8 of them and rewrites the rest every time. Start with the messages every candidate gets: application received, screen invite, interview confirmation, reminder, missing document, offer next steps, not moving forward. Seven or eight, written well, in the same voice. Add a template only when the same message has been typed from scratch three times. Review the whole set once a quarter and delete anything that has not been sent in 90 days. If a template gets edited before sending more than half the time, the template is wrong, not the recruiters.

Templates are a writing task, not a settings task. Spend an afternoon on them once, in the voice of your best recruiter, and every message your team sends for the next year gets a little better. Candidates will not notice that you used a template. They will notice that you answered fast and sounded like a human. That is exactly the outcome you want.

#templates#SMS#email#candidate experience#messaging

Keep reading

See it live

Fifteen minutes, your own job post.

We load one of your open roles into Apex on the call, run a real resume through the parser and text a test applicant. No slides.