Summary
SMS settings appear to be the main admin surface for making SMS workflows actually runnable. The current app suggests two core setup responsibilities here:- define the organization phone number used for SMS-related behavior
- create or update the provider credentials used to send messages
Who this is for
Owners, admins, and technical operators responsible for account setup and governance.Where to find it
- Settings → SMS
What the current settings page suggests
Organization-level phone configuration
The page includes an organization-level phone number field, which means admins should think of this page as both branding and infrastructure setup.Provider credentials
The page also appears to support creating or editing an SMS provider integration using account credentials. That means SMS setup is not complete until both the visible number and the hidden provider connection are correct. The current product flow specifically suggests a Twilio-style provider path, with either token-based or key/secret credential styles. That means SMS setup is both a provider decision and a credentials-format decision.Recommended setup order
- confirm which team should own SMS setup
- set the organization phone number correctly
- configure provider credentials
- validate that the team understands which credential method is active
- verify contact phone data quality before trusting live workflows
What “SMS ready” should mean here
- the organization number is correct
- the provider integration exists and saves successfully
- the team knows which credentials are in use
- contact phone fields are good enough for real use
- campaign owners understand SMS is short-form and infrastructure-sensitive
Common mistakes
- saving the visible phone number but forgetting provider setup
- assuming provider credentials alone are enough without the right originating number
- overlooking contact phone quality until campaign launch
- treating SMS like a lighter version of email instead of a channel with its own constraints
Verification checklist
- A valid organization phone number is saved.
- Provider credentials are created or updated successfully.
- The team knows SMS workflows may still fail if contact phone data is missing or incorrect.
- The team knows whether the provider uses token-based or key/secret credentials.