The Software Behind Your Cab: How Cabica Runs A1 Cabs

Most people never think about the software behind a taxi, and that is rather the point — the best possible outcome for a dispatch system is that the passenger notices nothing except a car arriving. But since a fair amount of what this website does is only possible because of it, here is a look at the machinery.

A1 Cabs runs on Cabica, a dispatch platform built for operators like us: local companies with real cars, real drivers and a dispatch office, rather than a global app with no phone number.

What happens when you press the button

From the outside, booking on this site is two addresses and a name. Underneath, a sequence runs in about a second:

1. 1Address resolution. As you type, each suggestion is matched to a real place with coordinates — a pin, not a string of text. That is why the driver ends up at the right one of three doors.
2. 2Pricing. Those two sets of coordinates are priced against the company's live tariff: metered rates for city work, flat rates for airport and out-of-town runs, plus any demand pricing in force at that moment.
3. 3Job creation. The booking is written into the dispatch queue with everything the office needs — where, when, how many passengers, whether it needs a van or a wheelchair-accessible vehicle, and the notes you typed.
4. 4Assignment. Dispatch, or the platform's own allocation, matches the job to a car that can actually do it and is near enough for that to be sensible.
5. 5A reference back to you. You get a booking reference, which is the thread tying your phone to that specific job for the rest of its life.

That whole chain is why the price on this site is the operator's real price rather than an estimate. The website has no price list of its own to fall out of date — it asks the same system the dispatchers use.

Why the address suggestions matter more than they look

The unglamorous truth of taxi work is that most late arrivals are address problems, not driving problems. A passenger types "81 Ave" and means one of several places. A driver arrives at a building with entrances on two streets. An acreage has a name and no number.

Resolving your address to coordinates at the moment you book removes most of that. The driver's screen gets a point on a map, not a guess. It is also why the booking form nudges you to pick your pickup from the suggestion list rather than typing it freehand and pressing on.

Capabilities: matching the job to the right car

Not every car can do every job. A wheelchair-accessible van, a vehicle with room for seven, a car with a child seat fitted — these are what the platform calls capabilities, and they are attached to specific vehicles.

When you tick one of those boxes on the booking form, you are not sending a polite request to be read later. You are filtering the job so only a car that can genuinely do it gets offered it. Which is precisely what you would want if you were standing outside with a wheelchair.

Tracking, and what the reference is for

Every booking gets a reference. Put it into the tracking page and you see where the job actually is: received, driver assigned, driver arrived, on the trip, completed. Each of those is a real timestamp written as it happens, not a progress bar animating on a timer.

The reference is also the fastest route to help. "I left my phone in the cab" is a hard problem. "I left my phone in the cab, reference GP-4K7Q2" is a thirty-second problem, because the office can go straight to that trip and that driver.

Why a local company runs a platform at all

There is a version of this industry where your only route to a company is an app: no office, no phone number, and no local dispatcher who knows the grid road past the second cattle guard is impassable in March.

We would rather have both. Software doing what software is good at — pricing, matching, timestamps, keeping a record — and people doing what people are good at. When you call 780 518 3503 at 3am, a dispatcher answers, and they are looking at the same system this website talks to.