Phase 1: which sender route fits?
The team confirms that the planned traffic is application-to-person messaging to US recipients from a local 10-digit number. That points to A2P 10DLC registration. Toll-free and short-code routes remain alternatives, but they follow different verification and cost paths.
Phase 2: does the website support the application?
The privacy page, terms, legal business name, contact details, opt-in disclosure, and mobile form are checked together. Any mismatch is fixed before screenshots are captured. From June 30, 2026, Twilio requires public privacy and terms URLs for new API campaign submissions.
Phase 3: what goes into the campaign record?
The campaign purpose describes promotional retail messages without vague labels. Sample texts identify the sender and match the claimed use case. The opt-in explanation names the website path. STOP and HELP behavior is recorded. The application evidence tells one consistent story.
Phase 4: what happens during review?
Launch planning allows for Twilio's stated 10-to-15-day campaign review estimate. Production continues on consent-source tags, ecommerce events, templates, suppression rules, and test plans. No promotional traffic uses the 10DLC route until the required status and number assignment are confirmed.
Phase 5: how is the first send tested?
Internal recipients test personalization fallbacks, URLs, landing pages, sender identity, STOP behavior, and tracking. Audience logic is exported and reviewed. The launch record stores final copy, audience count, test evidence, approver, and scheduled time.
Phase 6: what is handed over?
The retailer receives its application evidence, sender record, consent-path inventory, campaign calendar, production checklist, launch log, and open-issue register. The operator can trace why the program was configured that way and which changes need counsel or provider review.
Compare the full registration service, use the A2P field guide, or see project scope options.