How it works on Indian calls
A distributed ledger keeps the same record in step across several parties. In Indian telecom, the operators use one as their digital consent platform under TRAI's Telecom Commercial Communications Customer Preference Regulations (TCCCPR), 2018. Two things sit on it that matter for AI calling:
- The sender. Your business registers on DLT as the principal entity: the sender of its commercial communications.
- Consent. Consent to receive commercial communications is registered there too. A promotional call can reach a DND-registered number only where the person's preferences allow it or their consent is registered.
The Third Amendment, announced by PIB on 18 September 2026 (release ID 2311989), tightened the consent side. Older consent counts only if it was obtained in a verifiable way and is registered on the DLT platform. Consent that sits only in your CRM doesn't meet that test.
Say an NBFC collected opt-ins on a loan form some years ago. Before it relies on them for a promotional AI campaign, those consents need to be verifiable and on DLT.
Why it matters
Registered consent is what lets a promotional call reach someone whose DND preferences would otherwise block it. Without it, promotional calls to DND-registered numbers draw complaints, and under the 2026 amendment complaints and AI spam flags lead to action against the sender sooner than before.
How Kallix handles it
DLT registration and consent stay with your business, because they come from your relationship with your customers. Kallix helps on the calling side. You can store each person's consent source and date on the contact. Kallix checks every number against the NCPR before a campaign dials, and declares automated (A2P) calling for the numbers it provides through Vobiz.