Four objects are created in sequence: a secondary customer profile carrying the business information, authorised representative and address; an A2P trust product wrapping the messaging profile; a brand registration tying both bundles together for carrier verification of the business number against government records; and, after the brand approves, a campaign on the builder's Messaging Service with use case, message samples and opt-in flow.
Also called: A2P 10DLC · brand registration · campaign approval · my texts get blocked · carrier registration
- 1The wizard collects legal name, business number, structure, address, website and the authorised representative.
- 2The platform's own approved primary profile is resolved first, before any objects are created.
- 3The secondary profile is assembled from four sub-objects, evaluated against the carrier policy, then submitted.
- 4The A2P trust product is created, evaluated and submitted the same way.
- 5The brand registration is filed; once approved, the campaign is filed on the builder's Messaging Service.
The pipeline exists to remove the operator, and its comments are a ledger of real rejections. The primary-profile check is first for a money reason: 'it's the most common blocker and checking it up front means a blocked submission creates zero TrustHub objects (and costs nothing) before failing with a clear message' — the underlying failure being 'Primary customer profile bundle is null', learned live on the first real submission (L2B-L6H6SS). A wrong policy constant is recorded as L2B-PG642P: the trust-product constant 'originally pointed at "Sole Proprietor TrustProduct" and the messaging evaluation demanded sole-prop brand/mobile/starter-profile fields no standard registration carries.' There is even a nuance learned from a live filing: 'Twilio's evaluation REJECTS "pending-review" (submitted, not yet picked up) — only in-review/approved satisfy the requirement.' And the whole thing must run as the right account: 'a brand registered with the parent's credentials belongs to the parent, not to the builder, no matter what name is on it.'
- US carriers filter business texts from unregistered numbers outright.
- Registration was an operator task nobody could self-serve.
- A registration filed on the wrong account belonged to the wrong business.
- A failed submission used to create billable objects before failing.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →