And i’m trying to keep participants engaged without pinging them to exhaustion — this spring we tested REDCap + Twilio for weekly ePRO texts with optional voice notes. It helped completion and felt kinder, but consent language and multilingual access are still clunky; what tools or settings have helped you keep two‑way communication warm, secure, and clear?
Since you’re on weekly REDCap+Twilio, turn on REDCap’s Multi-Language Management and front-load a one-liner like “We’ll text weekly; reply STOP to opt out” to clean up consent in every language… For warmer two-way without exposing staff numbers, route replies via Twilio Proxy (Proxy: One-to-one Masked Communications | Twilio) and map simple keywords — “1” for a voice note, “9” for a question; would that cover your multilingual flow without extra burden?
Building on @sthomp48, wire your Twilio number to a Studio flow so replies trigger friendly, bilingual canned responses (HELP/AYUDA, CALL/LLAMAR) and anything else forwards to a monitored inbox, which keeps two‑way warm without opening PHI in SMS… In REDCap, use a [lang] field to branch Alerts & Notifications so your “weekly ePRO texts” go out in the right language and add a first‑day footer like “no PHI by text; we’ll call if needed.” If “optional voice notes” are key, add a TTS call fallback after 24h for non‑responders during business hours.