How setup works.
No mystery and no long sales process. Here is every step between the setup call and AVA answering your line — and what we need from you to get there.
Five steps, setup call to live line.
Setup is done for you and custom. Our team ran a chauffeured transportation company for 17 years — the same phones, the same board, the same nights you work. Wisconsin-built, serving operators nationwide.
Typically one to two weeks, once your rules are written down. The order below does not change.
A twenty-minute setup call
What you run, how many cars, and what your phone does at 2 AM right now. No slide deck. By the end of twenty minutes we both know whether this fits your operation.
Your rules, written down
Rate rules, service area, vehicle classes, and how a trip reaches your dispatcher today. Most of it already lives in your head or on a rate sheet. This step just gets it on paper.
The build
AVA is written around those rules — the greeting, the questions it asks a caller, and every field on the trip ticket. Nothing generic. It asks for what your dispatcher needs to run the trip.
Test calls you listen to
You dial the line and give it a real trip. An airport run, an hourly charter, a Saturday night pickup. You hear every word. Wording gets changed until it sounds like your office, not ours.
Live on your line
You forward your line to AVA. Start with after hours only if you want, then move to all day once you have heard it work. Every call comes back as a trip ticket, and your dispatcher confirms every one.
One thing does not change at any step: AVA captures, your dispatcher confirms. Direct write-back into your dispatch software is a per-account option, configured and tested during setup and switched on only after it verifies — until then the ticket goes to your dispatcher and a person enters it. AVA does not text or email the passenger. It does not assign a driver or send work out to an affiliate. All of that stays with your team, exactly where it sits now — which is why it works with your software without touching it.
What we need from you.
Six things. You already have all six — most of them are in your head, and step 02 is simply getting them written down. None of this needs a project manager or an IT department.
- Your rate rules or rate sheet. So AVA asks for the details your rate sheet needs, instead of a generic set of questions. Your dispatcher still prices the trip.
- Your service area. So the ticket shows whether a pickup sits inside your area. Farm-out calls stay your team's decision.
- Your vehicle classes. So the ticket names the car the way your run sheet names it — sedan, SUV, sprinter, coach.
- How a trip reaches your dispatcher today. So the ticket fits the process you already run, instead of you bending around it.
- Your after-hours arrangement. Who covers the phone tonight, and what should happen at 2 AM when nobody does.
- A number to forward. The line your callers already dial. You keep it, and you keep control of the forward.
There is no price list, and here is the reason.
Every build is custom to the operation — your rate rules, your service area, your vehicle classes, the way your dispatcher works. A small operation running weddings is not the same build as a fleet running airport contracts all week, so the two do not carry the same number.
That is the honest reason this page has no figures on it. There is no package to pick from, so there is nothing to publish. The build is scoped on the setup call, out loud, while you are on the phone. What gets built is the limo answering service that answers your line.
Hear the line first. Then take the twenty minutes.
The setup call goes better when you have already been the caller. Dial the number and give AVA a trip — an airport run, an hourly charter, whatever you get most. Nothing to install, no menu to sit through.
