Short answer: if your virtual number is used for inbound calls that customers choose to make, DND does not restrict you — India's preference framework governs unsolicited commercial communication that you send. The obligations that do apply are around recording announcements, retention, and — if you start dialling out for marketing — registration.
This is an operational summary of how businesses usually set this up, not legal advice. Anything sector-specific, and anything involving outbound campaigns at scale, is worth putting in front of someone who advises on telecom compliance.
The Distinction That Resolves Most of the Confusion
Almost every anxious question about DND and business numbers dissolves once you separate two things:
| Inbound — customer calls you | Outbound — you call them | |
|---|---|---|
| Unsolicited? | No — the customer initiated it | Depends entirely on purpose and consent |
| DND / preference rules apply? | No | Yes, for promotional content |
| Registration obligations | Not triggered by receiving calls | Applies to commercial campaigns |
| Recording announcement | Yes, tell the caller | Yes, tell the called party |
| DPDP applies to the recording | Yes | Yes |
Owning a business number and answering it is not a regulated marketing activity. Publishing a number and taking enquiries carries no DND exposure at all.
Exposure begins the moment you dial out with something promotional. That is a different activity, with a different setup — covered in TRAI regulations for AI calling in India and the DND registry and TRAI compliance.
Call Recording: The Four Things to Get Right
1. Tell the caller
The safe operating rule is simple: announce it, at the start, before anything substantive is said. One line in the greeting is enough, and it is far cheaper than any argument about whether consent was implied. This is why announcements are usually configured on the IVR greeting rather than left to individual staff to remember. A call recording disclosure generator drafts that one line for you.
2. Know why you are recording
A recording needs a purpose you could state plainly — training, dispute resolution, order accuracy, regulatory obligation. "Because we can" is the answer that causes problems later, and it is also the one that leads to indefinite retention.
3. Set a retention period and actually apply it
Thirty to ninety days covers most training and dispute needs. Regulated sectors have their own requirements that override this. The pattern to avoid is unbounded retention with no stated purpose — it increases what a breach would expose, for no operational benefit.
4. Control who can listen
Recordings of identifiable people are personal data under the DPDP Act. Access should be limited to people with a reason, and that is an access-control decision, not a telephony one. See DPDP Act compliance for voice and call recording compliance.
Recording is available on the ₹499 Business plan and above — see call recording and the pricing page.
If You Start Calling Out
The moment outbound becomes promotional, the picture changes and you should plan for it properly rather than discovering it mid-campaign.
- Purpose decides everything. A transactional call — an order update, a delivery window, an appointment reminder the customer asked for — sits differently from a promotional one. Be honest with yourself about which you are making; a "reminder" that is mostly an upsell is an upsell.
- Commercial campaigns run through registered channels, with registered headers and templates. Treat that registration as part of campaign setup, not an afterthought.
- Keep consent evidence. Whatever your basis for calling someone, you should be able to show where it came from and when.
- Honour opt-outs immediately and permanently, across every channel, including calls placed by a different team.
A fuller walkthrough across frameworks is in the voice AI compliance checklist.
Why This Is Easier on a Virtual Number
Compliance on personal mobiles is mostly hope. On a business number it is configuration:
| Personal mobiles | Virtual business number | |
|---|---|---|
| Recording announcement | Depends on each person remembering | Configured once in the greeting |
| Retention policy | Whatever is on the handset, indefinitely | Set centrally |
| Who can access recordings | Whoever holds the phone | Account access control |
| Evidence of what was said | Usually none | Call logs and recordings |
| Applying an opt-out | Person by person | Centrally, on the system |
The real advantage is evidencability. A policy you cannot demonstrate is, in practice, not a policy — and a handset-based setup cannot demonstrate anything. See call logs and analytics.
Settings are configurable yourself at voice-app.edesy.in.
A Short Operating Checklist
- Recording announcement is in the greeting, before anything substantive
- A one-line written statement of why you record
- A retention period is set, and it expires things
- Access to recordings is limited to people with a reason
- Inbound and outbound are treated as separate activities with separate rules
- Any outbound promotional calling runs through properly registered channels
- Opt-outs are applied centrally and permanently
- Sector-specific rules — lending, healthcare, insurance — checked separately
Common Questions
Can customers on DND still call my business number?
Yes. Preference registration restricts unsolicited commercial communication sent to a person. It has no effect on calls they choose to make.
Do I need to announce recording on every call?
Announce it at the start of any call that will be recorded. Putting it in the greeting means it happens on every call without anyone having to remember.
Is recording without telling the caller illegal?
Rather than arguing the edge cases, treat announcement as mandatory operating practice. It is one line of audio and it removes the entire class of dispute.
Does DPDP apply to call recordings?
Recordings of identifiable individuals are personal data, so purpose limitation, retention and access controls all apply. See DPDP Act compliance for voice.
Are appointment reminders promotional?
A reminder for something the customer booked is transactional. A "reminder" carrying an offer is promotional, and should be treated as such regardless of what it is called internally.
Does any of this change if an AI answers the call?
The obligations are the same, and disclosure becomes an additional consideration. See TRAI regulations for AI calling.