A manager posts a schedule. Half the team doesn't open the app. Someone calls out sick at 6 AM and the manager starts texting people from a personal phone. If that sounds familiar, your customers are already texting. They're just doing it outside your software, with no log, no consent record and no way to stop a message from going to the wrong person.

This guide is for the product team at an HR, workforce or shift scheduling product. We'll cover which texts to send, why consent works differently for employees, how to build open-shift offers, STOP handling, quiet hours and a sender per employer. All scenarios are made up for illustration.

Texts that fit scheduling

Start with what your platform already knows:

  • Schedule published. "Your schedule for next week is posted."
  • Shift reminder. A short note before a shift starts.
  • Shift change. Time moved, location changed, shift canceled.
  • Open shift offer. "A shift opened Saturday 10 to 4. Reply YES to take it."
  • Swap approved or declined.
  • Time-off decision.
  • Onboarding tasks. Paperwork due, training to complete.

Keep pay, performance, discipline, medical leave and benefits out of texts. A text like "You have an update in your account" is fine. Details belong behind a login. Ready isn't HIPAA compliant and doesn't sign BAAs, so keep health information, including the reason for a sick call or a leave, out of every message.

Consent for employees is its own topic

An employer can require staff to use a scheduling tool. Texting a personal phone is different. Treat texts as something the employee opts into, with a clear, specific agreement.

A pattern that works at onboarding or first login:

  1. A phone number field, with a short explanation: "Get shift alerts by text."
  2. An unchecked box naming the employer, the types of messages (shift reminders, schedule changes and open-shift offers), that message and data rates may apply, roughly how often and that replying STOP ends texts.
  3. A stored record: who, when, wording and the screen they used.
  4. An easy way to turn texts back on or off in settings.

Consent to schedule alerts isn't consent to company announcements, promotions or surveys. Keep purposes separate. Employment law varies by state and country, so have counsel review the wording for your market. This is the technical outline, not legal advice.

On the send, set consent_attested to true only when your record supports it. Ready logs the attestation (who sent, to how many, when) but doesn't keep each person's wording or opt-in time, so your database holds that. Our consent record schema for developers lists the columns. From January 20, 2027 (UTC), an API send without consent_attested is refused with a 403; until then it goes out with a warning and no attestation.

An open-shift offer, end to end

Open-shift offers are where texting earns its keep, and where logic needs care.

  1. A call-out creates an open shift in your system.
  2. Your platform selects eligible employees (qualified, not in overtime, opted in to texts) and sends each a message.
  3. Replies arrive at your webhook. The first valid YES wins the shift. Later YES replies get a polite "that shift was filled."

A send looks like this, with a made-up number:

POST /v1/messages
X-API-Key: <key>
Idempotency-Key: <one UUID per message>

{"to": "+12125550199", "body": "Example Cafe: open shift Sat 10 AM to 4 PM. Reply YES to take it. Reply STOP to opt out.", "consent_attested": true}

Details that bite:

  • Race conditions. Two people reply YES within seconds. Make the claim atomic in your database, and decide the winner there, not in the order messages arrive.
  • Duplicates. Send an Idempotency-Key, one UUID per message, reused on every retry, so a retry never texts the same person twice. See idempotency for duplicate texts.
  • Reply parsing. "yes", "Yes!" and "yep" will all show up. Normalize the case and punctuation, and send anything ambiguous to a human or ask once more.
  • Verify the sender. Match the replying number to an employee eligible for that shift before booking anything.

For a message to a small pool, POST /v1/messages/bulk takes up to 100 recipients per call. Our post on receiving inbound texts with webhooks covers the receiving side, and the endpoint docs are at https://docs.tryready.com/api/messages.

Segments count too. A plain segment is 160 characters, 153 per part when longer, and an emoji drops it to 70. Ready adds "Reply STOP to opt out" and the business name to the first text to each contact unless the account turns it off. See the segment counter post.

STOP means STOP, even for shifts

An employee replies STOP to a shift alert. A manager may still need that person to know about a schedule change. The product answer isn't to keep texting; it's to route around the opt-out.

  • Ready blocks further texts to a number that replied STOP, UNSUBSCRIBE or a clear phrase such as "please stop texting me."
  • Read the state with GET /v1/opt-outs and GET /v1/opt-outs/:phone.
  • Show the manager a "texts off" marker on that employee, and fall back to push, email or a note on the posted schedule.
  • Never let a manager flip texts back on for someone. Only the employee, through a recorded action, can.

A STOP always blocks the number in the sub-account that received it. Whether it also blocks the parent and other sub-accounts is decided by Ready, so check the per-number endpoint for the rest. More in handling SMS opt-outs.

Quiet hours versus 6 AM call-outs

Scheduling software lives in early mornings and late nights, exactly the hours texting rules protect. Ready enforces quiet hours by the recipient's area. A campaign or automation waits up to 24 hours for the window. An API text is held only if the window opens within 6 hours; otherwise it isn't sent, and your code sends it again once the window opens. Your product should handle both outcomes openly.

Practical design choices:

  • Publish schedules and send routine reminders at sensible daytime hours.
  • When a refusal comes back for an urgent open shift, tell the manager in plain words ("couldn't text Sam until 8 AM") and let them phone.
  • Treat a reply as a window: someone who texted in the last 24 hours can get a response at any hour.

See handling the quiet hours 409 and quiet hours across time zones for the details.

One sender per employer

Your customers are separate companies. A restaurant group's open-shift texts shouldn't share a number or a registration with a staffing agency's. Ready's sub-accounts give each employer its own numbers and carrier registration (10DLC), created through the API. Registration needs an EIN, and most approvals take 2 to 7 days. Plan for it in onboarding. If you serve staffing agencies, each agency client may need its own sender too, so decide the tenancy model early. Our multi-tenant SMS architecture post goes through the tradeoffs, and the vertical SaaS onboarding post covers sequencing.

FAQ

Can managers text staff from a personal number? That sidesteps the consent record and the log. Offer a way to text from the platform.

Do we need the employee's reply to start? No, consent can be captured at onboarding if it's specific and recorded.

How should we price this for customers? Ready bills per segment plus a carrier fee, itemized, on the pricing page. Decide whether you pass that through or bundle it.

The practical takeaway

Begin with schedule-change and shift-reminder texts, recorded consent, safe retries and a sender per employer. Add open-shift offers once those are solid. When you want to try the API, sign up and send from a test key.