Robocall mitigation and call reputation
Use authorized caller IDs and responsible calling practices without assuming call authentication guarantees delivery.
What mitigation means
Telephone providers use identity authentication, traffic analysis and complaints to identify unwanted or suspicious calls. A legitimate call can still be labeled or blocked, and a signed calling number is not proof that the content is safe.
Authentication and reputation differ
STIR/SHAKEN concerns the identity asserted for the calling number. Call reputation also depends on other provider signals. Message.com cannot guarantee the label shown by every receiving network or device.
Operate responsibly
Use the number assigned to your workspace and only contact recipients you are authorized to call. Honor opt-out requests and applicable calling restrictions. Do not rotate numbers to evade a block or continue unwanted calls.
What the product exposes
Use supported call records and usage reports to investigate your traffic. The current Calls API does not promise a verificationResult on every call, and the Reports API does not provide a per-number carrier reputation feed. Do not build an integration around those previously described fields.
Report a labeling or delivery issue
Keep the call ID, timestamp, originating number, destination and observed label or failure. Contact support with those details so the route can be investigated. Carrier review or configuration may be needed; repeatedly redialing is not a diagnosis.