Trust and rules
The reason most businesses are nervous about AI calling is not the technology — it is what an unsupervised machine might say to their customer. This is how DiaConn is built so that cannot happen.
Five things owners fear
The risk
One over-eager sentence about a claim ratio, a guaranteed return or an admission seat becomes your problem, months later, with no recording to check.
How it is prevented
Every line the AI can say comes from an approved library. Claims that need approval are blocked at the gate, and every word is transcribed and searchable.
The risk
A 10:40pm marketing WhatsApp does more damage to your brand than the enquiry was worth.
How it is prevented
Quiet hours are enforced per business and per campaign. Outside your window, the ladder simply waits.
The risk
Two telecallers and a campaign all reach the same person in one afternoon. They stop answering everyone.
How it is prevented
Frequency caps and a single shared ladder per person. When one channel gets a reply, every other queued touch is cancelled.
The risk
Opt-outs live in one person's memory, or in a column nobody filters on.
How it is prevented
Consent state is checked on every single send, across every channel, and an opt-out is permanent unless the customer themselves reverses it.
The risk
A complaint arrives and the desk reconstructs the story from memory and a few WhatsApp screenshots.
How it is prevented
Full transcript, timestamps, which gate passed, who approved the template and which person touched the lead — kept per business.
The ten gates
Every call, WhatsApp message, SMS and email runs the same chain. If a gate fails, the send is blocked and the reason is written down — visible to you in the console, message by message.
Consent, matched to purpose
Permission for a service reminder does not authorise a festival greeting. Purpose is stored with the opt-in and re-checked at send.
Opted out or complained
Permanent. No campaign, no exec and no copilot verb can override it.
Frequency cap
Max 2 non-transactional touches in 30 days, counted per person and not per campaign.
Fatigue
Four non-opens in a row rests the contact for 21 days instead of pushing harder.
Cooling off
14 days of silence after any complaint, delivery failure or refund.
Quiet hours
Nothing between 9pm and 9am IST. Messages are held in queue, never dropped.
Token integrity
No "Happy Diwali, {{first_name}}". Any unresolved token fails the whole batch row.
Region and language
Never infer religion or language from a name. Where the attribute is unknown, the record is excluded rather than guessed.
Deduplicate
One occasion, one message — even when three journeys all qualify the same person.
Human sign-off above cap
Any audience above 2,500 people waits for a named person to approve.
Data
One business's leads, recordings and templates are never visible to another. Access is enforced in the database itself, not only in the screens.
Owner, sales desk, and our own platform staff each see a different console. Staff access to a client workspace is logged.
Configuration changes, approvals, handovers and outreach attempts are all recorded with who did it and when.
Recordings and transcripts are kept for the period you choose, and deleted on request for a specific customer.
Bring your compliance or legal person to the demo. The gate log is the first screen we will open.