The AI Assistant has seven agents. Pick the one whose job matches your question; each agent also knows how to find a screen and explain the steps. On the AI Agents screen the agents appear as cards, and an administrator can hide some of them. The example questions below are the suggestions each agent offers in a new chat.
Every lookup runs with your own permissions. An agent cannot show you data that your role cannot open on its own screen.
All agents can use these, on top of their own:
- Find the screen for a task and read its steps.
- List what the agent can help with.
- Read your organisation's details, its users and its sub-accounts.
- List units, read one unit, and check the live state of every vehicle: moving, idling, parked or offline.
- List devices.
- Turn map points into street addresses.
- List the report templates, read what a report produces, check which units can answer it, run it for a period and draw its charts.
- Look at the reporting catalogue and compose a report on the spot when no template fits.
- Save a composed report as a template in your own list.
Finds the right report, runs it over the period you mean, and explains what the numbers say.
- Covers: finding the right report, running reports, building custom reports and putting reports on dashboards.
- Example questions: "What reports can I run?", "Run last week's trip report", "Which vehicle drove the furthest last month?", "Chart our fuel level over the past week", "Are my report exports ready?"
- Its own lookups: recent report runs and their status, the rows of a stored run, the size of a report before you run it, your dashboards and their widgets.
- Changes it may make: update a report template of yours, export a report as an Excel, PDF or CSV file that appears under Saved reports, create a dashboard, and put a report on a dashboard as a chart, table or KPI.
Answers questions about your units, their trips and the events they recorded.
- Covers: unit lookup, trip history and an event timeline.
- Example questions: "Which vehicles are moving right now?", "Which vehicles have stopped reporting?", "Show recent trips for one of our vehicles", "Which vehicle drove the furthest last week?", "How many trips did we do yesterday?", "Who was driving our van last Monday?"
- Its own lookups: the trips of a unit and the details of one trip, the recorded events of a unit, the GPS points of a trip, the odometer and engine-hour readings, the change log of a vehicle, its allocation history and a driver's details.
- Changes: none beyond saving a report.
Checks device inventory, connectivity and sensor readings to help you narrow down a fault.
- Covers: connectivity checks, the device inventory, SIM health and sensor setup.
- Example questions: "Which devices have stopped reporting?", "Why is one of our vehicles not tracking?", "How many SIMs are overdue for recharge?", "Which SIMs are not fitted to a device?", "Which devices are on old firmware?"
- Its own lookups: one device in full, its configured sensors (the setup, not readings), the supported device models, SIMs and their recharge history, SIM totals, the commands sent to a device and the commands a model supports, and a device's allocation history.
- Changes: none beyond saving a report. It cannot restart a device, change its settings or send a command.
Answers questions about your organisation, its users, roles and sub-accounts.
- Covers: organisation details, role lookup, the user directory and permissions.
- Example questions: "Who has access to this account?", "Which users have admin access?", "What can each role actually do?", "Are any invitations still pending?", "What sub-accounts do we have?"
- Its own lookups: the roles of the organisation, what one role may do, the catalogue of permissions and pending invitations.
- Changes: none beyond saving a report.
Answers questions about zones, planned routes, their timetables and whether vehicles kept to them.
- Covers: geofences, routes and checkpoints, timetables and route adherence.
- Example questions: "Which geofences do we have?", "Did the morning route run on time yesterday?", "Which route runs were late this week?", "Which vehicles are on the depot schedule?", "What checkpoints does our depot route have?"
- Its own lookups: geofences, routes with their checkpoints, the timetables of a route, the vehicles assigned to a timetable and the journeys actually run.
- Changes: none beyond saving a report.
Explains which alert rules exist, what each fires on, what fired and why someone was or was not told.
- Covers: alert rules, why no notification went out, who gets told, what fired and acknowledging an alert.
- Example questions: "Which alerts are open right now?", "Any critical alerts today?", "Why was nobody told about the last alert?", "What can I set alerts on?", "Acknowledge the latest open alert"
- Its own lookups: alert rules in full, with thresholds, vehicles, active hours and recipients, and the kinds of alert you can set up. Also the current incidents in the Alert Centre, alert counts, the alert history for a period, and one incident with its timeline, delivery log and escalations.
- Changes it may make: acknowledge one open alert incident, and only after you select Confirm. See Confirm a change the assistant prepared.
¶ Maintenance
Answers questions about service reminders, work already carried out and what maintenance costs you.
- Covers: what is due, service history, maintenance spend and service types.
- Example questions: "Which vehicles are overdue for service?", "What service is due in the next week?", "Which vehicle has the most overdue items?", "Show the last completed service for a van", "How do I log a completed service?"
- Its own lookups: service reminders across the fleet, one reminder in full, completed services with their line items and the service types.
- Changes: none beyond saving a report.
When you ask the Alerts & Rules agent to acknowledge an alert, it changes nothing by itself. It puts a card under its answer that says what will happen, for example which rule, unit and severity, and when the alert opened. Acknowledging stops the alert's pending escalations, and anyone the rule notifies on acknowledgement is told.
- Read the card.
It says "Waiting for your confirmation", "Nothing has changed yet." and how many minutes are left before it expires.
- Select Confirm to acknowledge the alert, or Cancel to leave it.
The card shows the outcome, and the assistant adds a sentence that says what happened.
| Card state |
Meaning |
| "Confirmed and done" |
The alert is acknowledged. |
| "Cancelled — nothing was changed" |
You selected Cancel. |
| "Expired — nothing was changed" |
Nobody confirmed in time. Ask again if you still want it done. |
| "Not done" |
The change failed. The sentence under the card gives the reason, for example that the alert was already resolved or cleared. |
Before you start:
- Acknowledging needs Alert Incidents with Edit, the same as on the Alert Centre. The app checks your rights again when you select Confirm.
- The agent acknowledges one open incident per request. To acknowledge several, use the Alert Centre.
- An alert that belongs to a parent organisation can only be acknowledged there.
Some tasks stay with a person. If you ask, the agent says so and points you to the right screen:
- Delete a report or a template. Other people may rely on it.
- Open another account for you. Support staff do that from the account list, and every such session is recorded.
- Handle passwords, sign-in or sessions. Use Forgot Password? on the sign-in screen, or change your password from your profile.
- Remove a unit or cancel its allocation. It affects tracking history and billing for good.
- Send a command to a device. A command changes how a tracker behaves in a moving vehicle.
An agent also does not add, edit or delete units, devices, geofences, routes, alert rules, users or roles. Apart from acknowledging one alert, it does not resolve incidents, retry deliveries or change alert preferences. It tells you which screen does it and the steps.