When registration is required
Not every caller-identity feature requires registering a business. The dividing line is whether a feature puts your own legal brand in front of recipients or carriers — that’s what needs a verified enterprise (a Federal EIN + a signed Letter of Authorization). Lighter-weight features work without one.| Capability | Needs EIN + LOA? | Notes |
|---|---|---|
| CNAM display name | No | Set the caller-ID name shown on the network. A carrier-database entry, not a brand vetting. |
| Number reputation monitoring | No | Every number you provision is auto-enrolled under our shared umbrella — live spam-risk scores from day one, no paperwork. |
| Branded Calling (your name, logo, call reason on the screen) | Yes | The rich on-screen identity is attested to your legal entity, so the carrier requires a vetted enterprise. |
| Own-brand reputation & remediation (dispute/fix spam labels under your entity) | Yes | Actively managing reputation as your own brand — rather than riding the umbrella — requires your registered enterprise. |
Registering an enterprise
When you do need it (Branded Calling or own-brand reputation), the flow is:Generate & sign the LOA
POST /v1/caller-trust/enterprise/generate-loa produces the authorization PDF; sign and submit
with POST /v1/caller-trust/enterprise/sign-and-submit (or …/submit if signed out of band).Vetting
Status moves
PENDING_VETTING → APPROVED (or REJECTED → fix and resubmit). Poll
GET /v1/caller-trust/enterprise or subscribe to the enterprise.status.updated webhook.Brand your calls
Once
APPROVED, your Display Identity Record becomes eligible — submit it via
Branded Calling to push your name, logo, and reason to recipients.