Trust
How we review accounts, which calling rules the dialer enforces, and how call data and recordings are handled.
Account review
- What we check
- The business's identity and owners, a sanctions check, lead sources, how consent is collected and recorded, the do-not-call subscription, state registrations and call scripts.
- When
- Before an account places its first call, for each new subaccount, and again every 12 months.
- Scales with you
- Agents, lines and numbers can be added on the same account without a second review or a new setup.
- No surprise shutdowns
- We email you before we pause, limit or close an account, with what we saw and what needs to change. We act first only when a law, a government or court order (including FCC orders), a law enforcement request, a carrier block or a traceback obligation requires it, or for a security incident such as a stolen API key, which we lock at once. Then we email you the same hour, unless the law or the order forbids it.
- Account actions
- Limits, pauses and closures follow the notice steps in the acceptable use policy: an email first, a follow-up, then the smallest step that fixes the problem. We act first only when a law, a government or court order (including FCC orders), a law enforcement request, a carrier block or a traceback obligation requires it, or for a security incident such as a stolen API key, which we lock at once. Then we email you the same hour, unless the law or the order forbids it.
Carrier and compliance
Enforced by the dialer on every call. Settings are in the compliance guide.
| Rule | Source | What the dialer does |
|---|---|---|
| Calling hours | 47 CFR 64.1200(c)(1), state law | 8:00 am to 9:00 pm in the lead's local time, inside stricter state windows and state holiday bans. |
| Ring time | 47 CFR 64.1200(a)(6) | At least 15 seconds or 4 rings. |
| Abandoned calls | 47 CFR 64.1200(a)(7) | Tracked per campaign over 30 days. At 3% the campaign dials one line per agent until the rate is back under. An identified message with an opt-out plays within 2 seconds. |
| Do-not-call list | 47 CFR 64.1200(d) | Checked before every call and message. |
| National Do Not Call Registry | 16 CFR 310.8, 47 CFR 64.1200(c)(2) | Checked with each business's own subscription, never a shared one. |
| State call limits | Fla. Stat. 501.616, Okla. Stat. tit. 15 775C.4, Md. Com. Law 14-4502 | 3 sales calls per person per 24 hours, across all numbers. |
| Opt-out requests | 47 CFR 64.1200(a)(10), (d) | Recorded at once and honored on every number and channel in the account. |
| Caller ID | 47 CFR 64.1601(e), STIR/SHAKEN | A number assigned to your account that takes calls back. Every call is signed for STIR/SHAKEN at no charge. |
| Call recording | State wiretap laws | One side or both, by the lead's state and the consent given on the call. |
You stay responsible for the consent your calls and messages require and for what your agents say. The acceptable use policy lists the traffic we do not carry.
Data and recordings
- Recording
- Set by the lead's state and the consent given on the call. Ringing, voicemail and machine audio are never recorded.
- Retention
- Recordings and transcripts are kept for 1 year by default. You can set 30 days to 10 years. Each deletion is sent as a webhook. Deleted recordings and transcripts are removed from our systems, except where the law requires us to keep a copy.
- Access
- Recording and transcript links need an API key or a signed link that expires.
- Use of recordings
- Recordings and transcripts are used only to provide the service to the account that made the call. We do not use them to train models.
- Privacy
- We process call data for you and do not sell it. A data processing agreement and our sub-processor list are available on request. See the privacy policy.
- Customer network information
- Call records and account details are customer proprietary network information under federal law. We use them only to provide the service, and give them out only to you or when the law requires.
Security
- Encryption
- TLS for the API, webhooks, SIP signaling and agent connections. SRTP for SIP media. Recordings and transcripts are encrypted at rest.
- API keys
- Separate keys per account and subaccount, with read-only and per-resource scopes. Keys can be rotated without downtime.
- Separation
- Each subaccount has its own numbers, leads, do-not-call list, recordings and keys.
Apply for access
We review lead sources, consent and scripts before an account can dial. Setup covers carrier approval, number registration and branded caller ID.