SMS setup

Business texting rides your existing trunk numbers: enable SMS on a trunk and its DIDs can send and receive texts, which land in the same Chat workspace as internal messages.

Enabling SMS on a trunk

Open the trunk (Admin → Trunks) — an SMS tab appears when the provider's template supports messaging (Telnyx has first-class support; several other providers work through the generic driver, and the generic trunk templates include an SMS section you can use with compatible carriers). Flip Enable SMS and fill in the provider fields the template asks for — typically an API key, which is stored encrypted and never redisplayed.

Registering the webhook

Inbound texts arrive by webhook. The SMS tab shows your system's webhook URL (with a copy button) — paste it into the provider's messaging configuration (for Telnyx: the messaging profile attached to your numbers). The URL embeds a secret token; the Regenerate button rotates it, after which the provider must be updated with the new URL.

Choosing which numbers text

With trunk SMS enabled, the main number and DIDs are text-capable by default; each DID row on the DID Numbers tab has an SMS checkbox to switch individual numbers off. Which user or team receives a number's texts is decided by your SMS routing.

Also set the trunk's SMS fallback destination — where a text lands when routing resolves to something that can't hold a conversation (an IVR, say). Unset, such messages are only logged.

Testing

Text one of your DIDs from a mobile: it should appear in Chat for the routed user (or all members of a routed group). Reply from the conversation — delivery ticks confirm the provider accepted it (one tick sent, two delivered, red on failure).