Built for secure, auditable voice operations.
Agni is designed for teams that need control over customer conversations, call data, access, and operational review. Every call is recorded, transcribed, and reviewableand India's calling rules are built into the workflow, not bolted on afterwards.
Controls your security team can verify.
Nothing about an AI phone call should be a black box. Agni gives administrators the access controls, records, and review workflows to see exactly what every agent said and did.
Workspace access & team permissions
Complete call records
Configurable data flows
Human handoff for sensitive calls
Post-call review workflows
Safe testing before deployment
India calling compliance, built into the workflow.
Most platforms treat India's calling rules as your problem to solve after deployment. Agni treats them as workflow requirementsscrubbing, templates, windows, disclosure, and records are part of how campaigns run.
DND/NCPR scrubbing before dialing
Contact lists are screened against DND preferences before a campaign dialsnot after a complaint.
DLT template workflows
Operate within 140-series (promotional) and 160-series (service) calling contexts, with campaigns aligned to your registered DLT templates.
Consent logging
Capture and store the consent basis for each contact, so every dial can be traced back to a recorded opt-in.
Calling-window enforcement
Campaigns respect configured calling hoursincluding RBI-aligned windows for collections workflowsautomatically.
AI-call disclosure support
Configure agents to disclose that the call is AI-assisted at the start of the conversation, in the customer's own language.
Per-campaign audit trails
Every campaign keeps complete recordswho was called, when, under which template, and what was saidready for internal or regulator review.
What the law requiresa short primer
If your team runs outbound calling in India, two regimes shape the work. Here is what they ask for, so you can map Agni's workflow controls against your own obligations.
TRAI TCCCPR & DLT
- Businesses (principal entities) and their telemarketers must register on DLT platforms, with PE–telemarketer linkage.
- Promotional calls run on 140-series numbers; service and transactional calls on the 160-series.
- Call scripts follow pre-registered DLT templates, and contact lists must be scrubbed against DND/NCPR preferences.
- Commercial calls are restricted to a 10 AM – 7 PM window, and AI-generated calls must be disclosed.
- Penalties range from ₹1,000 to ₹1.5 lakh per violation; repeated complaints can trigger disconnection.
DPDP Act 2023
- Rules notified in November 2025, with a full-compliance deadline of May 13, 2027.
- Consent notices must be itemizedand available in English plus India's scheduled regional languages.
- Bundled consent is not permitted, and withdrawing consent must be as easy as giving it.
- Organisations need data processing agreements governing the sub-processors that handle personal data.
- Penalties for breaches run up to ₹250 crore.
Running lending or collections workflows? RBI's Digital Lending Directions hold regulated entities accountable for the conduct of their agentsincluding AI agentsand restrict recovery contact hours. Agni's calling-window enforcement and complete call records are designed to support those controls. For the full clause-by-clause mapping, download the RBI Compliance Pack on Ravan Revenue Recovery, or model the economics in the ROI calculator.
This summary is for orientation only and is not legal advice. Your obligations depend on your registration status, industry, and use caseAgni provides the workflow controls; your compliance program defines how you use them.
Designed for DPDP-era consent management.
The DPDP Act changes how Indian businesses collect, use, and retain customer data. Agni's calling workflows are designed so consent, withdrawal, and review fit how the law expects data to be handled.
Readiness posture
- Itemized consent designcampaigns can be scoped to the specific purpose a customer agreed to
- Withdrawal flowsopt-outs on a call are recorded as structured outcomes, and contacts can be suppressed from future campaigns
- Data principal rights supportcomplete recordings, transcripts, and session details make access and correction requests answerable
- Retention and deletion terms documented per workspace as part of enterprise onboarding
- DPAs with sub-processor terms available on request for enterprise agreements
Consent in the customer's own language
DPDP requires consent notices in English plus regional languages. Most platforms treat that as a translation chore. Agni speaks 30+ Indian languages and handles 100+ accents & dialectsso consent, AI disclosure, and opt-out conversations can happen natively in the language your customer actually speaks.
Where we are on certifications, honestly.
Our architecture is SOC 2, GDPR, and HIPAA readycontrols, data handling, and agreements built to those standardswith formal certifications in progress rather than implied. Enterprise customers can request our current security documentation and DPA today, and we complete security questionnaires as part of evaluation.
Responsible AI calling, as policy.
Customers should never feel tricked by an AI call. These are the defaults we design forand the standards we recommend every team configures.
AI disclosure
Human escalation
Recording transparency
Grievance contact
Questions security teams ask us.
The short answers, before the questionnaire. For anything not covered here, our team responds directlyno portal, no ticket queue.
Evaluating the rest of the platform? See pricing, integrations, the ROI calculator, and the general FAQ.
Where is call data stored? Do you support India data residency?
How long are call recordings and transcripts retained?
Do you use sub-processors?
Will you sign a DPA?
Can we send you our security questionnaire?
Bring your security questionnaire.
Send your questionnaire, DPA, or audit requirements to info@ravan.aior book a demo and walk through Agni's compliance workflows live with our team.