Troubleshooting

A resident or driver isn't getting texts

Symptom

"Text Resident" or "Text Driver" doesn't seem to reach the person, or the button/option isn't even showing.

No consent on file. A resident needs "📱 OK to text ride reminders" checked on their record; a driver needs "📱 Send trip texts to this person" checked on their staff record. See Turn on text reminders.
No opted-in driver at all. If you see the error "No driver has opted in to texts yet...", add a mobile number and the opt-in checkbox to at least one driver's staff record.
They replied STOP. Recipients can opt out by replying STOP to any message — they'll need to text back a re-subscribe keyword or you'll need to confirm with your carrier/Twilio setup; check with support if unsure.
Daily send cap reached. Each facility has a shared daily cap for texts and voice calls combined (200/day). If you're running a high-volume day, some messages may be delayed until the next day.
Non-US/Canada number. Only US/Canada phone numbers are supported.
Message marked as spam by the recipient's carrier. New toll-free numbers are sometimes flagged "Spam Likely" by default. Ask recipients to save the RideLogger number as a contact (e.g. "RideLogger Dispatch") — this is also the fix for calls landing as "Spam Likely."

Managers and admins (staff/driver consent settings); anyone can check a resident's consent checkbox.