A driver calls a four-bay independent shop at 7:15 on a Monday morning. He says the van is making a noise and he needs it looked at today. The service writer, who is standing at the counter with two retail customers waiting and a coffee he has not touched, books him in as a walk-in, takes a first name and a cell number, and writes "white van, noise" on the ticket.
The van shows up. It has a company logo on the door and a unit number stenciled above the rear wheel. It belongs to a plumbing contractor with eleven trucks on an account the shop has serviced for three years. The driver has no authority to approve anything over a tire rotation. The shop diagnoses a failing wheel bearing, calls the number on the ticket, and gets the driver, who says "yeah, go ahead." Nobody at the contractor's office knows the van is at the shop. No purchase order exists. The work gets done, the invoice goes out, and it sits unpaid for six weeks while the contractor's office manager insists she never authorized it.
That whole mess was created in the first forty seconds of the phone call, when nobody asked whether the caller was a retail customer or a fleet account.
Sort fleet from retail in the first thirty seconds
Retail and fleet callers sound identical at the start. Both say a vehicle has a problem and they need it in. The difference is everything that comes after: who pays, who approves, how the vehicle is identified, and what the shop is allowed to do before someone signs off.
The sorting question is simple and it should be asked on every inbound call before anything else gets written down. Is this vehicle for a company account, or is it a personal vehicle? Most fleet callers answer immediately and are relieved to be asked, because they are used to explaining it three times.
A few tells show up even before the question. Callers who lead with a unit number instead of a year and model are fleet. So are callers who ask whether the shop bills the account, callers who mention a fleet card program, and callers who say "we" instead of "I" when describing the vehicle.
The reason to sort early is that the two intakes diverge hard. A retail intake collects a name, a phone number, a vehicle, and a symptom. A fleet intake collects an account, a unit, an authorizer, a billing path, and an approval limit, and the vehicle description is almost the least important part of it.
The fields a fleet intake has to capture
A fleet service call that gets written up like a retail ticket becomes a collections problem later. The information below is what keeps an invoice from stalling, and every field on this list exists because some shop somewhere ate the cost of skipping it.
- Company name and account number. The legal billing entity, not the name on the door of the van. Contractors frequently operate under a DBA that does not match the entity on the account.
- Unit number and VIN. Fleets track vehicles by unit number, and their maintenance records, their approval systems, and their invoices are all keyed to it. A shop that writes only "2019 Transit" will get an invoice bounced back asking which one. Capture the last eight of the VIN alongside it.
- Caller name and role. Driver, dispatcher, fleet manager, or office manager. The role determines whether this person can approve work at all.
- The authorizer, if it is not the caller. Name, direct number, and email of whoever actually approves repairs. This is the single most valuable field on the ticket, and the one most often left blank.
- Odometer. Fleets run mileage-based maintenance schedules and often will not approve a service that falls outside the interval. It also determines warranty coverage on a lot of drivetrain work.
- Billing method. Direct bill to the account, a fleet card, or a third-party fleet management program. Each one routes differently.
- PO number, or confirmation that one is coming. Many fleets will not pay an invoice without a PO referenced on it, and getting one after the fact takes days.
- Approval threshold. The dollar figure above which the shop must stop and call for authorization. Some accounts set it at $250, some at $500, some require a PO for every dollar.
- Vehicle availability window. When the shop can have the vehicle and when the fleet needs it back. This is a hard constraint, not a preference.
- Symptom, with driver detail. What the driver actually experiences, since the driver is usually the only person who has driven the vehicle and often will not be the one the shop calls back.
None of this is unfamiliar to a service writer who has run fleet work for a few years. The problem is that it takes four or five minutes to collect properly, and Monday morning at 7:15 does not have four or five minutes in it.
Authority: the driver is not the customer
The most expensive misunderstanding in fleet service is treating the person who dropped off the vehicle as the person who can approve the work on it.
Driver authority varies by fleet and is often surprisingly narrow. Some fleets let drivers approve nothing at all. Some allow routine items like oil changes and wipers up to a small cap. Some allow a driver to authorize a diagnosis but not a repair. A shop that assumes verbal approval from a driver is binding will eventually find out it is not, usually after the parts are installed.
The practical rule is to establish, at intake, who holds authority for this specific vehicle on this specific visit, and to get that person's direct contact information rather than a main office line. When the diagnosis comes back at 11 a.m. and the shop needs an answer to keep the bay moving, a main line that rolls to voicemail costs the rest of the day.
Capture the approval path in writing on the ticket, in plain language: "Diagnose only. Call Marisa at the office number before any repair. PO required over $300." Then the technician, the service writer, and whoever covers the counter at lunch are all working from the same instruction.
Billing paths: per-vehicle, per-account, and the card in between
Fleet billing is not one thing, and asking a general question like "how do you want to pay" produces a useless answer. The shop needs to know which of three paths this repair travels.
Direct account billing. The shop invoices the company, usually on net-30 terms, and the fleet's accounts payable process takes over. This is the path that lives or dies on the PO number. If the fleet's AP system requires a PO and the invoice arrives without one, it sits in an exception queue until somebody notices.
Fleet card programs. Large national fleet management and leasing companies, including names like Element and Enterprise Fleet Management, run maintenance programs where the shop calls in for authorization and the program pays directly. These programs generally have their own authorization steps, their own labor time expectations, and their own approval numbers that have to be captured before work begins. The specifics vary by program and by the individual client's plan, so the shop should confirm the current requirements with the program rather than assume, and should never start work on a program vehicle without an authorization number in hand.
Per-vehicle billing inside an account relationship. Some fleets, particularly owner-operators and small contractors, want each vehicle invoiced separately even though they hold one account, because they cost-track by unit. Others want one consolidated monthly statement. Getting this wrong does not lose the money, but it generates a rebilling request and a delay.
The intake question that separates these cleanly is: does this repair get billed to the account directly, or does it go through a fleet card or maintenance program? One sentence, and it routes the entire back end of the job.
Hear it handled live. Answara's own AI receptionist answers our main line. Call (857) ANSWARA and ask it whatever a customer would ask you, or see plans and get set up.
Turnaround is the number the fleet actually cares about
A retail customer with a car in the shop is inconvenienced. A fleet with a truck in the shop is losing a route, a crew, or a day of billable work. That difference shapes every conversation about timing.
Fleet callers will accept bad news about turnaround far better than they accept uncertainty. A dispatcher who hears "we can diagnose today, and if it is the bearing we can have it back tomorrow afternoon" can plan around it. A dispatcher who hears "we'll see how it goes" cannot, and will start calling other shops.
So the intake should capture the fleet's constraint, not just the shop's estimate. Ask when the vehicle is needed back and whether there is a hard deadline. Ask whether the fleet has a spare unit to cover, because a fleet with no spare is in a different situation than one with three vans idle in the yard. Ask whether the vehicle can stay overnight.
Then commit to a specific callback time with the diagnosis. Not "later today." A time. The service writer who says "I will call you by 11" and calls at 11, even to say the part is still being sourced, keeps the account.
Routing a vehicle that is blocked on approval
There is a specific state that fleet work falls into and retail work rarely does: the vehicle is diagnosed, the shop knows what it needs, and nothing can happen because nobody has approved it. This is not a stalled job. It is a job in a defined state, and it needs a defined handling.
The first thing is to get the vehicle out of the bay. A blocked unit sitting on a lift while the shop waits for an office manager to return from lunch is a bay not producing. Move it to the lot, note where it is, and put the bay back to work.
The second is to make the approval request easy to say yes to. The person on the other end is often approving a repair on a vehicle they have never seen, for a driver they may not have spoken to, against a budget they are accountable for. Send the estimate with the unit number, the odometer, the symptom the driver reported, the diagnosis, the line items, and the total. Reference the PO if one exists. Fleet managers approve fast when they have a clean document and slowly when they have a phone call and a number.
The third is to set a follow-up rhythm and hold it. One call, one email with the estimate, then a defined follow-up the next morning if there is no answer. Vehicles that go quiet in a shop lot for a week become arguments about storage and liability.
The last piece is a written policy for what happens when approval never comes: how long the shop holds the vehicle, whether diagnostic time gets billed on a declined repair, and who tells the driver. Shops that write that down before they need it have a much easier conversation than the ones that improvise it.
Where an AI receptionist fits
Everything above is a phone problem before it is a shop-floor problem. The account number, the unit number, the authorizer, the PO, the approval threshold, the turnaround constraint: all of it exists on the call, and all of it gets lost when the phone rings during a bay change or after the counter closes at 5:30. Answara answers inbound calls, runs the same fleet intake every time, captures the caller and vehicle details, and books the appointment, so the ticket that reaches the service writer already has the fields on it instead of a first name and "white van, noise." Shops that want to see how it handles automotive calls can look at answara.ai/auto.
FAQ
Should we require a PO on every fleet repair? That depends on the account, and it is worth confirming per account rather than setting one shop-wide rule. Many fleets require a PO above a threshold and allow small routine items without one. The thing to avoid is guessing, because an invoice missing a required PO usually stalls in the fleet's accounts payable queue rather than getting rejected outright, which means nobody tells you it is stuck.
What do we do when a driver insists he can approve the work? Write down exactly what he said and who he is, then verify with the account contact before starting. Drivers are not being dishonest when they say this. They usually believe it, and sometimes they are right. But the shop carries the risk if they are wrong, so the verification call is cheap insurance.
How do we handle a fleet card program vehicle we have never serviced before? Get the program name and the account contact at intake, then call the program for authorization before any work, including diagnosis in some cases. Capture the authorization number on the ticket. Requirements differ between programs and between individual client plans, so confirm the current process directly with the program rather than applying what another program required.