Why recruiters love texting — and why that's the risk

Text messages get read. A recruiting email might sit unopened for three days; a text is usually read within minutes. For scheduling interviews, nudging a quiet candidate, or confirming a start date, SMS is the highest-response channel a recruiter has. That is exactly why so many teams have wired automated texting into their process — and exactly why so many of them are sitting on legal exposure they don't know about.

Automated and bulk recruiting texts fall under the Telephone Consumer Protection Act (TCPA) and related state laws. The TCPA's defining feature is statutory damages assessed per message — a fixed dollar amount per text, with no need for the recipient to prove they were harmed, and a multiplier for willful violations. Multiply a per-text penalty by a blast to a few thousand phone numbers and you understand why recruiting-text class actions are a real category. This is a recruiter-and-HR working guide, not legal advice — TCPA litigation is fast-moving and the state-law overlay is genuinely complex, so run your texting program past counsel before you scale it.

Consent is the whole game

The TCPA is, at its core, a consent statute. The riskiest texts are the ones sent to people who never agreed to be texted using automated technology. So the entire compliance posture comes down to a few questions you must be able to answer for every number you message:

  • Did this person give us their mobile number for this purpose? A candidate who applies and provides their cell number, knowing they're in a hiring process, is in a very different position than someone whose number you bought, scraped, or pulled from a resume database they didn't submit to you.
  • Can we prove it? Consent you can't document is consent you don't have, in practice. The defensible posture is a logged record of when and how each person provided their number and agreed to texts.
  • Is this an automated/bulk send or a genuine one-to-one message? A recruiter typing a single personal text from their own phone to one candidate is a different risk profile than a platform firing templated messages to a list. The automated, scaled sends are where TCPA exposure concentrates.

The safest design is express, documented opt-in for recruiting texts, captured at the point a candidate gives you their number, with the purpose stated plainly.

The rules that turn a good program into a defensible one

Beyond consent, a few operational rules separate a clean texting program from a liability:

  • Honor opt-outs instantly and permanently. If someone replies STOP — or says "please don't text me" in any clear way — texting must end immediately and that number must be suppressed across your whole system, not just for one campaign. A re-text after an opt-out is one of the easiest violations to prove.
  • Respect quiet hours. There are time-of-day windows during which marketing-style messages shouldn't go out, generally interpreted against the recipient's local time. Blasting candidates at 11pm is both bad recruiting and avoidable risk.
  • Identify yourself. Every text should make clear who's contacting them and why. "Hi, this is Dana from [Company] about your application" is both more effective and more defensible than an anonymous nudge.
  • Mind the state overlay. Several states have their own telemarketing and texting statutes that are stricter than federal law, including their own consent and registration rules. If you recruit across state lines, you inherit all of them — the same multistate-complexity problem covered in hiring across state lines.

Texts versus templates: pick the channel for the moment

Texting isn't the right tool for every recruiting touch, and treating it as a one-size channel is how programs drift into spam (and into risk). A useful split:

  • Transactional, expected, consented touches — interview confirmations, "running five minutes late," "here's the parking info" — are where SMS shines and where consent is usually cleanest, because the candidate gave you the number for exactly this.
  • Outbound sourcing and cold outreach belong in channels built for it, like the structured recruiter outreach email templates and the cold-contact discipline in sourcing passive candidates — not in unconsented automated texts to numbers you scraped.

Matching the channel to the moment isn't just compliance; it's the candidate experience difference between feeling cared for and feeling hunted.

A small-team checklist that keeps texting clean

  • Capture consent at the source — when the candidate gives you their number, with the purpose stated — and log it.
  • Suppress opt-outs globally and forever, the instant they happen.
  • Send within quiet-hour windows based on the candidate's location.
  • Keep automated blasts narrow and consented; use real one-to-one texting for anything outside clear opt-in.
  • Document everything — consent, opt-outs, message logs — the same retention discipline you apply to the rest of hiring in recruiting records retention.

Where the product fits

In Hosting HR, candidate contact lives alongside the consent and history that make it defensible: a candidate's communications, their interview schedule, and their status are in one record, so a confirmation text is tied to a real, consented relationship rather than a number floating in a spreadsheet. The system favors transactional, expected touches — interview reminders and scheduling — over untargeted blasts, which is both better recruiting and a smaller legal surface. Texting candidates is one of the highest-leverage tools a recruiter has. It's also one of the few where a careless send is priced by the message. Get the consent and the opt-outs right, and you get the response rate without the class action.