Docs: update A2P SMS consent guidance for Twilio compliance (BREW-2794)

[haleyserrano]

Summary

Updates the US SMS/A2P registration help content to reflect the Twilio compliance fixes shipped in BREW-2794 ("Update the A2P Campaign template based on Fast Track feedback").

JIRA: BREW-2794 (Done, resolved 2026-07-23)
Repo targeted: Business App (end-user facing)
Classification: UI/UX change + feature behavior change (A2P campaign registration consent flows)

What changed and why

Per the ticket, three end-user-visible behaviors changed:

1. The registration form no longer asks "How will you use SMS?" — every campaign now automatically covers both transactional and marketing messaging (confirmed in ticket comment, deployed to production, verified against live campaign registrations).
2. Verbal consent scripts must now separately confirm transactional and marketing consent, reference the HELP keyword, include privacy policy/terms links, and — because marketing consent requires proof in writing — verbal marketing agreement must be followed by a written (SMS) confirmation before marketing messages begin (double opt-in).
3. The AI Chat Receptionist consent prompt and website chat widget must give the customer a clear way to decline (not just "reply yes"), alongside privacy policy and terms links.

Files updated

• docusaurus/docs/business-app/conversations/sms/us-businesses-sms-registration.mdx
  • "Understanding brand and campaign" — campaign now always covers both message types
  • "Types of SMS messaging" — removed the "choose transactional, marketing, or both" framing
  • "Other consent methods" — added the verbal-script and chat-widget compliance requirements
• docusaurus/docs/business-app/administration/sms_configuration.md
  • Step 4 "Enable AI chat consent" — updated the quoted AI consent script to include the decline option and privacy policy/terms links that were missing before this fix

No new pages were created — existing docs already covered A2P registration, brand/campaign, and consent in detail, so this fix was placed inline in the existing sections it changes.

Acceptance criteria coverage

The ticket has no formal acceptance criteria checklist; the description lists 4 backend fixes (kickoffRegistrationWorkflow.go) and 2 frontend guidance updates. Documentation coverage:

• ✅ Use-case mismatch fix (always transactional + marketing) — documented
• ✅ Verbal consent script requirements (HELP keyword, policy links, double opt-in for marketing) — documented
• ✅ Widget/AI consent prompt decline option + policy links — documented
• ⚠️ Webform message-flow description change and "Galaxy registration form i18n" webform help-text wording — these are internal/carrier-submission copy and existing form-facing copy already documents the required webform checkboxes and disclosures; no separate business-facing doc change was needed beyond what's listed above.

Figma / images

None provided on this ticket; no visual assets were used.

Skills used

• pre-push-validation — frontmatter, tag balance, and link checks on both edited files (passed)
• style-review — ran the automated scan-style.sh scan on both files (no new violations introduced; one pre-existing unrelated flag on an unmodified line was verified and left as-is)

Assumptions and limitations

• Epic not Done: The parent epic (BREW-2733, "A2P Revisions") is still "In Progress." Its only open sibling ticket (BREW-2809, "Write up A2P Business App Documentation") is itself a documentation story, not a feature-flag/eligibility/rollout gate, so this was not treated as a hold signal. BREW-2794 itself is Done, with comments confirming the fix is deployed to production and verified against live campaign registrations.
• Reviewer: GitHub access for this session is scoped to the businessapp-docs and partnercenter-docs repos only, so the code repos where the actual PRs for this ticket live (kickoffRegistrationWorkflow.go, Galaxy frontend) could not be inspected, and no GitHub handle could be confidently matched to the ticket assignee (Rodrigo Vasquez) without risking mistagging an unrelated account. No reviewer was set as a result — please assign manually.
• Not addressed here (out of scope for this ticket): BREW-2809 is a dedicated, separate "To Do" story to rework these same pages for audience-fit/skimmability. This PR only corrects content that is now factually stale because of BREW-2794's shipped changes — it does not attempt that larger rework.
• Partner Center docs were checked and do not require updates: the only SMS registration content mirrored there covers an unrelated "Unified SMS Numbers" topic, not the A2P consent/campaign flows this ticket touched.

@ahnikakuse @haleyserrano @maryam6samadi

---

Generated by Claude Code