Current scope and good to know

To set expectations correctly, this is what the plugin does not do today:

• Navigation happens in your maps app. The route screen is an ordered list of stops, not a map with turn-by-turn guidance. The Map button hands the destination over to Google Maps, Waze or whichever app the technician prefers, which is also what gives access to live traffic and voice guidance.
• Arrival is confirmed by the technician, not detected automatically. There is no geofence: the work timer starts when the technician stops the travel timer on arrival.
• Timer notifications are local to the technician's phone. They show that a timer is running; they are not GLPI e-mail notifications to supervisors. Supervisors follow progress through the Live Routes tab.
• Reporting is done through GLPI lists and the CSV export, not through dedicated KPI dashboards.
• Every route calculation consumes Google API quota. Creating or editing a route triggers several calls. Disabling Billing includes return trip roughly halves that consumption.
• A ticket visited in more than one route appears once per visit in the CSV. That is intentional — each visit is a separate journey with its own times and distances.