Buyer's guideNo named competitors

Choosing a calling or telecalling system in India

DND compliance is not optional and not a checkbox — it is a gate that has to hold on every path a call can be queued from. Six questions about consent, calling hours, and what happens when an AI voice agent wants a person on the line — with Automix's own honest answer to each.

See what Wani already does Read the technical docs

What this guide will not do

No named or characterised competitorNo invented statistic or ratingHonest where our own answer is a limit

Before you buy

A DND scrub that only runs on one entry point is not a DND scrub.

A calling system in India sits under specific regulatory pressure the rest of this market does not — the National Do Not Disturb registry, consent requirements, and calling-hours restrictions that apply regardless of which product places the call. The question worth asking is not whether a tool 'supports DND compliance' as a headline feature, but whether that compliance check runs on every single path a call can be queued from: a manual dial, an outbound campaign, an AI voice agent, an appointment reminder triggered by another system entirely.

Six questions follow, with Automix's honest answer to each about Wani, the telecalling agent — including the parts that work fully today with no telephony provider connected, and the parts that stop at 'ready to dial' because placing an actual call needs one.

Ask what it refuses to do

A tool with no refusals has not thought about the edges of your business.

These are specific refusals in Automix's own code, named so you can ask the same question of anything else you evaluate.

It will not permit promotional dialling to a number with an unknown DND status

Until the National DND registry feed is connected, an unknown answer blocks promotional dialling by default rather than permitting it — the safer failure direction, not the more convenient one.

It will not let a promotional voice agent label itself a service call to dodge the DND scrub

A voice agent's purpose is evaluated from its own declared category, not one the caller supplies when queueing — the loophole of relabelling a promotional call as a service call is closed at the queueing layer itself.

It will not let the AI-disclosure or human-handoff step be removed from a call script

The normaliser re-inserts both nodes on every write to a flow. Wording is editable; their existence in the flow is not — deleting them does not take effect.

Evaluation criteria

6 questions to ask any vendor in this category.

Ask these of Automix and of anything else on your shortlist. The status pill is how the honest answer scores today, not a claim of perfection.

Does the DND and consent check run on every path a call can be queued from — or only the obvious one?

Why it matters. A compliance gate that runs on the manual-dial screen but not on a bulk campaign import, an API call from another system, or an AI voice agent's own queueing logic is not a real gate — it is a gate with a documented way around it. The specific test: can any code path reach the dialler without passing through consent and DND logic first?

How Automix answers it. Consent capture with basis-derived expiry, permanent opt-out, the workspace suppression list and the blocked-dial log all run locally, and no queue or dial route can be reached without passing through them first. The National DND registry feed itself needs a telecom access-provider credential; until one is connected, a phone number with an unknown DND status blocks promotional dialling rather than permitting it by default.

Needs your setup

Are calling-hours rules a display setting, or something the system actually enforces regardless of who initiates the call?

Why it matters. Permitted-hours restrictions matter most when a person is not watching the queue — an automated campaign, a reminder job, an AI agent working through a list overnight. A rule that only shows on a dashboard and does not stop the dial itself is not an enforcement mechanism.

How Automix answers it. The permitted calling window is evaluated in the recipient's own local time zone, and a call outside it is deferred with a visible next-attempt time rather than placed. The regulatory bound is enforced with database CHECK constraints, so a workspace can narrow the window further but nothing in the product can widen it past the regulatory limit.

Works today

Can a promotional call disguise itself as a service call to get around the DND scrub?

Why it matters. This is a specific and easy-to-miss loophole in any system built around 'purpose' categories: if the caller (a human agent, an automation, a voice AI) gets to declare its own purpose when queueing a call, a promotional campaign can simply label itself a service call and walk past whatever gate only applies to promotional dialling.

How Automix answers it. A voice agent queues through the same single helper as every other entry point and is evaluated against its **own** declared purpose, not one the caller supplies at queue time — so a promotional agent cannot label itself a service call to skip the DND scrub. Compliance gate, deferral, per-contact frequency caps and escalating retry backoff all run locally. Dispatch ends at awaiting-provider: placing the actual call needs a telephony credential.

