SMS-capable Terri numbers receive inbound texts so humans can see OTP and alert traffic without changing voice.
When SMS is enabled on a Terri number, Twilio delivers inbound texts to Terri's messaging webhook. Each message is logged with its full body for the owning account. Numbers are provisioned voice-only by default; SMS receive is enabled later on that DID. MMS media download is not supported.
Inbound texts — including one-time passcodes and short alerts — are surfaced to a configured human alert path with the full message body. The goal is that a person can read what arrived on the DID, not that software invents a reply.
The public inbound SMS webhook does not run the voice agent and does not auto-reply to strangers. Replies are only START/HELP on the public program number, or a hold-request thread on an SMS-capable business DID. Carrier opt-in and HELP/STOP terms for the public program number live at /sms — that page is not this product guide.
If SMS is enabled on the business DID, a caller can text a hold request. Terri replies with the same open times the public /book page shows, then a manage link after they pick a time. There is no stranger auto-reply outside that thread, no marketing blast, and STOP still cancels texts. This is not a chat product.
Enabling SMS sets the number's SMS webhook only. VoiceUrl is never rewritten, so inbound and outbound voice keep working the same way after SMS is turned on.
This product doc does not claim outbound marketing blasts, mass campaigns, or MMS. Inbound receive and the owner alert are the customer SMS product. Carrier program terms are on /sms.