Skip to content

Simplified doc page for SMS Messaging Requirements #821

@akalsey

Description

@akalsey

A single landing page that answers "why can't I use my number for SMS and how do I fix it?" Linked from the dashboard phone number search UI.

Audience: New SignalWire users trying to purchase a phone number and discovered SMS is disabled. Assumes no prior knowledge of TCR, 10DLC, or carrier compliance requirements.

What it should cover

  • Why SMS is disabled by default. Carrier compliance requirement, not a SignalWire policy, or something user did wrong.
  • Two paths, clearly distinguished
    • Path 1 — Testing only (Platform Free Trial) For users who just want to verify the API works before committing to registration. Steps: verify a personal mobile number in the Messaging Campaigns dashboard, then purchase a SignalWire number. Covers the constraints upfront: one-to-one sending only, 200 messages/day, [SignalWire Free Trial] prefix on all messages, no SWML/LaML/Call Flow Builder support. Explicit warning that PFT is single-use — releasing either number ends the trial permanently.
    • Path 2 — Production (TCR Registration) Summarize the three steps with links to the full registration guide.
  • One short paragraph noting that toll-free numbers and short codes go through different, separate processes with link to the relevant guides.
  • What to do if you're stuck (support?)
  • Specifically note that if a user accidentally ended their PFT by releasing a number, they need to complete TCR registration — there's no way to restore PFT.

Users hitting this page are blocked and frustrated. Lead with the fix, not the explanation.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions