Know what the carrier is attesting to.

Telnyx’s explanation, checked September 26, 2026, distinguishes three levels. A, or full attestation, means the provider knows its customer and has verified the right to use the originating number. B, or partial attestation, establishes the customer relationship without the same number-authorization verification. C, or gateway attestation, identifies entry into the network with more limited origin information.

Those labels describe what the provider can attest to about identity. They are not ratings of lead quality, consumer interest or legal permission for the campaign.

DialBreeze production calling uses your own Telnyx account. Have the account owner confirm the outgoing numbers and the intended caller identity through the supported carrier process. Keep the business identity accurate and consistent with the entity placing the call.

Owning an account does not, by itself, guarantee an A attestation on every path. Ask the carrier which verification and configuration apply to the actual call. Do not infer the answer from a purchased number or a screenshot of a general account dashboard.

Use the supplied onboarding process for the connection. Never paste an API key, password or token into the public trial form or a screenshot used in a support message.

A verified calling identity and the label shown on a receiving device are different observations. The person may still decline the call, the call may encounter a delivery problem, or the receiving service may apply a label. Do not turn an attestation result into a “never marked spam” promise.

Likewise, number authorization does not establish that the contact is eligible or that a prerecorded message is permitted. Apply the customer’s approved list and calling policy separately. See the pre-session policy checklist.

1. Which originating number and account were used?
2. What attestation or identity information can the carrier provide for the relevant call?
3. Is there an incomplete verification or configuration step?
4. Does the observed result differ by the receiving network or authorized test destination?
5. What call references and timestamps does the carrier need to investigate?

These are questions for the supported carrier interface or support process, not a claim that DialBreeze exposes a particular attestation panel. Save the response and the relevant references without sharing credentials.

Identity configuration is incomplete: resolve the carrier’s requirements before relying on the number. A legitimate call is labeled unexpectedly: document the display and authorized test context, then use the carrier’s review process rather than assuming a cause.

A person asks not to be called: handle the stop request; changing a number is not a workaround. The number is not yours to present: do not substitute a nearby number to appear local or bypass an identity check.

The reputation investigation guide covers evidence collection without inventing a warm-up formula or recommending number cycling to evade a label.

The account owner should be able to identify the authorized number, the relevant verification status and the route for reporting a problem. The operator should know which caller identity to use and where to escalate an unexpected result.

Retain the approved test references and any carrier response. A clean display on one device is one observation, not a universal delivery guarantee. Recheck the actual configuration when the originating number or calling route changes.