What compliance questions should I ask an AI calling vendor?
Ask an AI calling vendor whether its calling line is DLT-registered, how it screens against DND, how it enforces calling hours, how recordings and consent are handled, and who is responsible when a rule is broken. Responsibility for lawful calling stays with your business, so you need clear written answers.
Why compliance is part of the buying decision
In India, rules from TRAI and related laws govern who may be called, when, from which number series and with what disclosures. A breach can lead to blocked numbers and penalties, and the business whose product is being sold carries the exposure. A vendor that makes compliance easy lowers risk; it does not remove it.
The question list
| Question | What a good answer includes |
|---|---|
| Is the calling line DLT-registered? | Yes, with an explanation of who registers what |
| How do you screen against DND? | Automatic screening on bulk campaigns, with a clear scope |
| How are calling hours enforced? | Configurable windows that block calls outside permitted hours |
| Which number series do you use? | A clear answer for promotional versus service calls |
| How is consent handled? | Guidance on capturing and recording consent for leads |
| Are calls recorded, and who is told? | Controls for recording and disclosure in the script |
| How is personal data protected? | Mention of the DPDP Act and retention controls |
| Does the agent disclose it is an AI? | Configurable opening line and honest answers if asked |
| What happens if a customer asks not to be called? | A way to stop further calls to that number |
| Who is liable if something goes wrong? | A written split of responsibilities |
Sector rules are on top
Lenders, insurers, investment advisers, real estate developers and healthcare providers face additional rules from RBI, IRDAI, SEBI, RERA and medical regulators. A general vendor cannot make a regulated script compliant for you. Ask whether the vendor lets you control the script fully and whether it supports review by your compliance team.
Practical safeguards on your side
- —Call only people with a lawful reason: enquiry leads, existing customers or consented contacts.
- —Keep a record of when and how each lead gave their number.
- —Honour do-not-call requests immediately.
- —Keep scripts honest and avoid promises you cannot keep.
- —Review transcripts regularly for statements that cross a line.
What Outpero provides
Outpero operates a DLT-registered calling line, screens bulk campaigns against DND and lets you set calling windows. It records calls with transcripts, and the agent can end calls and stop further attempts when asked. Responsibility for lawful use rests with the business running the campaign, as with any vendor.
Outpero publishes this page and it is not legal advice. For regulated sectors, take advice from a qualified professional before launch.
Want to hear an AI voice agent handle this on a real call?
Follow-up questions
Does a compliant vendor make my calls compliant?
+
No. A compliant platform gives you the tools, such as registered lines, screening and calling windows, but you still decide who is called and what is said. Keep consent records, restrict lists to lawful contacts and review scripts before sending campaigns.
- TRAI — TCCCP Regulations 2018, consolidated with amendments (21 May 2026)
- TRAI — Telecom Commercial Communications Customer Preference Regulations, 2018
- MeitY — Digital Personal Data Protection Act, 2023
- MeitY — Digital Personal Data Protection Rules, 2025 (notified 14 Nov 2025)
- SEBI — (Investment Advisers) Regulations, 2013 (Gazette)