What Otto handles

Lead handler.
Lead generator.

Inbound voice on your service line. Outbound voice and WhatsApp. The chat widget on your website. Drag-and-drop journeys for the chases that always got skipped. Same Otto across all of it — same customer record, same diary.

Click the chat bubble in the bottom-right corner to try the widget yourself.

Inside Otto

How Otto handles a service drive call.

📞
01
Pick up
Voice, WhatsApp or web chat. First ring, every ring.
🔎
02
Qualify
Reads the vehicle, the history, the customer's intent.
📅
03
Book
Drops the slot into your DMS with the right codes and notes.
🤝
04
Hand off
Warm-transfers anything Otto isn't sure about.
📥
05
Follow up
Chases the no-shows. Re-runs MOT & service campaigns.
✶ Otto · Your AI Service Advisor
01 · Inbound voice on your service line

Otto answers. 24/7.
Forwards to a human when it matters.

Forward your busy lines, your overflow, or your out-of-hours to Otto. Customers hear a calm UK voice that knows their car, your service types, and your diary. When a call genuinely needs a human, Otto warm-transfers to the right advisor with the context already collected.

  • Picks up on the first ring — including weekends, lunchtimes and overnight.
  • Knows the caller's vehicle and service history before saying hello.
  • Books mid-call into your diary with the right advisor codes and job types.
  • Forwards to the right advisor with a one-line brief — "Sarah, courtesy car required, MOT due Friday."
  • Every call recorded, transcribed and reviewable in your dashboard.
Concrete example

A 12-site Audi/VW group forwarded their service overflow to Otto. Saturday morning calls answered: 0 → 84 in the first month. Saturday bookings up 23%. Saturday cover staff redeployed to drive sales.

app.otto.ai/calls/c-91A3

Inbound call · +44 7700 900 921

SAT 09:42 · 38S · BOOKED MOT
✶ AI HANDLED
▶
00:38
"Morning, do you have a slot for an MOT this Saturday? Black Golf, LV21 KFG."00:04
I see the Golf — last service was October. I've got 10:30 or 14:15 on Saturday with a courtesy car. Which works?00:11
"10:30 please."00:23
Booked. Confirmation just gone to your phone. Anything else?00:28
02 · Outbound voice

Otto rings the customers
who haven't booked yet.

Service-due reminders. MOT chase. No-show recovery. Recall outreach. Otto picks up the list each morning and works it on the phone — politely, in your tone, in your hours. Books mid-call when the customer's ready.

  • Calls only inside the hours you choose. Respects regulator and brand rules.
  • WhatsApp first on every list — voice is the fallback when there's no reply.
  • Books straight into your diary, with the right job type and courtesy car.
  • Tags answerphone vs picked-up and only loops back when sensible.
  • Every outbound call recorded and transcribed for review.
Concrete example

A franchised dealer's MOT chase used to be a 4pm-on-Friday spreadsheet. Switched to Otto outbound voice with WhatsApp fallback. MOT capture from the dealer's own database climbed from 41% to 67% in a quarter. No additional headcount.

app.otto.ai/campaigns/mot-chase/dialer
Calling now
James Doyle
LV21 KFG · VW Golf · +44 7700 900 921
Objective
Book MOT before 28 May
Max 90s · Quiet hours respected
Live transcript · AI voice 00:42
Hi James, it's Otto from Wimbledon Motors. Your Golf is due an MOT before 28 May — do you have a moment to find a slot?
"Yeah, can you do Saturday?"
09:30 or 14:00 Saturday with a courtesy car. Either work?
"09:30 please."
Booked. Confirmation sent by text. Thanks James.

Where customers actually reply.

Most workshops have a WhatsApp Business number that nobody really watches. Otto runs it properly. Reads service-due dates from your DMS, reaches out, holds a real booking conversation, confirms.

  • Outbound MOT, service-due, parts-arrival and recall messages.
  • Inbound enquiries answered in seconds, day or night.
  • Holds a thread across days — picks up the conversation where the customer left off.
  • One-tap "stop" handled the way regulators expect. You stay clean.
  • Photos and videos forwarded straight to your service advisor when needed.
Concrete example

An independent multi-marque workshop set Otto loose on its 2,400-strong "haven't been back in 18 months" list. WhatsApp first, voice on no-reply. 312 conversations, 84 bookings, £41k of aftersales recovered in six weeks.

04 · The chat widget on your website

Every web visitor, answered.
Every anonymous lead, captured.

