How EV Companies Can Build a Connected Customer Platform

A traditional automotive sale ends the active customer relationship until the next service appointment. An EV is different: it reports charging sessions, battery state of health, software version and usage telemetry continuously, whether or not the customer has any active interaction with the brand. This creates a stream of operationally relevant data that most customer platforms are not architected to receive, store or act on.

The result, in practice, is that this telemetry often ends up in a separate vehicle or IoT platform managed by engineering, disconnected from the customer record managed by sales and service. A service advisor speaking with a customer about a range complaint may have no visibility into that vehicle's actual charging pattern or battery degradation curve, and is left working from what the customer describes rather than what the vehicle has already reported.

A connected customer platform treats vehicle telemetry as customer data, not purely engineering data. That does not mean every service team member needs raw telemetry access, but it does mean the relevant, interpreted signals — degraded battery health, an unusual charging pattern, a fault code — need to reach the systems where customer relationships are actually managed.

Many EV manufacturers sell directly to consumers rather than through a franchised dealer network, which removes a layer of data fragmentation that legacy automotive OEMs struggle with, but adds a different kind of complexity. The manufacturer is now directly responsible for financing, configuration, delivery logistics, after-sales service and often the charging experience, all of which were previously split across dealer, OEM and finance company systems.

This means the EV customer profile has to hold far more than a traditional CRM record: vehicle configuration and options at order time, financing and lease terms, delivery status, home charger installation status, software subscription entitlements and service history, all tied to one customer and one vehicle identity. If these live in separate systems — a configurator, a finance platform, a charging partner, a service tool — the company recreates the exact fragmentation that dealer networks caused in the legacy model, just inside its own walls.

The direct-to-consumer model is an advantage only if the manufacturer actually unifies what it now owns. Owning every stage of the relationship without connecting the data behind it produces a customer experience that is no better than the fragmented dealer model it was meant to replace.

Battery degradation is gradual, measurable and central to both customer trust and warranty exposure, yet many EV manufacturers can only assess it reactively, when a customer complains or brings the vehicle in for service. By the time that happens, the manufacturer has lost the opportunity to intervene early, and the customer has already formed a negative view of the product's reliability.

A connected customer platform makes battery health a proactive signal rather than a reactive complaint. Degradation trends reported by the vehicle can be evaluated against warranty thresholds continuously, allowing the manufacturer to reach out before a customer notices reduced range, or to flag a vehicle approaching a warranty boundary so service and finance teams are not surprised by a claim.

This also has direct financial relevance. Warranty reserves for battery replacement are typically estimated using population-level assumptions about degradation. A manufacturer that can see actual, vehicle-level battery health data has a materially better basis for warranty reserve accuracy and for identifying whether degradation patterns are consistent with expectations or indicate an emerging quality issue that needs to be addressed before it scales across the fleet.

Software delivered over the air means two vehicles of the same model and year can behave differently depending on which update has been applied, when it was applied, and whether it succeeded. Customer service and technical support need to know the exact software state of a vehicle to diagnose an issue accurately, but this information frequently sits in a software deployment system that customer-facing teams cannot see.

This is a straightforward but frequently overlooked integration requirement: current software version, update history and any failed or pending updates need to be visible alongside the customer and vehicle record used by service and support. Without it, support interactions default to generic troubleshooting scripts that do not account for the fact that the reported issue may already be resolved in a pending update, or may be a known issue specific to one software version.

EV manufacturers increasingly sell software-based features — extended range, advanced driver assistance, connectivity packages — as subscriptions rather than one-time purchases baked into the vehicle price. This introduces recurring billing, proration, entitlement activation and renewal logic that a traditional one-time vehicle sale record was never built to handle.

A customer platform built for a single transaction treats the sale as complete once the vehicle is delivered. A platform built for subscription entitlements has to track what a customer is currently entitled to, what has lapsed, what is due for renewal, and how a feature entitlement maps to an actual capability activated in the vehicle. Getting this wrong produces customer-facing failures that are highly visible and reputationally costly — a customer who paid for a feature that was never activated, or one who is billed for a subscription tied to a vehicle they no longer own.

None of this requires forcing every source system — telematics, charging network, billing, service — into one platform. It requires a clear customer and vehicle identity model that every system references consistently, and an integration layer that brings the relevant, interpreted data from each source into the systems where customer relationships and service decisions are actually managed.

AX3 approaches this by establishing that shared identity model first — one customer, one vehicle, consistently referenced across configurator, finance, charging, telematics, software deployment and service systems — before building the connected experiences on top of it. Automotive Cloud, Data 360 and connected-vehicle integration engineering are used to bring telemetry, battery health, software state and subscription entitlements into a single governed customer view, so that sales, service and support are working from the same picture of the vehicle and the relationship, rather than from whichever system happens to be closest to hand.