One validator used by both the wizard and the route, so the builder is told exactly which field is missing before any object is created on the carrier. Spam monitoring asks what the line is used for, roughly how many calls a day, and how many people work there — as picklists. Branded calling asks for the display name plus an authorised representative and a verification contact, with email and phone format checks. Display names are capped at fifteen characters, matching the carrier limit.
Also called: what do they need from me · branded calling requirements · 15 character limit · call volume
- 1The wizard renders the product's questions with pre-set option lists.
- 2The shared validator runs client-side as the gate and server-side before filing.
- 3Branded calling reuses the address the texting registration already recorded, for both the business-address and letter-of-authorisation documents.
- 4Only once everything passes are Trust Hub objects created.
The requirement list was read from the carrier's live policies and is recorded as L2B-XA9BLZ: 'These are the carriers' checklists, not ours — the wizard collects them, the route validates them, and this module files them.' The picklists exist because 'Twilio takes free text, but a builder should never have to invent carrier vocabulary.' The shared address is deliberate: 'a builder never types it twice and the two filings can't disagree.' CNAM has its own recorded gap: the display name 'used to be collected in the UI and sent nowhere — the carriers were never told what name to show.'
- Carrier vocabulary was unanswerable by a normal business owner.
- Re-typing the address risked two filings disagreeing.
- The CNAM display name was collected but never actually filed.
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 →