Works with what you already run.
The ticket arrives ready for whatever system your dispatcher already has open.
AVA sits on the phone line, not inside your software.
Nothing is installed. Nothing is replaced. Nothing is migrated. There is no plugin to add, no export to run, no records to move, and no login to hand over. AVA answers the phone in front of your operation and writes up what the caller said.
That is why the software question mostly answers itself. Your dispatch system never meets AVA. Your dispatcher does — the ticket comes in, they read it, and they confirm the trip in the same screen they had open yesterday. What sits in front of it all is the limo answering service itself.
Here is how that reads on the systems operators actually run. The detailed map — every platform, one row each, with the real status of each connection — is the integration status table. This page is the plain-English version; that one is the list.
Limo Anywhere
Keep it. Your dispatcher opens the ticket, enters the trip the way they always have, and confirms it. Your rates, your rules, your reservation flow — untouched.
FASTTRAK
Same story. The ticket has the trip details in plain order, so your dispatcher is reading them off, not calling the passenger back for basics.
Santa Cruz / GroundWidgets
There is nothing to connect and nothing to configure on your side. The ticket is plain, complete, and readable by whoever is on dispatch that shift.
Ground Alliance
Affiliate and farm-out calls are still your team's decision. The ticket just puts the full trip in front of them early enough to make that call before the window closes.
iCabbi
Nothing changes inside the platform. What changes is that the 2 AM airport call gets answered and written down instead of ringing out to nobody.
A shared inbox
Plenty of operators run the phone with an inbox and a notepad. That counts as a system. The ticket reads the same, and your dispatcher confirms the trip the same.
Where the ticket lands, and who touches it next.
The same three facts for every system operators actually run. Ticket delivery is included in every setup and its route is scoped on the setup call; direct write-back is a separate per-account step on top of it. The detailed map is the integration status table, which carries every platform and where each one stands.
| Platform | How the ticket arrives | Dispatcher action |
|---|---|---|
| Limo Anywhere | As a written trip ticket, delivered to the inbox or channel your team already watches. | AVA delivers a completed trip ticket that a dispatcher confirms inside Limo Anywhere. |
| FASTTRAK | The same written ticket, in the same place. Nothing is installed on the FASTTRAK side. | AVA delivers a completed trip ticket that a dispatcher confirms inside FASTTRAK. |
| Santa Cruz | The same written ticket. No account is shared and no records are moved. | AVA delivers a completed trip ticket that a dispatcher confirms inside Santa Cruz. |
| A shared inbox | Straight into the inbox, addressed and subject-lined the way you agree at setup. | AVA delivers a completed trip ticket that a dispatcher confirms in your shared inbox. |
Scroll the table sideways to see every column.
One call, written up as a trip your dispatcher can work.
Below is a sample of an early airport run — the call that comes in at 5 AM when the office is dark. The trip details came from what the caller said.
Plain text, every field filled, nothing to log in to just to read it. Whichever screen your dispatcher opens next, the details are already in front of them before they start typing. Call the line and hear one →
AVA captures. Your dispatcher confirms.
Other people in this business blur this part. Here it is straight. AVA answers the phone, takes the whole trip, and writes up a trip ticket. A human on your side reads that ticket and confirms the trip. That is the product today, start to finish.
Until direct write-back has been configured and verified for your account, AVA does not write into your dispatch software at all — and plenty of operators leave it that way on purpose. It never texts or emails the passenger. It does not assign a driver, move a car, or send work out to an affiliate. It does not confirm anything to anybody. All of that stays with your dispatcher, exactly where it sits now.
Who reads the ticket, and how it gets to them, is set on the setup call. That depends on how your shop runs, not on which software you own. How setup works covers the rest of it.
Bring your own trip. Then read the ticket.
Dial the line and give AVA an airport run the way a customer would. Then look at what comes back. If your dispatcher could work from that ticket, the software question is settled.
