DND, consent and call recording: what calling teams in India need to get right

Calling teams live inside a set of rules that most sales managers learn about only after a complaint. The rules are not complicated, but they must be operational — built into who gets called, when, and how the record is kept — rather than a poster on the wall.

The DND registry and unsolicited commercial calls

India’s telecom regulator maintains a customer preference framework (the Telecom Commercial Communications Customer Preference Regulations, commonly called DND) that lets subscribers block promotional calls and messages, fully or by category, by registering their number. Calling a registered number with promotional content exposes the business and, depending on the pattern, the sending number to complaints and penalties, and carriers act on repeated violations.

Two distinctions matter operationally. First, promotional versus service or transactional communication: a call to someone who enquired about your product, or an existing customer about their account, is generally treated differently from a cold promotional call to a purchased list. Second, consent: a documented opt-in from the person — a form they submitted, an enquiry they made — is your evidence that the call was requested.

• Screen bought or cold lists against DND status before you import them, and keep the screening record. LumaKol does not check DND status on import, so this step happens before the upload.
• Store the lead source and the timestamp of the enquiry on every lead; that is your consent trail.
• Give agents a Do-not-call outcome that removes the lead from every queue immediately and permanently.
• Restrict promotional calling to permitted hours and let the CRM enforce calling hours before the dial.

SMS and WhatsApp: templates and registration

Commercial SMS in India requires the sender and message templates to be registered on the telecom operators’ distributed-ledger (DLT) platform; unregistered templates are filtered. WhatsApp Business messaging outside an active customer conversation uses pre-approved templates as well. In practice this means the follow-up messages your agents send should come from a small library of approved templates rather than free text typed each time — which is also better for consistency and for logging.

Call recording and consent

Whether a call may be recorded, and who must agree, depends on the jurisdiction of both parties and on the purpose. Many jurisdictions require at least one participant to consent; some require all participants; several sector regulators expect recording of specific interactions such as financial product sales. Two operational safeguards travel well everywhere: tell people when a call may be recorded, and control who inside the company can listen.

A calling CRM that does not carry the audio itself — it syncs recordings the handset’s own dialer makes, where the manufacturer and region allow it — keeps you in control of when recording is on. Access should be restricted by role — in LumaKol a privacy setting decides whether only owners, admins and team leads can listen, or agents too for their own calls — and retention limited to what your policy states.

Personal data obligations

Names, numbers, call logs and notes about a person are personal data. India’s Digital Personal Data Protection Act (2023), with its rules being phased in, sets out obligations around purpose, consent, security and the rights of the individual, alongside similar regimes elsewhere for teams calling internationally. For a calling team the practical checklist is short.

1. Collect what the sales process needs and nothing more; every custom field should have a reason.
2. Show agents which permissions the app uses and why, and capture only the work SIM, never personal calls.
3. Mask numbers for roles that do not need them; a viewer does not need a lead’s full mobile number.
4. Keep an access trail for bulk data: who exported which list, and when. Limit who may export, and who may listen to recordings, by role.
5. Be able to correct or delete a person’s record on request, including from agents’ phones.
6. Decide how long you keep call history and recordings, write it down, and delete what is older.

Turning rules into daily operations

The difference between a compliant team and a lucky one is that the compliant team’s rules run inside the tools. Calling hours are checked before the dial. Attempt limits stop the pattern that reads as harassment. A do-not-call request is an outcome that closes the lead and blocks further dialing, not a note. Templates are the only way to message. Recording access is a permission. Deletion requests are handled from one screen and propagate to every device. Choose software that lets you configure these, then audit them quarterly.