One question at a time
Visitors answer in plain words, and each answer decides the next question. A buyer and a seller get different ones.
A lead capture chatbot talks to visitors on your website and asks what your team would ask on the first call. The answers reach you as one complete enquiry.
Book a free consultation
The contact form has a message box, and the message says "Interested, please call." So someone calls back to ask what they need, where, by when and roughly what budget they have in mind. Some never pick up. A longer form collects the details, but some people close the page when they see twelve fields.
Asks the first questions and sends sales a complete enquiry.
Visitors answer in plain words, and each answer decides the next question. A buyer and a seller get different ones.
People often want an answer before they give any details, such as how the first meeting works. It answers from information you approve, then asks for details once they want to go ahead.
Your team gets a short summary with the contact details and every answer, instead of a chat transcript. It goes to the right person, or into your CRM where its API allows.
If an enquiry matches what you told us to watch for, such as a start date this month or a budget above a level you set, it is marked so your team calls it first.
Write down what you ask every new enquiry and which answers make you call back fast. A few real enquiries with the names removed help us test it, and the name of your CRM tells us where enquiries can go.
In this order, and nothing goes live before you have tried it.
We go through the questions you ask a new enquiry and note the answers that change what happens next. They become the chatbot's questions.
Together we decide which answers matter most and which person gets which kind of enquiry.
Each enquiry goes to an inbox or, where its API allows, straight into your CRM with each answer in its own field. A failed connection sends an alert, and the enquiry waits for review.
We run past enquiries through it, vague ones included, and check that each summary is something your team can act on. You try it yourself before launch.
What it looks like in a few kinds of business.
Viewing and valuation requests sent to the right agent.
Stock questions answered, with test drives and trade-ins passed on.
Quote requests and policy changes, without advice on cover.
First call requests and document reminders, without mortgage advice.
For some businesses. A form suits people who know what they want. A chat suits people who have a question first, and it can ask follow-up questions a form cannot. You can keep both.
Often, through the CRM's API. We check what yours allows before we promise it. If it cannot connect, enquiries go to an inbox or a shared spreadsheet in the same format.
It tells them politely when you cannot help, for example when they are outside your area. You decide where that line sits, and whether it suggests somewhere else.
No. It explains how your service works and collects the details an adviser needs. Which product suits someone is for the adviser to say.
It asks only for what your team needs to follow up. We agree where enquiries are stored and who can see them, and your privacy notice is updated to match.
Bring one that came in with too little detail, and the questions you had to ask afterwards. The consultation is free, over Google Meet, a voice call or text.