Docs: A2P exemplar site link in SMS registration form (BREW-2853)

[haleyserrano]

JIRA

BREW-2853: Demonstrate to Customers what good A2P looks like (Done)
Subtask: BREW-2854: Add link to the A2P Exemplar site to the A2P form (Done, 2 merged PRs)

Classification

• Type: UI / UX change (small addition to an existing form)
• Product impacted: Business App only. This is an end-user (business owner) experience change to their own SMS/A2P registration form — it does not touch a partner-facing, reseller, or agency workflow, so it does not meet the criteria for a Partner Center repo update.
• Repo targeted by this PR: Business App

Summary of documentation updates

Added a short callout to the two existing articles that document the A2P 10DLC SMS registration form, noting that the form now includes a link to an example website demonstrating a compliant contact form, privacy policy, and terms of service:

• docusaurus/docs/business-app/administration/sms_configuration.md
• docusaurus/docs/business-app/conversations/sms/us-businesses-sms-registration.mdx

Existing vs. new docs

Updated existing docs only — no new page was created. Both articles already fully document the registration form and the website compliance requirements (privacy policy, terms of service, opt-in consent) the exemplar site is meant to illustrate, so a short callout in each was the natural fit. (Note: these two articles cover substantially overlapping ground already; that's a pre-existing duplication in the repo, not something introduced by this change.)

Placement reasoning

Both edits sit immediately after the step that describes opening/filling out the registration form, since that's where a reader would notice the new link in the actual product UI.

Acceptance criteria coverage

The parent story's acceptance criteria (contact form, privacy policy, terms of service exemplar) are represented at the level of detail available — see Assumptions/Limitations below.

Figma / images

None were provided with this ticket. No visual assets were available to verify the exact UI placement or copy of the link.

Skills used

• pre-push-validation (frontmatter, tag balance, and link checks passed on both modified files)

Assumptions / limitations

• No Figma links, screenshots, or acceptance-criteria list were attached to either ticket, and neither ticket's description specifies the exemplar site's URL or the exact label text used for the link in the product. To stay source-based, the wording added here describes the link generically (what it shows) rather than quoting UI copy or a URL I couldn't verify. Please confirm the wording matches the shipped UI, or supply the exact link text/URL if it should be more specific.
• BREW-2853 has no parent epic, so the rollout-gating check (Step 1.5) had nothing to inspect at the epic level. Both BREW-2853 and its only subtask (BREW-2854) are in "Done" status, and BREW-2854 shows 2 merged PRs, which is the strongest available signal that this shipped.
• The identical article docs/business-app/conversations/sms/us-businesses-sms-registration.mdx also exists in the Partner Center repo (partner-facing mirror of Business App content). It was intentionally left unchanged in this PR since this ticket doesn't meet the Partner Center update criteria — flagging in case a follow-up sync is wanted.

@ahnikakuse @haleyserrano @maryam6samadi

---

Generated by Claude Code