The short version
- Built for requested calls
LumaKol is made for calling people who asked to hear from you. TRAI allows calls on an enquiry for seven days; after that you need consent, and promotional campaigns belong on 140-series numbers.
- Controls before the dial
Calling hours, a do-not-call block and attempt limits are checked before every dial. Switch auto-dial off unless you have declared A2P calling.
- No DND checks
LumaKol does not check numbers against the DND registry. Screen bought or cold lists before you import them.
- Consent is yours to record
Keep the source, date and wording of each enquiry on the lead. That is your evidence that the call was requested.
A plain-language summary for orientation. This page describes how LumaKol works and is not legal advice.
1Who this page is for
This page is for LumaKol customers whose teams call people in India. It covers TRAI’s rules on unsolicited commercial communication (the TCCCPR and the DND registry), the Digital Personal Data Protection Act, 2023, and call recording.
This page explains how LumaKol works and what it does and does not do. It is not legal advice. The rules depend on your sector, on why you are calling and on the consent you hold, and they change often, so take advice from your own lawyer before you rely on it.
2The rules in brief
Commercial calls: the TCCCPR
TRAI, India’s telecom regulator, controls commercial calls and messages through the Telecom Commercial Communications Customer Preference Regulations, 2018 (TCCCPR), which were amended on 12 February 2025.
- DND: a subscriber can block all commercial communication, or chosen categories of it, by registering a preference in the National Customer Preference Register, usually called DND.
- Number series: promotional calls are to come from 140-series numbers through a telemarketer registered with the telecom operators. Service and transactional calls from banks, insurers and other regulated financial entities are moving to the 1600 series.
- Unregistered senders: since August 2024, TRAI has directed operators to disconnect all the telecom resources of unregistered senders whose promotional calls draw complaints, and to blacklist them for up to two years (TRAI direction of 13 August 2024).
- Complaints: since the 2025 amendment, a person has 7 days to report an unwanted commercial call or message.
- Mixed content: a service or transactional call that also carries promotional content is treated as promotional.
September 2026: the Third Amendment
TRAI introduced the Third Amendment to the TCCCPR on 18 September 2026. The changes that matter most to calling teams:
- Calls after an enquiry: commercial calls based on a customer’s own enquiry are allowed only for seven days from that enquiry, and the enquiry must have been made in writing or by digital means and be kept in a verifiable form.
- Automated calls: calls started by an application or automated platform without direct human dialling, including autodialling, are application-to-person (A2P) calls. They must be declared to your telecom operator in advance, with the numbers used, or they are treated as unsolicited.
- Consent: consents you already hold count only if they were obtained in a verifiable way and are registered on the operators’ digital platform.
- Complaints: action against a sender can start at three complaints in ten days when the operator’s systems also flag the number.
- The 140, 1600 and 1601 series may not be flagged as suspected spam by caller-ID apps.
What this means if your team calls from its own mobile numbers
The rules are aimed at unsolicited commercial communication. A call someone asked for is in a stronger position than a cold call, but since September 2026 that lasts seven days from a written or digital enquiry; after that you need the person’s consent. Promotional campaigns to people who have not asked to hear from you belong on a registered telemarketer’s 140-series numbers, not on your agents’ mobile numbers: complaints against a mobile number can lead to it being barred or disconnected.
Personal data: the DPDP Act
The Digital Personal Data Protection Act, 2023 covers the personal data of the people you call. Its rules were notified on 13 November 2025 and come into force in phases, with most obligations on notice, consent and individuals’ rights applying from May 2027. Your business is the Data Fiduciary for its leads’ data, and LumaKol processes that data for you under the Data Processing Addendum.
Call recording
Indian law has no single rule on recording a call you take part in. Telling people that a call may be recorded, and limiting who can listen, is the safe practice, and some sector regulators set their own expectations for recording sales calls.
3How calls are placed in LumaKol
LumaKol is not a dialer platform. Every call is an ordinary mobile call from the agent’s own phone, on the SIM the agent chose as their work SIM, and the agent is there to talk when it connects. A call starts in one of three ways:
- The agent taps Call on a lead in the Android or iPhone app, or in their calling queue.
- The agent clicks Call on a lead in the web app, and the call rings out from their own phone.
- Auto-dial next lead, if the agent switches it on. It is off by default and is each agent’s own choice. After the agent logs the outcome of a call, the next lead in their queue is shown with a countdown of a few seconds, which the agent can change, and is dialled when it ends unless the agent cancels. It stops as soon as the agent leaves that screen, and it dials one lead at a time. Owners and admins can switch auto-dial off for the whole workspace (Settings → Calling → Allow auto-dial next lead); then every call starts with a tap.
The only numbers LumaKol ever calls are leads the customer has stored in its own workspace, and the call is placed through the phone's own dialer. LumaKol does not generate numbers to call, does not dial several numbers at once or ahead of an available agent, does not play artificial or prerecorded voice messages, and does not leave voicemails. Text messages and WhatsApp messages from a lead open in the agent’s own messaging app for the agent to send; LumaKol does not send them.
Auto-dial next lead starts the next call after a countdown, without the agent tapping. Under the September 2026 amendment, calls started by an application without direct human dialling are A2P calls that must be declared to your telecom operator in advance. Unless you have made that declaration, switch auto-dial off for the workspace (Settings → Calling → Allow auto-dial next lead) so that every call starts with a tap, and ask your lawyer.
4What LumaKol gives you
Calling hours, checked before the dial
In Settings → Calling policy you set when calling starts and ends and which days are calling days (by default 9:00 to 20:00, Monday to Saturday). Before the Android or iPhone app dials a lead, from the queue, the lead page, the call history or a click-to-call from the web, it checks those hours. Outside them the agent is warned and must confirm before the call is placed, and the call is flagged as outside hours in the call list and reports. On days the workspace has closed for calling, such as holidays, the apps refuse to dial with no option to override.
A hard do-not-call block
The outcome “Requested no contact” moves the lead to Lost, which takes it out of every calling queue. With “Block calls to leads who asked not to be contacted” switched on in Settings → Calling policy (it is on by default), the apps refuse to dial that lead from anywhere, with no option to call anyway. Together these work as your internal do-not-call list for leads in LumaKol.
Attempt limits per lead
A workspace sets the maximum number of call attempts per lead (5 by default, adjustable from 1 to 50) and how long to wait before an unanswered lead comes back into the queue. Once a lead reaches the limit it leaves the queue and the apps stop dialling it.
Records of consent and opt-outs
Leads that arrive through a form, Google Ads, IndiaMART, JustDial or the API keep their source and the time they arrived, which is the written or digital record of the enquiry. Every lead also has notes, custom fields you define (for example consent date, consent source or the wording the person agreed to), the source it came from, and a timeline of every call with its time, duration and outcome. The audit log in Settings records who exported or changed what.
Caller ID
Calls show the agent’s own mobile number, because they are normal calls from the agent’s SIM. LumaKol does not change or hide caller ID; make sure your agents’ phones do not withhold their number.
Recordings and who can hear them
LumaKol does not record calls. Where an Android phone’s own dialer records them and recording sync is on, each recording is saved to the caller’s own Google Drive and linked to the lead. Settings → Privacy decides whether only owners, admins and team leads can play it, or agents too for their own calls.
Personal data controls
Number masking for agents, export permissions by role, an audit log of exports and changes, and deletion of a lead from the web app, which also removes it from your team’s phones when they next sync.
5What LumaKol does not do
- It does not check numbers against the DND registry, and it does not tell you whether a number is registered.
- It is not a telemarketer platform. It does not place calls from 140-series or 1600-series numbers; every call comes from an agent’s own SIM.
- It does not register you, your headers or your templates on the operators’ DLT platform. SMS and WhatsApp templates open in the agent’s own apps for the agent to send.
- It does not collect, verify or store proof of consent on your behalf, beyond what your team records on the lead.
- It does not scrub the lists you import. The do-not-call block follows the lead record: if a lead who opted out is deleted and the number is imported again later, the new lead is not blocked. Keep opted-out leads instead of deleting them.
- The calling-hours, do-not-call and attempt checks are made by the LumaKol mobile apps. A call an agent dials directly in the phone’s own dialer is not checked.
Screening lists, holding consent, choosing whom to call and why, and using a registered telemarketer for promotional campaigns remain your responsibility.
6A checklist for calling in India
- Call people who asked to hear from you: enquiries, existing customers and people who gave consent. Keep cold promotional campaigns off your agents’ mobile numbers.
- Call enquiries within seven days of the enquiry, and get the person’s consent before calling them after that.
- Keep Auto-dial next lead switched off for the workspace unless you have declared A2P calling to your telecom operator.
- If you run promotional campaigns, use a registered telemarketer and 140-series numbers for them.
- Screen bought or cold lists against DND before you import them, and keep the record of the screening.
- Record consent on the lead: the source, the date and how the person asked to be contacted. Custom fields work well for this.
- Keep “Block calls to leads who asked not to be contacted” switched on, and have agents log “Requested no contact” the moment someone asks.
- Set calling hours and days that suit the people you call, and an attempt limit that does not read as harassment.
- Tell people when a call may be recorded, and limit who can listen in Settings → Privacy.
- Collect only the fields your sales process needs, and be ready to correct or delete a person’s record when they ask.
7Questions
If you have a question about how a LumaKol feature works, write to support@lumakol.com. For questions about your legal obligations, speak to your own lawyer or read TRAI’s regulations: we cannot tell you whether a particular call is lawful.
Questions about this document?
A person answers every message — no ticket queue, no bot. Write to us and we will reply within one business day.
Email support@lumakol.comRelated pages
- ComplianceGDPR, the Data Processing Addendum and calling rules in the US, UK and India.
- GDPRRoles, rights requests, hosting and transfers for EU and UK data.
- Data Processing AddendumThe processing terms and the full sub-processor list.
- US calling rulesTCPA, the Do Not Call Registry and what LumaKol checks.
- UK calling rulesTPS, CTPS and PECR, and what LumaKol checks.
- Privacy PolicyWhat personal data we handle, why, and your rights over it.
Translations are provided for convenience; the English version governs in case of conflict.

