Portal and ad enquiries arrive in bursts, often at night. AvA calls each one within the minute, asks budget, locality and configuration, puts the buyers who are ready straight through to your sales team, and books a site visit for the rest, then keeps in touch until they decide.
Starts from the Real estate 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.
A buyer messages three developers at 11 pm. Whoever calls first usually gets the site visit.
A good closer spends the morning on people who were never going to buy, while a ready buyer waits.
A visit booked on Monday is forgotten by Saturday unless somebody reminds, sends the location and rebooks.
Thousands of past enquiries sit in the CRM. Nobody has time to find out which of them are ready now.
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 qualifies it on the call.
Judges intent on the call and puts ready buyers through to a person, live.
Books visits, sends the location and makes sure they turn up.
Keeps in touch on WhatsApp until a buyer is ready, and wakes up old leads.
Reminds buyers of each milestone payment, with a link.
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.
Calling hours, the do-not-disturb register and consent are checked before every call and message, not once per list.
Frequency caps across every journey, so a buyer in two campaigns is not called twice in an afternoon.
On every channel and every journey, at once, and it is never cleared by an import.
The property assistant is written not to state prices, availability or possession dates unless you have written them in.
A prepaid balance, a spend ceiling on each journey, a daily limit and one switch that pauses everything.
Record-level access for each salesperson, and white-label accounts for channel partners on your own brand.
Summaries of what AvA checks, not legal advice. More on the Trust page.
Speed-to-lead, live transfer to sales, and portal enquiries. The assistants, journeys and tables arrive as drafts in your console, wired to each other. Three things to do before it runs:
Commercial leasing and co-working teams can use AvA Prospect to find businesses in an area, see why each one fits, and start outreach.
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 portal and ad enquiry within a minute, ask budget and location, and book a site visit.Build this
When a buyer says they want to buy this month, put them straight through to my sales manager.Build this
Message everyone who enquired more than 30 days ago on WhatsApp, and call the ones who reply.Build this
Remind buyers on WhatsApp before each instalment with a Razorpay link.Build this
Within the minute it arrives, inside your calling hours. An enquiry at night gets a WhatsApp message straight away and a call when the hours open.
Yes. Add your sales team as transfer destinations on the assistant; when a buyer is ready it puts the call through by name. The assistant never dials a number it was not given.
Only what you have written in. The property assistant is instructed to say the sales team will confirm anything else, rather than guess.
Into your console as typed answers (budget, locality, configuration, purpose) you can filter and export, and to HubSpot, Zoho CRM or any webhook. Salesforce, Pipedrive and GoHighLevel are coming.
