Business identity, caller ID (CNAM), and SHAKEN/STIR
The Trust tab (Settings → Messaging → Trust) holds three things: a reusable compliance profile for your legal business identity, saved addresses, and your outbound caller ID name. This page covers what each one stores, where it gets reused, and what SHAKEN/STIR actually means for calls placed through message.com.
Compliance profile: your identity, saved once
A compliance profile stores the legal business details that A2P 10DLC brand registration and other verification flows ask for: legal name, display name, entity type, EIN, industry vertical, website, business address, and contact email and phone.
You fill it in once on the Trust tab, then reuse it from the brand registration wizard with a single click: choosing a saved profile fills the identity fields, while the entity type you already picked in the wizard stays authoritative and is never overwritten by the profile. Every filled field stays fully editable after prefill; nothing locks.
A compliance profile is a plain, instant record: create it, edit it, delete it, no review step. It is not a TCR brand and carries no approval status of its own. The brand you eventually submit to TCR is a separate record with its own draft → needs_review → registered/rejected lifecycle, described in brand registration. Saving or deleting a profile never touches a brand you already registered from it.
The EIN is masked everywhere the profile appears in a list: you see only hasEin and the last four digits. The full value is only ever returned when you open one specific profile by id, the same precedent message.com uses for every other stored tax ID.
Addresses: business and emergency locations
Addresses are a separate reusable list on the same tab: street, suite, city, state, and postal code, each tagged as a business address or an emergency address.
| Kind | What it is used for |
|---|---|
| Business | The physical location behind your account, reusable when a registration flow asks for one. |
| Emergency | What 911 dispatch sees for your phone numbers. Set this to a real, staffed location for any number that places or receives calls. |
Like compliance profiles, addresses are instant records with no review state. From the brand registration wizard, picking a saved address fills only the street, city, state, and postal fields, leaving identity fields it does not own untouched. Deleting a saved address does not affect a number or registration that already used it.
Caller ID (CNAM): the name recipients see
Caller ID name (CNAM) is the workspace-level name carriers display to recipients when your numbers call out. It is a single field, up to 15 characters, the limit carriers' caller-ID name (LIDB) field accepts. Leave it blank and recipients see just the number.
Saving a caller ID name pushes it to every active number on the workspace: message.com syncs the name to our upstream carrier so it is attached to each of your numbers' carrier records. There is no separate "sync" step to run afterward; saving the name is the sync.
Propagation is not instant, and it is not fully under our control. Carriers cache caller-ID name downstream in their own LIDB databases, so a saved name can take 24 to 72 hoursto show up for recipients. Some mobile carriers also no longer perform a LIDB dip at all: they show their own caller-ID data or app-based labels instead of the name a call is carrying. Setting your CNAM correctly is still the right move, since it is what shows up wherever a carrier does look it up, but it will not universally override every phone's own caller-ID source.
The per-number list on the Trust tab shows each active number's current cached caller-ID value read back from the carrier ("Not set" when none exists), read-only. There is no synthetic "synced" or "pending" status badge next to a number: message.com does not track a separate sync state beyond that cached value, so none is shown.
SHAKEN/STIR: what it is, and what we do and don't know
SHAKEN/STIR is a telecom industry standard that lets a call's originating carrier cryptographically sign it, so the terminating carrier and the recipient's phone can verify the call actually came from the number it claims to be from. It is the mechanism behind the "Spam Likely" and verified caller labels phones show today. See the STIR/SHAKEN concept page for the fuller background on attestation levels and how the standard works end to end.
Calls placed through message.com are carried and signed by our upstream carrier as the originating provider. We don't independently sign or attest calls ourselves, and we don't currently have a way to see or report which attestation level (A, B, or C) an individual call received.
Per-number attestation status isn't available in the dashboard yet. We plan to check whether our upstream carrier exposes this per number and add a real status column to the Trust tab once it does. Nothing on this page claims a specific attestation level for your calls today.
A note on cost
Compliance profiles, addresses, and caller ID name are all included: there is no fee to create, edit, or sync any of them. Fees only apply where they always have, on brand and campaign registration with TCR, and on phone number rental. See the campaign registration fee table for the full breakdown.
Next steps
- Register an A2P 10DLC brand: use a saved compliance profile and address to prefill the wizard.
- A2P 10DLC campaign registration: the next step after a brand is approved, including the full fee table.
- Verify API: a hosted alternative when you want one-time codes without owning the sending infrastructure or the identity records this page describes.