A discreet chat bubble on your service pages. Visitors ask about pricing, courtesy cars, MOT availability — Otto answers, day or night. Where it makes sense, books the slot before the customer leaves the page. Where it doesn't, captures the lead and hands it to a human.

👉 You're looking at it. Click the bubble in the bottom-right of this page.

  • Lives on every page — service, MOT, repairs, even your homepage.
  • Answers price, availability, courtesy car and diagnostics questions.
  • Books the work without the customer needing to fill in a form.
  • Captures contact details from anonymous visitors who weren't ready to book.
  • Hands off to a real advisor in one click for anything complex.
  • Branded — your tone, your colours, your wording.
Concrete example

An OEM-franchised dealer added Otto to its service landing page. Form-fill bookings stayed flat at ~30/month. Otto added 86 booked appointments via the chat in the first 30 days — most of them after 6pm or at weekends.

✶ Otto · Wimbledon Motors
Typically replies in seconds
How much for an interim service on a 2020 Polo?
Interim service on a 2020 Polo is £159, includes a complimentary VHC. We've got Tuesday 08:30 or Thursday 14:00 free — either work?
Tuesday — and can I get a courtesy car?
Yes, attaching one now. Confirmation by text in a moment.
Type a message…
↑
05 · Outbound chase campaigns

The lists you mean to work,
actually worked.

MOT due. Service due. Lapsed customer. Booked but didn't show. Recall outstanding. Otto reads each list from your DMS each morning and works through it — WhatsApp first, voice on no-reply.

  • MOT chase — 4 weeks before, 2 weeks before, day-of.
  • Service due reminders timed to mileage or interval, whichever's first.
  • No-show recovery — same morning, friendly, rebooked into today's gaps.
  • Lapsed customer winback — gentle, on the cars they already trust you with.
  • Recall and parts-arrival outreach the moment your DMS flags them.
Concrete example

A 3-site dealer group switched on the MOT chase. The list went from "we'll get to it" to fully worked, every week. MOT capture rate from their own database climbed from 41% to 67% over the quarter.

app.otto.ai/campaigns

Active campaigns

5 running
Booked this week
87
↑ 23% vs last wk
MOT conversion
38%
↑ from 22%
Aftersales (30d)
£41k
↑ recovered
📅
MOT chase · this week
84 customers · WhatsApp + voice fallback
38% booked
🔧
Service due · 14-day window
142 customers · WhatsApp first
29% booked
↩️
No-show recovery · today
14 missed appointments · same-day call
9 rebooked
💌
Lapsed customer winback
312 customers · 18m+ since last visit
running
⚠
Recall outreach
28 customers · OEM action
21 booked
06 · Journeys · the visual flow builder

Design your own follow-up flows.

Service-due chase, MOT reminders, no-show recovery, lapsed-customer winback — all running on autopilot. Drag-and-drop the trigger, the channel, the wait. Branch on reply or no-reply. Fall back to voice when WhatsApp goes quiet. No code, no agency — just rules in plain English.

  • Triggers from your DMS — service due, MOT due, no-show, recall, lapsed customer.
  • Channel steps: WhatsApp, AI voice call, SMS, email — in any order.
  • Wait steps in days or hours, with quiet-hours respected automatically.
  • Branch logic: "if no reply in 3 days, ring them" or "if booked, stop the flow".
  • Pre-built templates: Service-due winback, MOT chase, No-show recovery, Lapsed-customer winback. Use as-is or edit.
  • Approve the message style once. Otto runs the rest.
Concrete example

A 3-site dealer group built a "MOT chase" journey: WhatsApp at 28 days, wait 3 days, AI voice call, wait 2 days, SMS. 142 customers in the flow each week. 38% booked the same day they got the WhatsApp. The rest came in over the next two weeks via voice or SMS.

app.otto.ai/journeys/mot-chase
TEMPLATE
MOT chase · 4 weeks before due
✶ LIVE
T
Trigger · MOT due in 28 days
Pulled from DMS each morning
↓
W
WhatsApp · friendly nudge
"Want me to find a slot?"
↓
·
Wait · 3 days
If no reply, continue
↓
V
AI voice call
Books mid-call if they pick up
↓
·
Wait · 2 days
If still not booked
↓
S
SMS · last gentle nudge
With a one-tap booking link

Pick the channel that hurts most.

Most workshops start with after-hours voice or the MOT chase. By month two they've switched on the rest. Same Otto, same diary, same customer record.

Book a 20-min demo How we go live →