Submit your setup or issue
Share the campaign details, website URL, platform, rejection feedback, or API error. The more context you include, the faster the scoping conversation goes.
The process
A straightforward A2P onboarding process
Share the current campaign, rejection, API issue, or implementation gap. The review starts there and ends with specific fixes — not a generic checklist.
Review and diagnosis
The submission is reviewed against TCR requirements, compliance criteria, or the specific technical failure point — depending on what you shared in step one.
Receive recommendations
Recommendations are specific to your setup — what to change, what to rewrite, what to configure, and in what order. Not a generic checklist.
Implement changes or resubmit
Apply the fixes to the campaign submission, website, API configuration, or internal workflow. Follow-up support is available if something surfaces during implementation.
Before you submit
What to include in your request
The more of this you can share upfront, the faster the review moves. Nothing is required — share what you have.
Campaign details
Use case description, opt-in flow, sample messages, and current TCR registration status.
Website links
Homepage, opt-in page, Privacy Policy, and Terms of Service URLs.
Platform and setup context
Messaging provider, number type (10DLC, toll-free, short code), Messaging Service SID if applicable.
Rejection feedback or error detail
TCR rejection reason, error code, failed API request/response, or delivery failure pattern.
Ready to start a review?
Share the setup or issue and the scope can be confirmed from there.