For volunteer management software, text shift reminders, last-minute fill-in requests and quick confirmations from each organization's own sub-account and number. Use two-way replies for yes or no answers, send only to volunteers who agreed, and keep each organization's opt-outs separate.

Volunteers aren't employees. They give their time between other things, so they respond to short, specific texts and ignore long ones. A reminder the night before cuts no-shows, and a fill-in request can fill an empty shift in minutes. See SMS API for HR and shift scheduling software for the staffing version of this problem.

Messages

MomentTextReply
Signed upShift details and a how-to-cancel lineNone
Day before"Reminder: food drive Sat 9 AM at Example Pantry. Reply Y to confirm or N to cancel."Y or N
Short on volunteers"We need 2 more for Sat 9 AM. Reply YES if you can come."YES
After shiftThanks and the next opportunityNone

Treat the first reply as the source of truth and ignore later noise. Parse only Y, N and YES in code. Send everything else to a coordinator. Two-way keyword routing covers the safe pattern.

Building it

  1. Sub-account per organization via POST /v1/sub-accounts.
  2. Register each organization through the registration API. Ready registers businesses with an EIN. Most approvals take 2 to 7 days.
  3. A number per organization, $2 a month.
  4. Fill-in requests go through POST /v1/messages/bulk to a short list of qualified volunteers, at most 100 numbers per call. Cap the size, so you don't over-fill a shift.
  5. First-come logic. Lock the shift in your database when the first YES arrives, and send a short "thanks, it's covered" to late repliers.

Consent

Capture agreement on the volunteer signup form, naming the organization, the types of texts and how to stop. Store the record in your own data. Ready keeps no per-contact consent record for API sends. A STOP blocks that number in the sub-account that received it, so show coordinators who has opted out. See SMS consent language that passes registration.

Minors

If your volunteers include minors, be careful: get a parent's or guardian's agreement before texting, and keep messages simple. Check the rules that apply to your organizations.

Cost

A pantry with 60 volunteers, getting a reminder and one request a week, sends about 120 segments a week. That's 120 × ($0.0075 + $0.0045). Replies bill too, at $0.0075 plus the $0.003 received carrier fee. These are assumptions.

Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.

Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.

Frequently asked questions

What if two volunteers reply YES at once? Use a database lock so one wins, and send the other a polite note.

Can I text outside quiet hours for urgent shifts? A reply to someone who texted in the last 24 hours can go out at any hour. A first text follows quiet hours rules.

Do I need a number per event? No. One number per organization is typical, and it keeps recognition steady for volunteers.

Next step

Build the day-before reminder with Y or N replies first. It teaches your team the whole send and reply loop.