Coru
Book a demo

ADI AGENTS · ONBOARDING

From approval to first transaction

Sign-up and activation guided by voice, WhatsApp or web, with deterministic identity validation at every sensitive step.

Identity validated by deterministic rules, returning approved or rejected
Sign-up variables arrive by webhook — the customer never repeats what is known
The channel changes and the conversation continues: no completed step is repeated
Hand-off to a human with the whole history and the data already collected
ISO 27001 PCI SOC 2
14:32 ▮▮▮ ⌁ 84%
ADI · Example Bank online
Hello, Marcos. I am ADI. Your account is approved — two steps left to activate it. 14:30
Message

The operational jump

Approved is not activated

Both models start from the same approved sign-up. What changes is how many reach the first transaction.

Email activation and a human queue

× Between approval and first use sits a drop-off that never shows in the acquisition report
× Document friction: every photo, validation and confirmation step is a drop-off point
× The customer switches channel and starts from scratch
× Back office manually reviews cases that are identical to each other
× The rest is absorbed by the operation in manual calls

ADI onboarding agent

Identity validation outside the model, with a binary result
Personalisation from dynamic variables received at the start of the conversation
Resumption across WhatsApp, voice and web without repeating completed steps
Extraction at close, over the full transcript
Escalation with the full thread when the case needs human judgement

Results in production

Impact that is measured

Aggregated platform results, measured in production. Not attributed to any specific account.

70% of volume automated, with human relief on demand
<800 ms time to first byte of a voice response
1–3 weeks from defined case to production

How it runs

From approval to an active account

01 · TRIGGER

Approved sign-up

The agent is triggered with name, account number and sign-up status received by webhook.

02 · CONTACT

On the customer's channel

WhatsApp, voice, web widget or app webview, with the same script and the same context.

03 · IDENTITY

Deterministic validation

Format, check digit and lookups against your sources run in code, outside the model.

04 · DOCUMENT

Frictionless capture

Guided upload inside the conversation, verified in a dedicated service returning approved or rejected.

05 · SETUP

Passcode and preferences

The agent runs the last steps and stays until the account is usable.

06 · RECORD

Data in your system

Fields defined in Data Collection, extracted from the transcript and delivered by signed webhook.

Capabilities

Activating without a queue

Validation outside the model

Verification runs in a dedicated service and returns approved or rejected, with no room for interpretation.

Dynamic variables

Name, account number and status arrive by webhook at the start of the conversation.

Cross-channel resumption

Starts on WhatsApp, continues on voice, ends on the web. No completed step is repeated.

Extraction at close

Every field is defined beforehand in Data Collection, with a type and a natural-language instruction.

Correct local pronunciation

CPF, CNPJ, CURP and contract numbers read as a trained agent would read them.

Escalation with the full thread

The operator arrives reading, with the history and the data already collected.

Feasibility

Connects to what you already have

Validation sources, core and CRM connected through a documented interface. No core changes.

WhatsApp Business PSTN voice Web widget App webview REST APIs · JWT HMAC webhooks HTTP Tools MCP
Timeline

Onboarding in 1 to 3 weeks. With an existing SIP trunk, the voice channel goes live in 2 to 5 days.

Inside the rules

Activating without leaving policy

PII tokenised at the edge

Personal data is tokenised before any call to a model provider.

Guardrails in code

Deterministic filters before and after the model, three of them mandatory on any agent.

Traceability

Every interaction reconstructable: what the agent said, on which version, under which controls.

Closed catalogue

The agent executes only actions registered as enums validated outside the model.

FAQ

Frequently asked questions

Does the model decide whether the identity is valid?

No. Validation runs on deterministic rules in a dedicated service, returning approved or rejected. The agent runs the capture and communicates the result, without assessing the document.

Do we need to change our KYC provider?

No. Validations are configured against your current sources, called through HTTP Tools during the conversation.

Does the customer start over when switching channel?

No. Context travels across WhatsApp, voice, web widget and app webview, and no completed step is repeated.

How does the data reach our system?

Through a webhook signed with HMAC-SHA256 at close. The fields are defined beforehand in Data Collection, with a type and an instruction per field, and extracted from the full transcript.

And when the case needs a human?

Escalation follows the rule you define, and the operator receives the whole history with the data already collected.

Request a demo

Bring your current activation rate.

The projection comes off your funnel, with the KPI agreed before the pilot starts.

What you bring

Approved volume, current activation rate and the point in the funnel where drop-off concentrates.

What we bring

Benchmarks measured in production, the agent configured against your validation sources and a dedicated compliance liaison.

What comes out

An activation projection, a proposed pilot KPI and the basis of the rollout plan.

Shall we start?

Please use your work email.

By submitting you accept our privacy policy. We do not share your information with third parties.

Newsletter

Insights on AI in regulated operations, once a month.

Governance, architecture and what happens after go-live. No spam.

By subscribing you agree to receive communications from Coru.