TCPA Compliance for Staffing Agencies: Texting Candidates Without Getting Sued (2026 Guide)

The short answer: recruiting texts are usually not treated like ordinary telemarketing

Most courts have drawn a line between recruitment and telemarketing. That matters because staffing firms often need to text fast, at scale, and across high-churn candidate pipelines.

The practical answer to "is texting job candidates considered telemarketing" is usually no when the message is genuinely about filling a job, coordinating an interview, or moving an applicant through the hiring process. But the legal line gets much thinner once the text starts promoting products, services, or fee-based offerings.

Why staffing and recruiting sits in a gray zone

Recruiting is not a clean retail marketing workflow. The message is often tied to a specific job, a pending interview, or an open requisition. That is why courts have often treated it differently from advertising.

But gray zone does not mean no risk.

Staffing firms still run into trouble when they:

1. Text scraped numbers from Indeed, ZipRecruiter, or LinkedIn without clean sourcing records.
2. Keep sending after a candidate replies STOP.
3. Use the same sender for candidate updates and job-promotion blasts.
4. Add fee-based or product language that turns a recruiting message into advertising.
5. Rely on prerecorded calls or automated voice workflows without ordinary prior express consent.

The issue is not whether the business is "staffing." The issue is what the message is actually doing.

What the major cases are really saying

Several cases shape the recruiting-text analysis:

1. Kale Realty and Reardon v. Uber are often cited for the idea that recruitment-style outreach is not automatically telemarketing.
2. Gerrard v. Acara Solutions and Andersen v. Nexa Mortgage are part of the broader line of cases that separate job-related outreach from classic sales advertising.
3. Dolemba v. Kelly Services is frequently used in the same discussion around recruiting and candidate contact.
4. Loyhayem v. Fraser Financial (9th Cir. 2021) is the important caution flag: prerecorded recruitment still needs ordinary prior express consent.

That last point matters. Even if the content is recruitment-related, the delivery method can still trigger consent requirements.

The lawsuit anchors staffing leaders should know

Joseph v. TrueBlue

Joseph v. TrueBlue is a major anchor because it involved repeated "Job Alert" texts that continued after STOP. The reported settlement figure was about $5 million.

The lesson is not subtle: if a candidate opts out, do not keep sending because the lead is in another list, another queue, or another vendor platform.

Friedman v. Torchmark

Friedman v. Torchmark is a warning about recruitment messages that stop looking like recruiting and start looking like advertising because they reference fees, products, or paid offerings.

If your message talks about a paid course, paid certification, referral product, or other commercial upsell, you are moving away from the safer recruiting lane.

Loyhayem v. Fraser Financial

Loyhayem reinforces a narrow but important rule: prerecorded recruitment is still not free from consent analysis just because the subject matter involves hiring.

If your staffing workflow uses prerecorded voice drops, you need a separate legal review.

Scraped candidate numbers are radioactive for a reason

Recruiters love speed. Compliance teams love provenance. Those two priorities collide when a team uses scraped candidate numbers from job boards or social platforms.

That is where the biggest avoidable mistakes happen.

Scenario 1: a job seeker who never opted in

A staffing coordinator exports a list from a sourcing tool and texts, "We have a warehouse picker role in your area. Reply YES for details."

If the number came from a scraped profile, there may be no defensible evidence that the person consented to receive texts from that recruiter or that sender.

Scenario 2: a candidate who opts out once

A candidate replies STOP to a job alert. A second recruiter at the same firm continues texting from a different number the next day.

That is exactly how an otherwise routine recruiting workflow becomes a complaint file.

When recruiting becomes advertising

Recruitment texts stay on safer ground when they are limited to real openings and candidate coordination.

The risk increases when the text starts promoting:

1. Fee-based placement services.
2. Paid certifications or training programs.
3. Commercial partner products.
4. Generic job blasts that are really lead-generation campaigns.

That is where Friedman v. Torchmark becomes relevant. If you are selling something, even indirectly, you are no longer just recruiting.

10DLC registration for recruiters: no waiver, no special category

There is no special 10DLC fee waiver for recruiters.

That matters because some staffing teams assume recruiting automatically qualifies for a preferred use case. It does not. For most staffing and recruiting programs, the correct classification is usually:

1. Marketing, if the traffic is promotional or job-blast oriented.
2. Mixed, if the messages blend recruiting, updates, and broader outreach.
3. Customer Care or Account Notifications, if the message is truly an applicant-status update, interview reminder, or similar operational communication.

What goes into Marketing or Mixed

1. Mass job blasts.
2. Promotion of openings to large candidate pools.
3. General recruiting outreach that looks like outbound prospecting.

What goes into Customer Care or Account Notifications

1. Interview confirmations.
2. Application status updates.
3. Schedule changes.
4. Candidate onboarding logistics.

The most important rule is simple: your 10DLC classification should match the actual message behavior.

A staffing texting program that is easier to defend

Here is the operating model that tends to hold up better in disputes:

1. Keep recruiting, candidate care, and promotional messages in separate workflows.
2. Do not use scraped lists unless you can document sourcing and permission.
3. Centralize STOP handling across every sender and vendor.
4. Store the exact text shown when the candidate opted in.
5. Audit message purpose before registration, not after a complaint.

Message examples

Safer candidate update

"Hi Jordan, this is Apex Staffing. Your interview with Northside Logistics is confirmed for Thursday at 2 PM. Reply STOP to opt out."

This is a candidate-status message, not a promotional pitch.

Safer recruiting follow-up

"We reviewed your application for the warehouse lead role. Are you still available this week for a call? Reply STOP to opt out."

This stays tied to the hiring process.

Riskier job-blast style message

"We have 20 openings with flexible pay and referral bonuses. Text back now to hear about all current opportunities."

If this is sent at scale to scraped or weakly sourced numbers, it starts to look much more like outbound marketing.

Riskier mixed-purpose message

"Join our recruiter training program and get certified for $299 while also seeing new openings in your area."

Once fees or products enter the message, the recruiting-only argument weakens.

What staffing agencies usually miss

Mistake 1: treating recruiting as a blanket exception

Recruiting is not a free pass. It is a context-specific analysis.

Mistake 2: keeping old candidate data forever

Candidate numbers age out fast. Reassigned-number risk and stale contact records are common.

Mistake 3: ignoring message drift

The first draft of a text may be candidate care, but later revisions add promotions, bonuses, or training offers.

Mistake 4: forgetting prerecorded and automated voice paths

Loyhayem makes clear that recruitment subject matter does not eliminate consent requirements for prerecorded outreach.

Practical compliance checklist for recruiters

Before sending, ask:

1. Is this text genuinely about a job or candidate process?
2. Does the source of the phone number support the send?
3. Are we mixing recruiting with products, fees, or training offers?
4. Have we registered the right 10DLC use case?
5. Does STOP work across every sender, queue, and vendor?
6. Are we using prerecorded calls, and if so, have we cleared consent requirements?

If any answer is unclear, hold the campaign.

Bottom line

TCPA compliance for staffing agencies texting candidates is mostly about discipline, not loopholes. Most courts treat recruitment differently from telemarketing, but scraped numbers, promotional recruiting, STOP failures, and prerecorded outreach still create real exposure.

The safest model is to keep candidate updates in one lane, promotional job blasts in another, and any prerecorded or fee-based messaging under separate legal review.

*Informational only and not legal advice. Confirm final policies, scripts, consent rules, and 10DLC classifications with qualified counsel and your messaging providers.*