Loading

SMS

Text messaging is documented under Messaging, Letters & Meetings — this page says where each part lives.

SMS is documented in full elsewhere, because text messaging shares its providers, accounts, consent model and logs with WhatsApp and letters. Splitting it across two categories meant the same ground covered twice and neither copy complete.

This page says where each part lives.

Where to find it

Architect Panel → Communication:

  • SMS & WhatsApp Accounts — the accounts messages are sent through
  • Message Opt-Outs — consent and suppression
  • Message Log — what was sent

Architect Panel → Activity:

  • SMS Log — individual sends and their provider identifiers

Sending text messages

Under Messaging, Letters & Meetings:

  • Connecting a Messaging Provider — the drivers, accounts and credentials.
  • Sending Messages and What They Cost — how sends work, message length and billing, and the sender name.
  • Opt-Outs and Suppression — consent, opt-out handling and the do-not-send list.

Receiving them

Also under Messaging: Receiving and Routing Messages and Two-Way Conversations, which cover inbound texts and replies.

SMS for sign-in and password reset

Those are authentication rather than messaging, so they sit under Security:

  • SMS Codes — the second-factor settings, including the code validity window and the sender name.
  • E-mail or SMS — choosing the password reset channel, and why the reset channel should differ from the second factor.

Campaigns by SMS

Under CRM: campaigns send by e-mail, SMS or WhatsApp from the same segments, with topic-level consent that holds across every channel.

Reading the log

Under Logging: Reading the SMS Log covers the provider identifiers you need to trace a message somebody says never arrived.

Why it is arranged this way

SMS is a delivery channel rather than a feature. The account, the consent record and the log are shared with WhatsApp; the second-factor use is an authentication decision; the campaign use is a marketing one. Documenting the channel once and referencing it from each context keeps those consistent.

Worked example

An organisation setting up text messaging reads the provider article to connect an account, the consent article before its first campaign, and the Security articles when deciding whether to offer SMS as a second factor. Three different decisions, three different places, one channel underneath.

Recommendations

  • Start with Connecting a Messaging Provider if you are setting up.
  • Read Opt-Outs and Suppression before any bulk send.
  • Treat the 2FA use separately — it is an authentication decision.
  • Keep the SMS log identifiers — they are the only route to a real answer from a provider.