Route a Stellantis Uconnect Assist/roadside call to provider dispatch
domain: stellantis.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Vehicle occupant presses the Assist Call button (or SOS Call button for collision/emergency) in the Uconnect-equipped vehicle
The call connects to a Stellantis customer care agent along with the vehicle's telematics location data
Agent determines the appropriate service (roadside assistance vs. emergency/collision response)
Agent dispatches the roadside request to the provider network to send help to the vehicle's location
Coverage runs under the vehicle's Safety & Security Package, active for a defined ownership period (currently the first 10 years on covered 2024 model-year Chrysler, Dodge, Jeep, Ram, Wagoneer, Maserati, and Alfa vehicles)
Known gotchas
The Assist Call and SOS Call are distinct triggers (roadside vs. emergency/collision) routed differently on the backend; don't conflate them as one flow
Underlying connected-vehicle data access for fleets runs through Stellantis's Mobilisights/Geotab partnerships, a separate channel from the consumer-facing Assist Call roadside flow
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?