Why we don’t do bulk outbound calling

What the rules actually say

Unsolicited commercial communication in India sits under TRAI’s regulations, which are stricter than most people assume and have been tightened repeatedly. The framework requires senders of commercial communication to be registered, requires the content and the sending entity to be recorded, and requires recipient preferences to be honoured. Consent is meant to be verifiable rather than assumed.

The DPDP Act 2023 adds a second layer on the data side. If you are calling people, you are processing their personal data, and that needs a lawful basis, a stated purpose and a notice. A list bought from someone else does not come with any of those attached, whatever the seller said.

None of this is legal advice, and the enforcement picture changes. But the direction of travel has been one way for a decade, and building a product that depends on the rules getting looser is not a good bet.

The practical consequence is worse

Regulatory risk is slow. Losing your number is fast.

Recipients report calls they did not ask for. Carriers act on volumes of reports, and increasingly so do the handsets themselves — a number with enough reports gets labelled as spam on the recipient’s screen before it rings, or stops connecting. That happens to the number, not to the campaign.

For a business whose customers call it, this is a serious failure. The number on your signage, your listings and your invoices is now flagged, and the customers you actually want are the ones who cannot reach you. It is not a reversible mistake in any convenient timeframe.

The usual workaround is to burn a separate number per campaign, which tells you what the practice is worth: an approach whose own operators will not run it from a number they care about.

What we do instead

Outbound in VokaLQ runs against the business’s own contacts — the people it already has a relationship with and a lawful basis to call. In practice that is enquiry follow-ups, reminders, feedback after a job, registration and admission drives where the person signed up, and reactivating customers the business has served before.

Following up on an enquiry. Somebody rang, asked about a service, and has not been called back. The follow-up call already knows who they are and what they asked, which makes it a continuation rather than an interruption.

Feedback after a job. A short call to a customer whose appointment is finished, asking how it went, with the answer recorded against their record.

A campaign against a list the business owns. Its own customers, its own enquirers, its own registrants — imported as a spreadsheet, called inside the permitted window, with DLT registration and consent sorted out before the first call goes out.

The difference is not a technicality. Every one of these is a call the recipient can place immediately, from a business they have dealt with, about a thing they wanted. That is the property that makes an outbound call acceptable, and it is exactly the property a purchased list cannot have.

If bulk calling is what you need

Then this is the wrong product, and it is better to find that out now than after a setup fee.

It is worth being honest about why the option is attractive. Outbound at volume is measurable in a way that answering the phone is not: you can point at calls made and leads generated. Inbound coverage shows up as an absence — the customers who did not go elsewhere — and absences are hard to put in a report.

What we would say is that the arithmetic usually favours the boring option anyway. The people already ringing your number have chosen to contact you, and a meaningful share of them are currently reaching nobody. Converting those is cheaper than manufacturing new ones, and it does not put the number on your signage at risk.