Your training data, wired into the rest of the business
TrainAR knows what your engineers have trained on. Your job system knows what work they have done. Your accounts know what it earned. Connect Tugger and those stop being three separate stories. Tugger pulls your TrainAR sessions, tasks, users and forms into one place alongside ServiceM8, Simpro, BigChange, Xero, BambooHR or whatever else you run, then you ask questions across the lot in plain English through Claude or ChatGPT. Read-only, one direction, nothing written back.
What "ask your training data anything" actually looks like
Office manager, Monday morning, looking at next week's schedule.
Two questions. One spans training tasks and next week's schedule, the other turns hardware you have bought into a utilisation number. Neither system could answer either on its own.
What TrainAR data Tugger reads
When you connect Tugger to Claude or ChatGPT, these are the tools it can call. Every one of them is a read. There is no write tool, so nothing in your systems can be altered by asking a question.
read sessions
AR training sessions with durations, dates and outcomes. Powers adoption and utilisation questions across your engineers.
read tasks
Training tasks with status, due dates and the job reference they carry, so training can be lined up against the job it belongs to.
read users
Engineer records matched on email, so training sits next to start dates, roles and teams from your HR system.
read forms
Completed forms and their fields, available for reporting alongside everything else you have connected.
Read-only by design
No write, update or delete tool exists in the set. Nothing in TrainAR or anywhere else can be changed by a query.
Audited & scoped
Permission-scoped access per account. Every query runs through an audited surface, so you can see what was asked and what was returned.
Questions worth asking once it is connected
Ask in plain English
- "Who has glasses assigned and hasn't run a session in a month?"
- "Show me open training tasks past their due date, by assignee"
- "How long are training tasks taking from created to completed, and is that improving?"
- "Total training minutes by role and by depot over the last six months"
- "Which jobs went out with the attached training task still open?"
How the cross-system joins work
- Training tasks arriving from your field service system carry your own job reference, so Tugger lines training up against the job it belongs to.
- On the people side, user email connects TrainAR to your HR system, so training sits next to start dates, roles and teams.
- Prefer dashboards? Tugger feeds TrainAR data into Power BI and Tableau alongside everything else you have connected.
Read-only, scoped and audited
ISO 27001 certified
Your data sits in Tugger's UK-hosted environment on Microsoft Azure and refreshes automatically.
Read-only by design
No tool in the set can write, update or delete anything, in TrainAR or anywhere else.
Permission-scoped per account
Access is scoped per account and every query runs through an audited surface.
Yours to revoke
Your data is not used to train AI models. Revoke access from your Tugger account and the sync stops immediately.
Common Tugger questions
Do I need a particular TrainAR plan?+
Any plan with API access. Tugger authenticates against your normal TrainAR account.
Does Tugger change anything in TrainAR?+
No. Read-only, one direction. Your training records stay exactly as they are.
Do I need another system connected for this to be useful?+
Not strictly. TrainAR data on its own gives you adoption, utilisation and task throughput. The interesting questions come from adding your job system, and the really interesting ones from adding your accounts and HR.
Do I need to know SQL or build dashboards?+
No. You ask in your own words through Claude or ChatGPT. Power BI and Tableau are there if you want them.
How fresh is the data?+
It refreshes automatically on a schedule. Nothing to export by hand.