Do-not-call scrubbing
Before every dial attempt, the number is checked against the do-not-call registries you enable for your regions and against your own suppression list. A match means the call is not placed.
Security & Compliance
Honest about being an AI. Careful with every number.
Outbound calling is regulated, and the data behind it is sensitive. This page states what Amruthik does on every call, how call data is handled, and where responsibility sits between us and you.
On every call
Enforced by the system, not left to a script.
Calling-hours enforcement
Calls are placed only inside the permitted hours you configure for the lead's local time zone and day. Calls queued outside a window wait until it opens.
AI disclosure at call start
The agent identifies itself as an AI and states who it is calling on behalf of at the start of every call, before any sales conversation.
Recording consent, per region
Recording notices and consent handling are configured per region. Where recording is not permitted or consent is not given, the call is not recorded.
Immediate opt-out
When a prospect asks not to be called, the agent confirms it on the call and the number is added to your suppression list across all campaigns.
Human handoff guarantee
A prospect who asks for a person is transferred to someone on your team, or offered a callback when no one is available, with the transcript attached.
Call data
What's stored, and who can see it.
Retention periods are set per account during onboarding, and data can be deleted on request when your contract ends.
| Data | When it's stored | Access scope |
|---|---|---|
| Call recordings | Only where recording is enabled for the region and consent requirements are met | Users you grant recording access |
| Transcripts | For every connected call, attached to the call record | Users on the campaign |
| Lead data | The fields you upload or sync from your CRM for calling | Users on the campaign |
| Qualification facts and scores | Per call, written to your CRM fields you map | Users on the campaign and your CRM |
| Suppression list | Numbers that opted out or are on registries you enable | Account administrators |
Encryption
Data is encrypted in transit using TLS and encrypted at rest.
Access control
Access to recordings, transcripts, and lead data is scoped by role and campaign.
Change history
Changes to playbooks, criteria, and CRM write-backs are logged.
Retention
Recording and transcript retention is configured per account, and deletion requests are honored.
Least data needed
The agent only asks for the information your qualification criteria require.
Your configuration, reviewed
We review region, disclosure, and consent settings with you before your first campaign goes live.
Compliance posture
Stated as it is, not as it might be.
We don't claim certifications we don't hold. If your procurement process needs specific documentation, ask us and we'll tell you exactly what's available today.
What Amruthik enforces
- Suppression checks before every dial
- Calling-hours limits per time zone
- AI disclosure at the start of every call
- Recording consent per your region settings
- Immediate opt-out and human handoff
What remains with you
- How your leads are sourced
- Having the consent or lawful basis to call them
- Choosing the regions and registries that apply
- The content of your approved playbook
- Following the laws of the countries you call
Calling regulations vary by country and change over time. Amruthik provides the controls; configuring them for your markets and using them lawfully is your responsibility.
Next in queue
Have a compliance question before you start?
Tell us which regions you call and how your leads are sourced. We'll walk through the disclosure, consent, and calling-hours setup with you.
- Lead 0418 · Operations leadBooked
- Lead 0419 · Finance headHandled
- Lead 0420 · Opted outSuppressed
- Your first campaignDialing next