Needs your setup

Can a call be recorded without a stored, mandatory record of consent?

Why it matters. Call recording without disclosed consent is both a compliance risk and an ethical one. The specific test: is consent a checkbox in a settings screen that can be left unchecked, or a database-level requirement the recording literally cannot exist without?

How Automix answers it. The consent reference on a recording is a NOT NULL column — a recording that names no disclosure cannot be written to the database at all, not a setting that happens to default to off. A mandatory retention clock is enforced alongside it. Capturing the actual audio needs a provider recording API and encrypted object storage.

Needs your setup

If an AI voice agent handles a call, can its disclosure or human-handoff option ever be turned off?

Why it matters. A voice AI that can be configured with no disclosure of what it is, or no way to reach a person, is a voice AI configured to deceive by omission. The question worth asking a vendor directly: is disclosure a default that can be switched off, or a fixture of every flow the system generates?

How Automix answers it. Three ways exist to build a call script — templates, a hand-built configuration, or a plain-English description — and all three write through the same normaliser, which re-inserts the AI-disclosure and human-handoff nodes on every write. Deleting them from a flow does not take effect: wording is editable, existence is not. A collections agent's copy is refused before the row even exists if it reads as a debt-collection threat, enforced by a database CHECK constraint rather than a setting that could be skipped.

Works today

When nothing has an outcome yet, does the connect-rate metric show zero — or admit it does not know?

Why it matters. A freshly launched calling campaign with no completed calls yet has a true connect rate of 'unknown,' not zero. Reporting zero is a false statement about performance dressed up as an empty state, and it can make a brand-new campaign look like a failing one before it has had a chance to run.

How Automix answers it. Connect rate and average talk time are reported as null rather than zero when nothing has an outcome yet. Daily volume, outcome breakdown, and blocked-dial counts are drawn only from this workspace's own rows.

Works today

Where we do not measure up yet

In one place: which of the answers above is not a green light.

Pulled straight from the criteria above, not a separate list — a guide that scores itself full marks on every criterion is not one you should believe, ours included.

Does the DND and consent check run on every path a call can be queued from — or only the obvious one?

Consent capture with basis-derived expiry, permanent opt-out, the workspace suppression list and the blocked-dial log all run locally, and no queue or dial route can be reached without passing through them first. The National DND registry feed itself needs a telecom access-provider credential; until one is connected, a phone number with an unknown DND status blocks promotional dialling rather than permitting it by default.

Needs your setup

Can a promotional call disguise itself as a service call to get around the DND scrub?

A voice agent queues through the same single helper as every other entry point and is evaluated against its **own** declared purpose, not one the caller supplies at queue time — so a promotional agent cannot label itself a service call to skip the DND scrub. Compliance gate, deferral, per-contact frequency caps and escalating retry backoff all run locally. Dispatch ends at awaiting-provider: placing the actual call needs a telephony credential.

Needs your setup

Can a call be recorded without a stored, mandatory record of consent?

The consent reference on a recording is a NOT NULL column — a recording that names no disclosure cannot be written to the database at all, not a setting that happens to default to off. A mandatory retention clock is enforced alongside it. Capturing the actual audio needs a provider recording API and encrypted object storage.

Needs your setup

Questions

Common questions.

Does Wani actually place calls today?

Queueing, compliance gating, scripting and analytics all work locally. Placing the actual call needs a connected telephony credential, which is the honest gap this deployment has right now.

What happens to a call queued outside permitted calling hours?

It is deferred, not dropped or placed anyway — the queue shows a visible next-attempt time inside the recipient's own local permitted window.

Can a business narrow the calling-hours window further than the regulatory default?

Yes — a workspace can restrict its own calling window further. What it cannot do is widen the window past the regulatory bound, which is enforced with a database constraint rather than left to a setting.

Is recording a call ever possible without the customer's consent being on record?

No — the consent reference is a required, non-null field on the recording row itself. There is no path to a stored recording with an empty consent reference.

Can I turn off the AI disclosure to make a voice agent sound more human?

No — the disclosure and human-handoff nodes are re-inserted into every flow on every write, regardless of how the flow was built. Their wording can be edited; their presence cannot be removed.

