Every ride booked, even the calls you cannot take

The call gets answered while you are driving

A car service loses work in one specific way: the phone rings while the driver is on a job and cannot safely take it, and the caller books the next company on the list. Airport runs and event work are booked on the phone, often at odd hours, and the business that picks up gets the job.

Calls are answered in a natural voice, on the first ring, at any hour, and the conversation gets as far as a confirmed booking before the caller hangs up. Critical details are read back for confirmation before anything is committed, which matters when a wrong pickup time means a missed flight. See how phone answering works.

• Every call answered, including overnight and mid job
• A read-back gate confirms the critical details before a booking is committed
• Speech is sanitized, so no raw links or formatting are ever read to a caller
• The platform never places outbound calls: customers are answered, not chased

The questions that come before a booking, answered from your own information

Before anybody books a car they ask the same handful of things. What vehicles do you have. Can you take six people and luggage. How far in advance do you need. What does an airport run involve. Those answers live in your head and in a document nobody reads.

They are answered from your own business information rather than from a script, and where there is a choice to make, the options render as tappable chips: vehicle choices, time slots, confirmations. The customer taps instead of typing, which is the difference between a booking and an abandoned thread on a phone screen in a car park.

• Answers from your own information, including vehicle and service details
• Tappable options for vehicle choices, slot lists, and confirmations
• The current date, time, and day in your timezone checked on every request
• Multiple languages on every channel

Deposits, because a cancelled car is a wasted hour

An empty run costs fuel, time, and the job you turned down for it. For high-value trips, event work, and long bookings from a first-time customer, a deposit or a payment hold changes the odds materially.

Deposits run through Stripe with a secure payment link sent in the same conversation and automatic reminders if it is unpaid. Every booking is also scored for no-show risk against weighted factors, and a paid deposit lowers that score, so reminders concentrate where they are actually needed. See booking, risk scoring, and deposits.

• Deposits and payment holds via Stripe, with secure payment links
• Every booking scored for no-show risk and sorted into tiers
• Reminder frequency matched to the risk, with quiet hours respected
• Replies to reminders classified and acted on automatically

The rider is known before they say who they are

Repeat riders are the business. The regular airport run, the corporate account, the family that books the same car for every event. Every call, message, and booking becomes one customer record with full history, preferences, and lifetime value, merged across phone and email so the same rider is not three separate entries.

That is why a customer who messaged on WhatsApp last month is recognised when they call this month, with their usual vehicle and their past trips already attached. See the unified customer record.

• One record per rider, merged across phone, email, and channel
• Full trip history, preferences, and lifetime value on the record
• The same record behind the phone line, the chat, and the website

The riders who drift, and the enquiry that never booked

Corporate and repeat riders leave quietly. Win-backs here trigger on real inactivity relative to how often that rider normally books, so a monthly account that goes silent is noticed and an occasional customer is not pestered.

The enquiry that never converted gets one follow-up, once, grounded in what they actually asked about. And after a completed trip, a review request goes out while the experience is fresh, with every review that arrives getting a reply drafted for you to approve. See retention and review management.

• Win-backs on real inactivity, judged against their own booking pattern
• One follow-up for the quote enquiry that never turned into a trip
• Review requests after a completed trip, never filtered by predicted rating
• An immediate alert the moment an unhappy review lands

Questions owners ask