Commercial auto telematics has moved from pilot projects to default infrastructure. Roughly 80% of top-50 commercial auto insurers now consume telematics data, and 82% of commercial policyholders have some form of adoption, up from 65% in 2023. Yet combined ratios have stayed above 100% in five of the last six years, a paradox Orion Fleet Intelligence calls telematics' “broken promise.” The data exists; the problem is plumbing. This whitepaper lays out how carriers and MGAs in commercial trucking insurance can close that gap by treating fleet telematics data as a first-class input to telematics underwriting, rating, and FNOL — with the Mercury Policy and Claims Administration System as the integration spine.
Commercial auto has been the problem child of U.S. P&C for most of the past decade. Loss severity has climbed faster than rate, nuclear verdicts have reset expectations in trucking litigation, and reinsurance terms have hardened. Telematics was supposed to be the cure. It has not been — at least not yet. Orion Fleet Intelligence documents that 2023 was the fifth time in six years the industry posted a combined ratio above 100%, despite ELD mandates and near-universal device availability.
The paradox resolves when you look at plumbing rather than policy. Underwriters often see a PDF driver-behavior summary at renewal rather than a continuous feed. Claims teams learn about a crash hours later, when the scene is disturbed and memories have hardened. Rating engines rarely ingest telematics into factors that materially move premium. The signal is there; the wiring isn't. This paper is about the wiring.
Adoption tells two stories in parallel. On the supply side, SambaSafety's 2025 Telematics Report finds 80% of top-50 carriers consume telematics, and 68% report improved pricing accuracy. Fleets combining telematics with structured driver training reported a 68% crash reduction. Earlier 2024 SambaSafety benchmarks showed 74% of fleets use the data for driver coaching and 72% saw reductions in crashes and claims, with 25% reporting lower premiums. Central Insurance reports 82% of commercial policyholders now have some adoption, up from 65% in 2023.
On the demand side, the insurance telematics market is projected to grow from USD 2.5 billion in 2023 to USD 12.8 billion by 2032, a 19.8% CAGR. Capital flows into device makers, aggregators, and scoring vendors — but only slowly into carrier core systems. The gap between receiving the data and pricing and adjudicating on it is where the next decade of commercial auto profitability will be decided.
A modern commercial account generates signal from multiple layers: OEM-embedded connected vehicle insurance feeds, aftermarket ELD and dashcam devices, and third-party aggregators that normalize vendor differences. The practical question is not which device is on the truck but which events cross the wire in real time and in what schema.
Fleet telematics data converges on de facto event standards: hard braking, harsh cornering, speeding relative to posted limits, idling, HOS and duty-cycle compliance, geofence entry/exit, and crash detection with g-force thresholds. Aggregators expose these as JSON streams over webhooks or pollable REST endpoints. Mercury consumes them as canonical telematics events keyed to policy, unit, and driver, so the same feed powers rating, underwriting review, and automated FNOL without a separate integration per use case.
| Data Type | Underwriting Value | Claims Value | Integration Method |
|---|---|---|---|
| Hard braking events | Driver score input; usage-based insurance rating factor | Event reconstruction around loss time | Webhook to Mercury event endpoint |
| Harsh cornering | Fleet-level risk trend; renewal adjustment | Contributing factor analysis | Daily batch via aggregator API |
| Speed / posted-limit events | Class-code validation; tiering for commercial trucking insurance | Liability and subrogation evidence | Streaming feed to Mercury |
| HOS / duty-cycle compliance | Regulatory risk flag; account declinature signal | Fatigue-related claim review | ELD provider API |
| Geofencing | Radius-of-operation verification vs. filing | Territory-of-loss confirmation | Policy-linked geofence rules in Mercury |
| Crash detection | Post-bind loss frequency signal | Automated FNOL within seconds | Real-time webhook to Mercury claims intake |
Three telematics underwriting patterns are now operational. First, new-business tiering: a feed covering the last 90 to 180 days of prior-carrier operation produces a driver- and fleet-composite score that slots the account into a rating tier before a human underwriter touches the file. Second, renewal-based usage-based insurance adjustments: instead of waiting for annual loss experience, rating engines consume monthly aggregates and adjust factors within filed bands. SambaSafety 2024 benchmarks tie this to the 25% premium reductions reported by well-performing fleets. Third, mid-term intervention: when scores drift beyond thresholds, Mercury opens a structured underwriter task with the events driving the change — turning fleet data from a passive dashboard into an accountable workflow item.
SambaSafety's 2025 research surfaces three recurring reasons fleets hold back data from their carriers: (1) lack of trust that strong performance will earn lower premium — the rate-reduction promise has been inconsistent; (2) fear of surveillance and liability exposure in litigation; and (3) pricing opacity, with no clear line of sight from specific behaviors to specific credits. Carriers that publish transparent, behavior-linked rating factors and contractual data-use terms close this gap faster than those that do not.
FNOL acceleration is where telematics produces the most immediate, measurable claims impact. A crash-detection event with timestamp, coordinates, speed, delta-V, and vehicle ID lands in Mercury's claims intake within seconds — before the driver calls, before dispatch is notified, and before the scene is disturbed. That single data point unlocks a cascade: automated coverage verification, a photo/video capture workflow pushed to the driver's phone, geofence-based routing to the nearest preferred repair facility, and proactive outreach to the insured.
Downstream effects are material. Fraud signals that rely on timing consistency become automatic. Subrogation potential is captured from the first moment because location, direction, and speed are established by the device rather than by witness memory. Reserve accuracy improves because delta-V thresholds correlate to injury severity. For trucking programs, dispatching a motor-carrier-trained adjuster within minutes of a crash — location already known — is a direct cycle-time and severity lever.
Continuous vehicle telemetry is personal data when tied to an identified driver. Treating it casually creates regulatory exposure and, as SambaSafety's research shows, destroys the fleet trust that data-sharing programs depend on. A defensible governance posture for connected vehicle insurance data has four elements: written consent tied to a specific use-purpose list (rating, claims, safety coaching), minimum-necessary retention per data type, event-level access logging, and clean separation between aggregated fleet metrics used in rating and driver-level data used in claims investigation. Mercury enforces these distinctions through role-based access, purpose-tagged data stores, and per-source retention policies.
Litigation discoverability is a second governance dimension. Crash-event data will be subpoenaed; that is a feature when it protects the insured and supports subrogation — but it requires documented chain-of-custody, device calibration, and transmission integrity from day one. Carriers that build this discipline into their programs differentiate themselves in markets where nuclear-verdict risk is structurally elevated.
The evidence is now unambiguous that telematics works at the fleet level — crash reductions of 68-72% and premium savings of 25% for well-run programs are real. At the industry level, carrier results have not followed. The missing piece is integration: getting the signal from the device into the systems that bind policies, set reserves, and adjudicate losses in real time.
Quick Silver Systems built the Mercury Policy and Claims Administration System with this integration as a first-class concern. Telematics events are canonical inputs rather than bolt-on reports. Automated FNOL, geofenced coverage verification, and policy-linked event streams are configuration, not custom work. Carriers that close the gap between adoption and outcome turn fleet data into faster FNOL, cleaner underwriting, and defensible claims outcomes.
We would welcome a conversation about integration patterns with your current telematics stack and reference implementations for trucking programs.
Quick Silver Systems, Inc. makes the Mercury Policy and Claims Administration System. Contact us to discuss how telematics-integrated policy and claims workflows can support commercial auto, trucking, and specialty programs.