Skip to main content
Callers gives you controls for the data your agents collect and for what your agents may say: what is stored, for how long, who can see it, and which responses are blocked. This page lists each control and where to find it. For Callers’ own security program and compliance documents, visit the Callers Trust Center. For calling and messaging rules that apply to your agents, see Compliance.

​
Controls at a glance

​
Pick the controls for your use case

Agents that take payments

Detect Payment and credentials, and delete transcripts and recordings that contain them.

Healthcare and other regulated data

Keep phone numbers in your own system, and detect Personal identifiers and Health information.

Limit what the agent says

Block advice, commitments, or off-topic answers with guardrails.

Limit who sees conversations

Member access, retention, and support access.

​
Verify requests from Callers

Callers signs the HTTP requests it sends to your webhook endpoints, so you can confirm they’re genuine and unchanged.
  • Webhook Signature. In Settings → General, click Show HMAC Secret to see your account’s secret. Callers signs requests with HMAC-SHA256 and sends the signature in the X-Signature header.
  • Signature type. Advanced webhooks and HTTP actions also send X-Signature-Type (HMAC or RSA). In an HTTP action, turn on Sign with RSA-SHA256 to sign with RSA instead of your HMAC secret.
For verification code, see Validating webhook signatures.

​
Allowlist Callers IP addresses

If your webhook endpoints or the APIs your actions call are behind a firewall, allow requests from these Callers IP addresses:

Callers Trust Center

Security practices and compliance documents.

Team and permissions

Roles, member access, and MFA.

Do Not Call

Honor opt-outs and DNC registries.

Validating webhook signatures

Verify that requests come from Callers.