Road journeys need more than a destination. Discover nearby service points and route stops, view their details and use roadside request tools when help is needed.
Illustrative scene. Local services and availability vary.
A CLOSER LOOK
When plans change, useful local details matter. Find the right kind of help or stop, then confirm what is actually available.
01
Match the problem to the service.
Mechanics, tyre shops and towing providers solve different problems. Describe the issue clearly and verify the service area, hours and next steps. A listing does not guarantee that a provider is currently accepting requests.
02
Plan the stops that make a route usable.
Parking, food, restrooms and highway places can be as important as the destination. Review location details and how far a stop takes you off-route before relying on it.
03
Know the difference between a request and help arriving.
Use available SOS and request history to keep track of the information you submitted. There is no guaranteed response time. In an immediate danger or medical emergency, contact the appropriate emergency services directly.
AN EVERYDAY EXAMPLE
A tyre problem, not a guessing game.
Look for a nearby tyre service rather than a generic garage. Read the service details, share the problem and location, and confirm whether the provider can help before expecting a visit.
A relevant listing and a clear request are a better starting point.
Map: nearby category shortcuts, destination search and SOS.
ATM & washrooms
Find nearby cash and restroom listings with location details.
Listing-dependent
Food & parking
Explore places to eat and park around your route.
Listing-dependent
Mechanic, tyres & towing
Inspect relevant roadside business details and available contact options.
Listing-dependent
Destination search & navigation
Choose an endpoint, preview a route and open navigation when the mapping integration is available.
Provider-dependent
SOS request & history
Submit roadside-help information and follow request history. No response time is guaranteed.
Operator-dependent
App workflow means the flow is implemented in the app source, not that the app is publicly released or every dependency is live. Check the app guide and the actual listing or provider status.
Use the app guide to find the relevant tab or role. Account access, local coverage and external service configuration are separate requirements; a website description does not activate a service.
Find a nearby service or open the roadside-help flow.
02
Check business details and available contact options.
03
Submit a request where supported and track its status.
LOCAL COVERAGE
Know what to expect.
Service coverage and response depend on local partners; no response time is guaranteed. For an immediate danger, contact local emergency services directly.