AvA runs the conversations a lender or insurer has thousands of a month: loan enquiries in the first minute, documents collected on WhatsApp, polite reminders before and after a due date, and renewals, each one checked against the contact rules before it goes out and kept on the record after.
Starts from the Lending & collections edition, installed in one go.
Each agent has one job. Journeys decide who acts next for each person, and every touch is checked against the rules first.
An applicant who fills a form tonight has applied somewhere else by the time your team calls tomorrow.
A missing ID photo or bank statement holds a disbursal for days, and chasing it is somebody’s whole job.
Reminders, promises to pay, disputes and follow-ups, all tracked in spreadsheets, all needing the right hours and tone.
Who was called, when, with what consent, and what was said. An auditor asks; most teams cannot answer quickly.
Each agent is an AvA assistant with its own voice, language and knowledge. They come back with typed answers, not transcripts to read.
Calls every enquiry within the minute and finds out if they are eligible.
Collects documents on WhatsApp and reads them into your records.
Reminds politely, sends a payment link, and waits for the payment to land.
Brings policyholders and borrowers back before something lapses.
Answers customers in their language, from your own documents.
The loan-enquiry questions are an example. You set your own in the same picker, and every one becomes a column you can filter and export.
An illustration of how the pieces work together, not a customer’s data.
Each one opens in the visual journey builder, so you can move a step, change a wait or add a branch, then test it on your own phone before it reaches a customer.
Every call and message is checked before it goes out, for that person, at that moment. Not once per list.
The window the RBI sets for recovery calls. A journey marked for collections cannot call outside it, whatever else is set.
Service, transactional, collections or promotional. The purpose decides the contact rules that apply to each person.
A consent ledger per person, the do-not-disturb register checked, and one “stop” ends every channel and every journey.
Recording switched per number. Recordings open through short-lived links, only for people allowed to see that campaign.
Roles, record-level access, SAML single sign-on, SCIM and an audit trail of every sensitive action, exportable.
Export or erase a person’s data with a receipt, retention periods per kind of data, and a breach register with the deadlines worked out.
Summaries of what AvA checks, not legal advice. More on the Trust page.
Payment links, renewals, KYC on WhatsApp and a daily dues count. The assistants, journeys and tables arrive as drafts in your console, wired to each other. Three things to do before it runs:
Business lenders and insurance brokers can use AvA Prospect to find businesses by industry and place, from Google Maps or India’s company register, and start outreach on the channel each one answers.
Pick one and AvA opens with it in the box. It writes a plan, you press Build, and your phone rings with the result.
Call every loan enquiry from my website within a minute, ask loan amount, income and city, and put the eligible ones through to my loan officer.Build this
Remind borrowers three days before their EMI on WhatsApp with a Razorpay link, call the ones who have not paid by the due date, and note any promise-to-pay date.Build this
Collect PAN photos on WhatsApp from everyone on my KYC pending list and file them in a table.Build this
Call policyholders 30 days before renewal, send the payment link, and pass any dispute to my team.Build this
No. A journey marked for collections is held to 08:00–19:00, the window the RBI sets for recovery calls, and the account cannot widen it. Outside it the person gets a message straight away (if they have agreed to messages) and the call waits for the window.
Politely and briefly. The collections assistant is written never to threaten, shame or pressure anybody; it says who is calling and why, asks when they can pay, offers a link, and ends the call if they ask it to stop. A dispute goes to your team, not into an argument.
Yes, if your system has an API. Add it by its OpenAPI description and AvA lists every endpoint, marked as reading or changing data; journeys and assistants then use the ones you allow. Google Sheets, webhooks, Zapier and Make cover the rest.
In cloud storage, not in the database, opened through links that expire after 15 minutes, and only by people allowed to see that campaign. Recording is a switch per number, so a line can be left unrecorded.
Not yet. What it has today is on the Trust page: the consent ledger, per-country contact rules, roles and record-level access, single sign-on, SCIM, an exportable audit trail, data-rights requests and a breach register. We send our data processing agreement on request.
