Qarhami is now technically integrated with American Business Insurance Services (ABI), one of America's largest commercial transportation insurance agencies. Turn sharing on for a vehicle and its Qarhami telematics reaches ABI — so rental activity can be verified faster, and a claim is supported by what the car actually did.
Live fleet view
There is no separate insurance workflow to learn. It is the vehicle record every operator already edits, with one extra checkbox at the bottom of the form. Here is the exact path — rebuilt live on this page, and captured on a real phone.
Ver. 5.5.2A tracker tells you where a car is. A rental operating system knows which trip it belonged to, who had access, what happened on the way and when it was last serviced. That is the difference between a location and a record — and a record is the thing an insurer can actually use.
Qarhami Fleet OS
ABI
American Business Insurance
Shared vehicle record
Sharing with ABI is a checkbox on the vehicle record — Shared with ABI Insurance — saved with the rest of that vehicle's details. Turn it on for the cars it applies to. Leave it off for the ones it doesn't. Nothing is fleet-wide and nothing is automatic.
Trips in Qarhami carry start and end times, route, distance and the events along the way. When ABI needs to confirm whether a vehicle was on rental at a given moment, that answer already exists — it doesn't have to be reconstructed from messages and memory.
Most operators lose arguments they were right about, because the evidence was a screenshot and a timeline they wrote from memory. A connected vehicle brings dated, system-generated context to the claim instead.
Qarhami provides the data-sharing control. Eligibility, underwriting, coverage terms, claim outcomes and any commercial effect on a policy are determined by ABI and by the policy itself — not by Qarhami.
Operators rarely lose money because they were wrong. They lose it because they could not show they were right, quickly, in the format the other side needed. Here is what a connected vehicle brings to each of those conversations.
Visible to ABI only while sharing is enabled on this vehicle.
The car comes back. Two days later a panel is damaged and nobody agrees about when it happened. Your version of events is a photo with no timestamp and a memory of what the car looked like on Tuesday.
Coverage often turns on whether a car was on rental at a given moment. Reconstructing that from booking screenshots and message threads takes days, and every day is a day the claim sits still.
A vehicle crosses a boundary it was not supposed to cross, hours before anyone would have noticed by looking. By morning the trip has a different shape than the booking described.
After an incident, the question of whether a vehicle was maintained stops being an operations question and becomes a liability question. A shoebox of receipts is not an answer.
Scenarios are illustrative and built from Fleet OS capabilities that exist today. They describe what a record can show; they are not a statement about how any particular claim will be assessed or settled. Event availability varies by device, vehicle, model year, installation, plan, permissions and connectivity.
American Business Insurance Services has been writing commercial transportation cover since 1984. They work across all fifty states with fleet owners, taxi and limousine operators, NEMT providers, TNC drivers, carshare fleets and Turo hosts — the operators whose risk does not fit a personal auto policy.
Their position has been that connected vehicles make for better insurance: clearer visibility, faster claims handling and safer vehicles. Qarhami is now part of how that works for rental fleet operators.
ABI's on-demand commercial transportation platform, built to be customised and scaled around how a fleet actually operates.
ABI's on-rental cover for carshare vehicles and fleets — the period when someone else is driving your car.
Figures as published by American Business Insurance Services. Qarhami is not an insurance agency, broker or carrier and does not provide insurance advice.
New vehicles are created with ABI sharing off. It becomes active only when you tick the box on that vehicle and save. There is no account-wide switch that enrols your fleet behind you.
The setting lives on the vehicle record, alongside its plate, VIN and device serial. Some of your cars can share and others can sit outside it entirely — that is a normal, supported state.
Open the vehicle, untick the box, save. The same three taps that switched it on switch it off, and you do not need to contact anyone to do it.
On what is shared. The exact data set exchanged is defined by ABI's programme requirements and by the agreement between you and ABI. Qarhami's role is to hold the vehicle's operating record and to pass it on for the vehicles you have enabled — not to decide what your insurer does with it.
Turo hosts and private rental operators across North America run their vehicles on Qarhami — and from today, the ones who choose to can put that record to work with ABI.
Open any photo to see the feature in focus
Send the guest a Shared Access link for one vehicle, set to the start and end of their booking. No account to create, no keys to hand over, no meeting at the curb.
In the appSidebar → Shared Access
Assign a return geofence to the vehicle and set Auto Lock After Entry, in minutes. The lock step at the end of a return stops depending on someone remembering to check. On supported vehicles.
In the appSidebar → Geofences → Edit
Filter the fleet by Driving, On Trip and Off Trip from the dashboard, so the first look of the day tells you which cars are working and which ones need you.
In the appDashboard → status filters
Tamper Alert tells you when device power is disconnected, on the channel you choose. Treat it as a reason to look closer — check the last ping, the location and the trip before drawing conclusions.
In the appVehicles → View Vehicle → Notification Settings
Turn on Geofence Entry and Exit alerts for each vehicle and pick the channel. Arrivals and departures at the lot, the airport or the service center reach you as they happen.
In the appVehicles → View Vehicle → Notification Settings
Report an issue when you spot it, log the service when it is done, and keep the history on the vehicle it belongs to — date, mileage, cost, notes and the invoice.
In the appDashboard → vehicle card → Maintenance
Invite a co-host by email and choose which controls they can use — lock and unlock, horn — on the vehicles you select. The team keeps moving while you are in transit.
In the appSidebar → Co Hosting
Tracking rolls each vehicle's week into trips, distance and drive time, with every trip listed by day. When a question comes up, you are reading a record rather than rebuilding one.
In the appSidebar → Tracking
Battery voltage and odometer, read on the vehicle's own record. Low voltage is far easier to deal with before the next guest is standing beside the car.
In the appVehicles → View Vehicle
Lock, unlock and horn sit on every vehicle card on the dashboard. Supported controls, on supported vehicles — one tap instead of one drive.
In the appDashboard → vehicle card
Share a time-bound link for one car and the guest gets that car's supported controls — not your account, not the rest of the fleet. Copy it, send it, get back to your workout.
In the appSidebar → Shared Access
A return geofence with Auto Lock After Entry gives the handover a grace period, in minutes, before the configured lock applies. You do not have to be there to close out the return. On supported vehicles.
In the appSidebar → Geofences → Edit
A dot on a map says where. Driving, On Trip and Off Trip say what it means — whether a car is earning, parked between bookings, or on the move with no trip attached.
In the appDashboard → status filters
Choose Battery Low — and whichever other events matter — for each vehicle, then choose the channel. A weak battery flagged on Tuesday is a car that still starts on Friday.
In the appVehicles → View Vehicle → Notification Settings
Home lot, airport, service center. Draw the zones once, assign the vehicles, and configure entry and exit notifications on each car.
In the appSidebar → Geofences
The issue you report today becomes the service you log tomorrow, and both stay on the vehicle. When someone asks when the brakes were last done, the answer is already written down.
In the appDashboard → vehicle card → Maintenance
Co-hosts sign in with their own login and use only the vehicles and controls you have granted. Handovers stop living in a group chat.
In the appSidebar → Co Hosting
Trips, distance and drive time for the week, with each trip ready to open by day — the driving history behind the decisions you make next.
In the appSidebar → Tracking
Open the vehicle and the readings are there — battery voltage and odometer — before you commit the car to its next guest.
In the appVehicles → View Vehicle
The supported controls live on the vehicle card, so the small jobs — a lock check, a guest who cannot find the car — take a tap from wherever you are sitting.
In the appDashboard → vehicle card
It is in the app right now. Open a vehicle, tap Edit, tick Shared with ABI Insurance, save. Repeat for each vehicle you want included.
Qarhami gives the vehicle its record. ABI writes the cover. If you need either side of that, start here.
Two things today: an opt-in, per-vehicle channel that shares that vehicle's Qarhami telematics with ABI, and the faster rental verification and better-evidenced claims that follow from it.
It does not, by itself, change your premium. Pricing, eligibility and coverage terms are decided by ABI and by your policy. If ABI applies any commercial benefit to connected vehicles, that comes from them and is confirmed by them, not by this page.
No. The setting lives on each vehicle record and is off unless you switch it on.
Sharing two cars and leaving seven off is a normal state. This matters for mixed fleets — partner-owned vehicles, cars insured elsewhere, or a vehicle you are about to sell.
Yes, from the same screen. Open the vehicle, tap Edit, untick Shared with ABI Insurance, save.
Any obligation you have already taken on with ABI under your policy is a matter between you and ABI — switching the Qarhami setting off changes what is shared going forward, not your contract with your insurer.
No. Qarhami is a rental fleet operating system first, and works exactly the same whether or not you share with any insurer.
The Fleet OS also supports data sharing with Tint, on its own separate checkbox. The two are independent of each other.
The sharing control is on the vehicle record, so it applies to a vehicle regardless of which device is fitted.
What varies is the data itself. Track is the hardwired path and OBD is the plug-and-play path, and the signals each one exposes depend on the vehicle, its model year, the installation, your plan, permissions and connectivity.
No. Qarhami is not an insurance agency, broker or carrier, does not sell cover and does not give insurance advice.
Qarhami provides the operating system and the data-sharing control. ABI provides the insurance.
Vehicles → View Vehicle → Vehicle Details → Edit. Scroll to the bottom of the form, under the Turo link.
You will see two checkboxes: Shared with Tint Insurance and Shared with ABI Insurance. Tick the ABI one and press Save Edits. The walkthrough on this page shows the whole path.
