Top questions
What is Captain, exactly? A chatbot or something else?
An AI workforce for the dealership. Each skill is a role, reception, sales, after-sales, leasing, marketing, quality, with a name, access to your systems and a job to finish. A chatbot waits for a keyword. Captain carries the conversation to an outcome: an answer, a booking, a follow-up, a score.
Which channels does it work on?
WhatsApp, web chat, phone calls, Instagram, Facebook Messenger, Telegram and email. One Captain with one memory across all of them: a customer can start on WhatsApp in the evening and finish on a call the next morning without repeating anything.
Does it book into our real calendar and read our real stock?
Yes. Captain reads live stock, prices and offers from your DMS or a feed, and books into the calendar your team actually uses. It never promises a car that is not in stock and never books a slot twice.
What happens when a customer is upset or asks for a person?
Captain hands over. It recognises frustration, a complaint or a request for a manager, apologises once and brings a person into the same chat, or transfers the call warm with a one-line summary. When the person is done, Captain picks the thread up again.
Getting started
How long does it take to go live?
About two weeks. We train on your stock, prices, offers and rules, test with your team, and go live on one channel first. Adding the next channel takes days, not weeks.
What do we need to provide?
Access to the calendar and the stock, your price list and current offers, and a short questionnaire about how you sell and what may be promised. Captain reads your website too, so hours and offers that change there change in Captain as well.
Can we start with one channel or one rooftop?
Yes, and most clients do. WhatsApp or calls on one rooftop is the usual first step. Once the numbers are in, the same setup extends to the other channels and rooftops.
Can we run it for several brands or rooftops?
Yes. Each brand and each rooftop gets its own models, stock, prices and hours, kept apart, under one account and one report. Mono-brand showrooms and multi-brand marketplaces run on the same setup.
Day to day
Which languages does it speak, and how well?
98 languages, in text and on the phone. Captain answers in the language the customer writes or speaks in and switches mid-conversation if they do. Arabic, English, Hindi, Urdu and Russian are the ones we tune most for the GCC.
Will customers know they are talking to AI?
Yes, if they ask, Captain says so. Most do not ask: they get an answer in seconds, in their language, that solves their question. We recommend introducing Captain by name in the first message, and every client so far has kept it that way.
Does it replace our people?
It takes the work nobody gets to: the call at 22:00, the third follow-up, the status question, the scoring of every conversation. Your team keeps the conversations where a person changes the outcome. Most clients redeploy people to those, rather than cut them.
How much of our team’s time does it need?
About an hour a week: a look at the conversations Captain flagged, and a word when an offer or a rule changes. Everything else it picks up from your systems and your website.
How do we measure that it works?
In your own numbers: calls answered, replies within a minute, test drives booked, visits kept, and the share of conversations closed without a person. Captain reports them weekly, and every conversation is recorded and scored, so you can open any of them and check.
Data and security
Where is our data stored, and who can see the conversations?
Conversations, customer data and recordings belong to you and stay in your region. Access inside the dealership is by role. We see data only to operate the service and never use it to train models for other clients.
Are calls recorded, and do customers know?
Yes, calls and chats are recorded, that is what the scoring and the hand-off summaries are built on. Customers are told at the start of a call, in the wording your legal team approves for your market.
What about OEMs that cannot export data?
For OEMs and groups with data-residency requirements we agree the deployment model case by case, including running inside their own infrastructure.
Still a question?
I have a question that is not here.
Book a demo and ask it live.