For UK taxi & private hire firms
Turn agreed email booking requests into bookings in Autocab, with less copying between your inbox and dispatch system. EBA manages the workflow; your team handles exceptions and stays responsible for the journey.
Free 30-minute consultation · Compatibility checked first
Agreed inputs. Clear boundaries. Human oversight.
TAXI / EBA01 / The work behind the journey
For taxi and private hire offices receiving repeat booking requests by email. The starting point is the formats you actually receive and the booking details your team needs, rather than a promise to process every possible message.
The workflow reads agreed email formats, extracts the required information and uses the agreed rules to create bookings in Autocab. Pickup, destination, date, time and account or passenger references are examples of fields we review with you before setup.
Missing details, unclear addresses and requests outside the agreed scope need human handling. We define those boundaries together. Booking creation does not complete journeys: your team still checks exceptions, dispatches vehicles and delivers the passenger service.
02 / Illustrative walkthrough
Imagine a repeat account sending its usual booking request with a journey date, pickup time, pickup location, destination and account reference. Here is the agreed workflow in plain English.
A text example, not a live customer record or a product screenshot. The exact fields, rules and output are agreed for your setup.
Receive an agreed email formatThe request arrives through the agreed email route. We establish which senders, message formats and booking types belong in the workflow during the compatibility review.
Extract the booking detailsThe relevant fields are prepared for the agreed Autocab booking process. The mapping is checked with your team so a date, address or account reference has the meaning your office expects.
Create the booking or hand back the exceptionA request that meets the agreed requirements can become an Autocab booking. If the request is missing a pickup time or contains an unclear destination, it needs human review instead of being treated as a complete, valid booking.
Your office takes the next stepThe resulting booking is available for your normal operating process. The automation does not assign responsibility for delivering a journey, and it does not mark a journey as completed.
03 / Before anything goes live
EBA provides a centrally hosted, managed service. You do not need to leave a PC running to host the automation. We review compatibility, access permissions and operational requirements with you before agreeing the setup.
Review your Autocab setup and accessWe check your specific Autocab setup, the supported connection route and the permissions needed to create bookings. We do not assume every Autocab setup can be connected, and access is agreed before activation.
Agree the inbox, formats and booking fieldsWe review the email route, representative message formats, required fields and account mapping. Attachments, amendments, cancellations and unusual requests need an explicit scope decision; they are not automatically included.
Decide who handles exceptionsYour team identifies who will check incomplete or out-of-scope requests and how those cases fit your existing office process. We agree the operational handover rather than guessing missing booking information.
Test the agreed workflow, then support itWe agree the expected output and the cases for human review before activation. If something breaks because of our own fault, we fix it free of charge. Scope changes and any additional cost are agreed separately.
Try the agreed automation for its first live week. If it isn’t right for you and you opt out within that week, we switch it off, waive the setup fee and you pay nothing. The trial start, end and opt-out process are agreed before activation.
EBA is an independent automation service. Autocab and Xero are third-party products; references to them do not imply an official partnership or endorsement.
Before we begin
Tell us about your current process.
Book a compatibility conversation
Compatibility is checked first. We review your Autocab setup, available access, email formats and the booking workflow you need. A reference to Autocab does not mean every version or configuration is supported. We only agree a setup once the connection route and scope are clear.
The agreed email formats and booking types are defined during setup. We check the fields and examples with you. We do not promise to understand any free-form email, attachment or message thread; anything beyond the agreed formats needs review.
Those requests go back for human review according to the agreed process. An unclear pickup location or missing journey time should not be treated as a complete booking. Your team remains responsible for resolving the request.
No. This package creates bookings from the agreed email inputs. Dispatching vehicles, delivering journeys and handling operational decisions remain with your taxi office. Creating a booking is not evidence that a journey has happened.
We review those requirements separately before agreeing the scope. A change or cancellation needs to be matched to the right booking and checked against your operating rules. Do not assume it is covered by the standard new-booking workflow.
No. EBA provides a centrally hosted, managed service. We agree the necessary email and Autocab access permissions, connection requirements and human handover with you; your team does not need to host the automation on a PC.
The rest of your taxi office
Once the journey has happened, the accounts team has a different job to do. EBA’s separate Xero workflow creates draft invoices with journey PDFs for review. Compare the individual packages or discuss both together.
A practical next step
30 minutes. Your tools. A clear starting point.