Service types and vehicle matching

Ambulatory, wheelchair, bariatric and stretcher — and how each one restricts the fleet.

Written for
Dispatchers
Reading time
1 min
Last reviewed
July 24, 2026

Service type is the single most consequential field on a trip. It decides which vehicles can run it, what the trip costs to serve, and what the payer is billed. It is a hard constraint in scheduling, not a preference.

Service typeRiderRequires
AmbulatoryWalks unaided or with a caneAny active vehicle
WheelchairTravels in their own wheelchairA vehicle with a lift or ramp and securement points
BariatricRequires higher weight capacity equipmentA vehicle rated for it, and often a second attendant
StretcherTravels lying downA stretcher-equipped vehicle and trained staff

Keeping the fleet's capabilities honest

Matching is only as good as the capability flags on each vehicle. A wheelchair-capable van that was never flagged as one is invisible to the optimizer for wheelchair trips, and the symptom is unassigned trips rather than an error message.

Related

Still stuck?

Technical documentation

API references, data model, webhook payloads and integration guides — the detail behind the workflows described here. Available to signed-in Naveera customers.

Open documentation

Ask your team

Support requests are raised from inside Naveera Console, where your organization and your role are already known — which means the answer can be about your configuration rather than the general case.

Settings → Support, or ask your organization’s administrator