Is Wani available to use today?

Not yet — its status is Coming soon. There is no public product page for it yet either, which is why this guide links to its documentation and its listing instead.

Apply it

Apply these six questions to Wani, and to whatever you use today.

The compliance gate, calling-hours enforcement and script disclosure all run today with no telephony provider connected. Ask any telecalling system you evaluate to show you the same, on every path a call can be queued from — not just the one it demos.

See what Wani already does Read the technical docs

Wani's own status today:Coming soon

More buyer's guides

Buyer's guide

How to choose a WhatsApp business tool

Six questions that matter more than the feature list any vendor hands you — plus the one constraint every tool built on Meta's Cloud API shares, whether its marketing page mentions it or not.

Read the guide

Buyer's guide

What to look for in a CRM for a small sales team

The feature list on a CRM's homepage is never the reason a required field gets skipped six months in. Six questions about what actually holds under an import, a bulk edit, or a rushed Friday afternoon — plus Automix's own honest answers.

Read the guide

Buyer's guide

Choosing a social media scheduling tool

The word 'scheduled' hides more than it reveals. Six questions about approvals, invented engagement data, and what actually happens when a post's date arrives — with Automix's own honest answer, including the one place nothing actually publishes yet.

Read the guide

Choosing a calling or telecalling system in India

What this guide will not do

No named or characterised competitorNo invented statistic or ratingHonest where our own answer is a limit

Choosing a calling or telecalling system in India

A DND scrub that only runs on one entry point is not a DND scrub.

A tool with no refusals has not thought about the edges of your business.

It will not permit promotional dialling to a number with an unknown DND status

It will not let a promotional voice agent label itself a service call to dodge the DND scrub

It will not let the AI-disclosure or human-handoff step be removed from a call script

6 questions to ask any vendor in this category.

Does the DND and consent check run on every path a call can be queued from — or only the obvious one?

Are calling-hours rules a display setting, or something the system actually enforces regardless of who initiates the call?

Can a promotional call disguise itself as a service call to get around the DND scrub?

Can a call be recorded without a stored, mandatory record of consent?

If an AI voice agent handles a call, can its disclosure or human-handoff option ever be turned off?

When nothing has an outcome yet, does the connect-rate metric show zero — or admit it does not know?

In one place: which of the answers above is not a green light.

Does the DND and consent check run on every path a call can be queued from — or only the obvious one?

Can a promotional call disguise itself as a service call to get around the DND scrub?

Can a call be recorded without a stored, mandatory record of consent?

Common questions.

Apply these six questions to Wani, and to whatever you use today.

Evaluate the rest of your stack.

How to choose a WhatsApp business tool

What to look for in a CRM for a small sales team

Choosing a social media scheduling tool

Choosing a calling or telecalling system in India

A DND scrub that only runs on one entry point is not a DND scrub.

A tool with no refusals has not thought about the edges of your business.

It will not permit promotional dialling to a number with an unknown DND status

It will not let a promotional voice agent label itself a service call to dodge the DND scrub

It will not let the AI-disclosure or human-handoff step be removed from a call script

6 questions to ask any vendor in this category.

Does the DND and consent check run on every path a call can be queued from — or only the obvious one?

Are calling-hours rules a display setting, or something the system actually enforces regardless of who initiates the call?

Can a promotional call disguise itself as a service call to get around the DND scrub?

Can a call be recorded without a stored, mandatory record of consent?

If an AI voice agent handles a call, can its disclosure or human-handoff option ever be turned off?

When nothing has an outcome yet, does the connect-rate metric show zero — or admit it does not know?

In one place: which of the answers above is not a green light.

Does the DND and consent check run on every path a call can be queued from — or only the obvious one?

Can a promotional call disguise itself as a service call to get around the DND scrub?

Can a call be recorded without a stored, mandatory record of consent?

Common questions.

Apply these six questions to Wani, and to whatever you use today.

Evaluate the rest of your stack.

How to choose a WhatsApp business tool

What to look for in a CRM for a small sales team

Choosing a social media scheduling tool