Integrations · the honest map

Dispatch software AVA works beside.

AVA answers your dispatch line, takes the whole trip, and delivers a complete trip ticket into the workflow your team already runs — a shared inbox on day one. Direct write-back into a dispatch system is configured per account and switched on after setup verification. Your dispatcher stays in command of every trip.

Last updated 7 August 2026

Platform status

Every platform, one honest status.

Five statuses cover the whole list. Included in every setup means it is on from day one. Available after setup verification means the connection is built and tested against your account first. Scoped during setup and review mean exactly that — the work is defined on your setup call, not assumed here.

No row on this page says a connection is verified in production. That sentence gets written the day a real operator's acceptance test passes, and not before.

Dispatch platforms AVA works beside, and the integration status of each
Platform	Integration status
Limo Anywhere	Direct write-back available after setup verification
FASTTRAK	Partner API integration scoped during setup
GNet	Network workflow review
Ground Alliance	Custom integration review
Moovs	Custom integration review
Livery Coach	Custom integration review
Hudson	Custom integration review
Santa Cruz (GroundWidgets)	Custom integration review
Limo Express	Custom integration review
A to Z Dispatch	Custom integration review
Shared inbox or email	Included in every setup

AI Chauffeur is an independent company. It is not affiliated with or endorsed by any of the platforms named on this page.

In detail

Two platforms with the whole answer written out.

These two get a page each — the connection ladder, the field map, and a worked trip ticket. The rest are a row in the table above until there is something real to write about them.

The connection ladder

Delivery on day one. Integration after that.

No operator waits on an integration to start capturing calls. The ticket has somewhere to land from the first live call, and the connection is built underneath it while the phone is already being answered.

Rung 1 · Day one

Shared inbox delivery. The completed trip ticket arrives in the inbox or channel your team already watches, addressed and subject-lined the way you agree at setup. Nothing is connected to your dispatch software yet, and nothing needs to be for a trip to get captured and confirmed.

Rung 2 · During setup

The connection is configured and tested. Service types, vehicle classes, rate rules, required fields, statuses and approval workflow get matched to your account. This is the work the setup call scopes, and it is done against your operation rather than against a generic template.

Rung 3 · After verification

Direct write-back is activated — where the platform supports it and your account has passed setup verification. Your dispatcher still confirms every trip inside the approval workflow you already run. Write-back changes where the record is created, not who says yes to it.

Any rung

You can stop at rung one and stay there. Plenty of operators run the whole business off a shared inbox and a dispatcher who reads it, and the product works exactly the same way for them.

What lands, whatever the platform

One shape of ticket, eleven ways to receive it.

The ticket does not change per platform. Below is an as-directed corporate booking — the call that comes in mid-afternoon while dispatch is already on two other lines.

Sample trip ticket · as-directed Captured

Inbound caller

Dana W.

+1 (414) 555-0126 · Inbound

Trip type

As directed · 4 hours

Client meetings, downtown

Pickup → release

Third Ward office → open

Pickup time

1:00 PM

Thursday

Vehicle

Executive SUV

Passengers

3 · 0 bags

Quote range

$420–$480 est.

Illustrative sample

Status

Routed to dispatch

Dispatcher confirms

Sample ticket · the quote range is illustrative only · real ranges come from your own rate rules

Same fields to a shared inbox, same fields to a configured connection. What changes as you climb the ladder is how much re-keying the person on dispatch does — not what they get told. The full field-by-field version lives on the Limo Anywhere page.

Hear it first

Call the line. Then pick your rung.

Dial the number and give AVA a real trip the way a customer would. What comes back is the ticket at the top of this page. Where it lands, and whether it ever gets written straight into your system, is the setup call's job to decide.

Call (414) 775-0019 AVA answers. Hear it yourself.

Book the setup call → Schedules the 20-minute setup call.

FAQ

Questions operators actually ask.

Does AVA connect to my dispatch software?

It can, on supported platforms, once the connection has been configured and tested against your account. Until then — and permanently, if you prefer it that way — AVA delivers a completed trip ticket to the person on dispatch, who enters and confirms the trip in the system you already run. Both are real setups, and the table above says which platforms are at which stage.

What happens on day one, before any integration exists?

The phone gets answered. AVA takes the whole trip and the ticket arrives in the inbox or channel your team already watches, so a call captured on your first live day is a trip your dispatcher can work that same hour. Nothing waits on connection work, which is the point of building the ladder in that order.

My platform is not on the list. Now what?

Shared inbox delivery covers you from day one regardless of what you run, because it depends on nothing at your end. Bring the platform to the setup call and it gets a custom integration review like the rest — that means someone looks at what your account actually supports before anybody promises you anything.

Who confirms the trip once write-back is switched on?

Your dispatcher, exactly as before. Write-back changes where the record gets created; it does not change who approves it. The approval workflow your operation already uses is one of the things configured and tested during setup, and a trip does not skip it because the record arrived automatically.