To add candidate texting to an ATS or recruiting product, collect clear text-message consent on the application form, send through a REST API with that consent attested, let STOP be handled automatically, and respect quiet hours in the candidate's time zone. Then give each employer or agency its own sender, so one customer's mistakes don't land on another's numbers.
Candidates read texts quickly and ignore voicemail, which is why recruiters want the channel. But recruiting is also a place where the rules are easy to get wrong: a person who applied for one job didn't agree to a marketing campaign, and a late-night "interview tomorrow?" text can become a complaint. This guide covers the consent, STOP, timing and tenancy decisions for a platform builder. Message templates for recruiters themselves are in our post on recruiting text messages.
Where texting fits in a hiring workflow
Think in events your ATS already has, then decide which ones deserve a text.
- Application received. A short acknowledgement, if the candidate agreed to texts.
- Screening or assessment link. Time-sensitive, short and one link at most.
- Interview scheduling and reminders. The highest-value use. A reminder the morning of an interview can cut no-shows, though we won't quote a figure here.
- Status update. "Your application moved to the next step."
- Offer or onboarding paperwork reminders.
Not every stage should text. Rejections are better delivered another way, and anything containing sensitive personal information belongs in a logged-in page, not a text. Also keep health information out of texts entirely. Ready isn't HIPAA compliant and doesn't sign BAAs, and an occupational health or drug-screening step shouldn't put results or conditions in a message.
Consent at the point of application
The key rule: the candidate has to agree to receive texts, and the agreement has to be easy to find, specific and separate from accepting the general terms.
A workable pattern on the application form:
- A phone number field marked as optional or required, as your workflow demands.
- An unchecked checkbox beside it with the agreement in plain words: who will text (the employer or the staffing firm, by name), what kind of messages (application updates and interview scheduling), that message and data rates may apply, roughly how often, and that replying STOP ends texts.
- A link to the privacy policy and terms that apply.
- A stored record of what the candidate agreed to.
Point 4 is on you. When you set consent_attested on a send, Ready records your attestation (who sent, to how many, when), but it isn't a per-contact consent record. Ready stores no recipient opt-in time, wording or page URL, so keep the candidate's agreement in your own database, tied to the application. A sign-up on a Ready-hosted opt-in page is stored per contact, but an ATS form is your own page. Our post on a consent record schema for developers lays out the columns we'd keep, and documenting SMS consent covers retention.
Two cautions. Consent for application updates isn't consent for promotions. If an employer wants to text candidates about other openings later, collect that agreement separately. And a candidate who came from a purchased or scraped list hasn't agreed to anything. We don't coach texting those, and the acceptable use policy bars it.
Sending a candidate text
A send is one call. This is the request shape from Ready's API, with a made-up number:
POST /v1/messages
X-API-Key: <key>
Idempotency-Key: <one UUID per message>
{"to": "+12125550199", "body": "Hi there, your interview with Example Staffing is tomorrow at 10:00. Reply STOP to opt out.", "consent_attested": true} Send an Idempotency-Key header, one UUID per message and reused on every retry, so a retried request doesn't text a candidate twice. Set consent_attested only when your stored record says the candidate agreed. Unless the account turns it off, Ready adds "Reply STOP to opt out" and the business name to the first text to each contact and again from time to time, so budget those characters. Messages are billed by segment: 160 characters in a plain-text segment, 153 for each part of a longer one, and 70 when an emoji is in the text. Our segment counter post shows how to check this before you send. The docs for the endpoint are at https://docs.tryready.com/api/messages.
For a message to many candidates, such as a hiring event, POST /v1/messages/bulk takes a list, with a cap of 100 recipients per call.
STOP handling
When a candidate replies STOP or UNSUBSCRIBE, Ready honors it, and the opt-out propagates so the contact can't be messaged again across campaigns. Clear phrases such as "please stop texting me" or "take me off" are caught too. A STOP always blocks that number in the sub-account that received it. Whether it also blocks the parent and other sub-accounts follows a Ready setting, so for the rest, check GET /v1/opt-outs/:phone.
What your ATS should do with it:
- Read opt-outs back.
GET /v1/opt-outslists opted-out contacts on the account, andGET /v1/opt-outs/:phonechecks one number. The plain list leaves out a few cases, such as a STOP from a deleted contact, so use?scope=allor the per-number check where it counts. See the opt-outs docs. - Show it in the candidate record. A recruiter should see "texts off" before typing a message, not find out from a refusal.
- Switch the workflow to email. An opted-out candidate still needs interview details.
- Don't re-add them. A candidate who reapplies with the same number hasn't re-consented to texts unless they tick the box again, and the opt-out still applies. Handling SMS opt-outs goes into the sync problem.
Quiet hours and candidate time zones
Candidates apply from everywhere, and a recruiter's morning is a candidate's night. Ready enforces quiet hours by the recipient's area. How a held text behaves depends on how it was sent:
| Send path | In quiet hours |
|---|---|
| Campaigns, drip campaigns, automations | Wait up to 24 hours for the window |
| A text typed in the app to one person | Scheduled for the recipient's next allowed time |
| API text | Held only if the window opens within 6 hours; otherwise the API answers 409 QUIET_HOURS_BLOCK and nothing is sent |
API text with hold_until_allowed: true | Held up to 24 hours, like a campaign text |
| Reply to someone who texted the account in the last 24 hours | Goes out at any hour |
For an ATS, the clean approach is to expect the 409, then queue the message in your own system until the window opens, or pass hold_until_allowed. If you schedule reminders, remember that the time you pick and the candidate's local time are not the same thing; see SMS scheduling, time zones and DST bugs. For the legal side of calling hours, TCPA calling hours by state is the reference.
One sender per employer or agency
Recruiting software is multi-tenant by nature. Staffing agencies and employers are separate senders with separate reputations. Ready gives each customer a sub-account with its own numbers and its own carrier registration (10DLC). You create one with POST /v1/sub-accounts and register it through the registration endpoints (sub-accounts docs, registration docs).
Registration is $25 a month per customer, covering the brand and its first campaign, and $2 a month per number. Most approvals take 2 to 7 days. Ready registers businesses with an EIN only, so a solo recruiter without one needs an EIN first. The registration use case must match the real messages, so describe candidate communications honestly. Our multi-tenant SMS architecture post covers the data model.
Frequently asked questions
Can I text a candidate after they applied online?
Only if they agreed to texts, and the agreement should say so in words on the form. A phone number on a resume isn't the same as agreeing to be texted.
What happens when a candidate replies STOP?
Ready honors it automatically and blocks that number in the sub-account that received it. Your app should read the opt-out, show it to the recruiter and move the candidate to email.
Do I need separate consent for job alerts?
Yes. Consent to hear about an application isn't consent to marketing. Collect it separately, and keep its own record.
Is this legal advice?
No. Compliance is the sender's responsibility, and Ready's tools reduce risk without removing it. Have counsel review your consent language.
Where to start
Add the consent checkbox and the stored record first, since nothing else works without them. Then wire interview reminders, because they have the clearest payoff, and show opt-outs in the candidate view. When you're ready to test sends, the API quickstart and pricing are the next two pages to open.