Each product is a Trust Hub bundle attached to the account's approved customer profile plus the specific evidence that product's checklist demands, plus the phone numbers the approval covers. Policy identifiers are resolved by name from the carrier's live policy list rather than transcribed. Beta products surface the carrier's own 'not authorised' text rather than pretending to be enabled.
Also called: Spam Likely · SHAKEN/STIR · branded calling · CNAM · voice integrity · my calls show as spam
- 1The account's A2P secondary profile must already be approved — checked first, so a premature click creates nothing.
- 2Product-specific details are validated locally before any object is created.
- 3A trust product bundle is created and the approved profile attached as identity evidence.
- 4Product evidence is created (call-volume and employee-count records for spam monitoring; display name, authorised representative, verification contact, business address and letter of authorisation for branded calling; a display-name record for CNAM).
- 5The account's live numbers are attached as channel endpoints, the bundle is evaluated, then submitted.
The header states why calling registration matters as much as texting: 'a builder calling a homeowner back from an unregistered number gets "Spam Likely" on the screen and the call is never answered. Registering fixes the display, not the dialing.' Reusing the existing profile is deliberate: 'a builder who registered for texting is already most of the way to trusted calling, and we never make them prove who they are twice.' The number-attachment fix is L2B-VSYHCS: 'The first version of this filed the bundle with the profile as evidence and never attached a single phone number, so a builder could clear carrier review and still have every call go out unattested, unbranded and without CNAM — it looked done and protected nothing.' Policy resolution by name is the L2B-PG642P lesson repeated: 'a transcribed sid that points at the wrong policy fails evaluation in a way that reads like a data problem.'
- Unregistered outbound calls were labelled spam and went unanswered.
- A registration that named no numbers protected nothing.
- A transcribed policy identifier failed evaluation in a misleading way.
- Builders would otherwise have to prove their identity a second time.
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 →