A complete field service platform — tickets, checklists, live expert calls, and AI — running on AR smart glasses
ContinuumAR brings together the tools field service teams actually need: structured ticket management, AR-guided checklists with a conditional rule engine, one-touch expert calling directly from an assigned job, and an AI assistant that answers questions about any ticket or call by voice. All of it runs on the technician's AR smart glasses, hands free.
Four integrated capabilities — one platform on the technician's AR glasses
Most field service platforms require technicians to switch between a work order system, a documentation tool, a communication app, and a manual. ContinuumAR brings all four into a single application running on AR smart glasses, controlled entirely by voice command in the field.
Every job starts and ends with a ticket
Tickets are the central object in ContinuumAR. Every call, every checklist, every recording, and every note is linked to its ticket — giving operations teams a single view of every job, its current status, and its complete history.
Structured procedures that enforce correct sequencing
Checklists are assigned to tickets and executed on the AR device. The technician sees questions one by one on their smart glasses and records responses by voice. The checklist cannot be skipped, bypassed, or completed out of order — mandatory locked states enforce the correct sequence.
Expert access from the ticket — not from a separate app
When a technician needs expert guidance, they initiate the call directly from their assigned ticket on the AR device. The call is linked to that ticket automatically — the video recording, annotations, transcript, and call summary are all attached to the job record when the session ends.
Ask questions about any ticket or call — by voice
ContinuumAR includes a conversational AI assistant inside the platform. Technicians and managers can ask questions in natural language and get immediate answers drawn from the ticket and call history — without navigating menus or running reports.
The ticket is the thread that connects everything
In ContinuumAR, a ticket is not just a work order reference. It is the live record of a job in progress — with its assigned checklists, its call history, its recordings, its notes, and its current status all visible in one place to the operations team and the expert.
When a technician arrives at a job, they open their assigned ticket on their AR smart glasses. Everything they need — the procedure checklist, the expert call button, the job notes — is accessible by voice, hands free, from that single ticket view.
When the job closes, the ticket contains a complete, auditable record: which checklist steps were completed, in what order, with what responses; which calls were made, with whom, and what was discussed; and which snapshots or recordings were captured. Nothing requires manual compilation afterwards.
Ticket created and assigned
The operations team creates a ticket in the web app, assigns it to a technician, and attaches the relevant checklist. The technician sees the ticket on their AR device when they log in.
Technician works through the checklist
The AR device presents checklist questions one by one. The technician answers by voice. The rule engine determines which questions follow based on their responses. Mandatory steps cannot be bypassed.
Expert called from the ticket if needed
If the technician needs guidance, they call the expert directly from the ticket on their AR glasses. The call is automatically associated with the ticket. Annotations, recordings, and the call transcript are attached to the job record when the session ends.
Ticket closed with a complete record
When the job is complete, the ticket holds everything: checklist responses and status history, call recordings and transcripts, snapshots, notes, and the full timeline of activity. Available immediately for compliance review, export to CSV, or print as PDF.
Checklists that adapt to what the technician finds — not just a static list
ContinuumAR's checklist engine goes beyond a simple list of steps. A conditional rule engine determines which questions appear based on the technician's previous answers. A Pre-Verification checklist that confirms safe isolation before work begins can automatically trigger a Diagnostic checklist if a particular condition is found. Safety steps marked as mandatory cannot be ticked off or skipped — the device locks the workflow until they are completed.
This structure matters in industrial field service because the consequences of skipping a safety verification or completing a diagnostic step in the wrong order are not theoretical. The checklist engine enforces correct sequencing at the device level, not through a paper-based honour system.
Checklist Rule Engine
Checklist Classification Types
Pre-Verification
Confirms conditions are safe and correct before work begins. Typically the first checklist in any job sequence.
Safety
Isolation verification, PPE confirmation, hazard identification. All steps mandatory — cannot proceed without completion.
Diagnostic
Structured fault-finding sequence. Conditional branching takes the technician down the correct diagnostic path based on findings.
Custom Types
Classification types are configurable for your specific operational procedures and naming conventions.
A chatbot that knows your tickets and your call history
ContinuumAR includes a conversational chatbot connected to your ticket data, call records, notes, and status history. Rather than navigating menus to find a specific job or call, you type — or speak — a question and get the answer from the record directly.
On AR smart glasses it works by voice. On the web app it is a chat window. The same queries work in both places. It is useful for technicians who need to check a job detail hands free, and for operations managers who want a quick view of what is open, who has what assigned, or what happened on a recent call — without pulling a report.
It handles ticket search by status and priority, ticket and call summaries, and access to notes and status history. Filtering by assignee is in development.
What you can ask it
Built for organisations running field teams across multiple sites
ContinuumAR includes enterprise-grade user, device, and domain management — designed for organisations where field teams operate across different sites, regions, or business units.
Multi-domain administration
A single client can operate across multiple domains — separate sites, regions, or business units — managed from a single admin account. Cross-domain user import and export is supported.
Device management
Device inventory is tracked per technician. Admins assign devices from the technician listing, manage QR code login credentials, and restrict multi-device login to prevent credential sharing. APK deployment via RealWear Cloud is supported.
Access controls and audit
Role-based access controls determine what each user can see and do. Technician user IDs are visible to admins and superadmins. End-to-end encryption and full audit logging are standard on all plans.
Where ContinuumAR field service is deployed
ContinuumAR field service is used wherever structured procedures, documentation, and expert access need to happen together — on the job, in the field, hands free.
Planned maintenance with enforced procedure compliance
Maintenance technicians follow AR-guided checklists on their smart glasses for scheduled equipment servicing. The checklist rule engine enforces the correct sequence of isolation, inspection, and sign-off steps. If a step reveals an unexpected fault, the technician calls the expert directly from the ticket — and the recording and transcript are automatically attached to the maintenance record.
Field operations with mandatory safety verification
Safety-critical field jobs require a Pre-Verification and Safety checklist before any work begins. ContinuumAR enforces completion — the device locks the Diagnostic checklist until the Safety checklist is fully complete. The operations team can see the checklist status for every active job in real time from the ticket dashboard.
Service calls with expert escalation built into the workflow
A service technician arrives at a site job, opens their assigned ticket on their AR glasses, works through the diagnostic checklist, and — if the fault is beyond their experience level — calls the expert without leaving the ticket or picking up a separate device. The expert joins, annotates the live view, resolves the issue, and the complete call record is attached to the job before the technician leaves site.
Operations management across multiple sites from one platform
An operations manager overseeing field teams across multiple sites uses the ticket dashboard to see job counts and status across all domains. The AI assistant lets them retrieve summaries of specific jobs, check what was discussed on recent calls, and identify open high-priority tickets — without manually searching through individual records.
Field service questions
Common questions from operations managers and IT teams evaluating ContinuumAR for field service deployment.
Ask a QuestionWhen you build a checklist in ContinuumAR, you define rules that determine what happens after each answer. If a technician answers "No" to a safety isolation question, for example, the rule engine can prevent them from proceeding to the next section until a corrective action is confirmed. If they find a specific fault condition, the engine can automatically branch them into a targeted diagnostic sequence rather than continuing the standard flow. Mandatory steps are marked at the checklist level — the AR device will not allow the technician to proceed past those steps without completing them.
Checklists are created, edited, and deleted directly within the platform by your own administrators — no involvement from the ContinuumAR team is required for ongoing checklist management. You define the classification type, the questions, the order, the conditional rules, and which steps are mandatory. Changes take effect immediately and are reflected on the AR device the next time that checklist is opened.
A single ContinuumAR client account can operate across multiple domains — each representing a separate site, region, or business unit. Each domain has its own users, devices, and tickets, but they are all managed from a single admin account. Users and devices can be imported and exported across domains. This structure is designed for organisations where field teams are geographically distributed but operations oversight sits centrally.
After each remote assistance call, ContinuumAR automatically generates a transcript of the conversation and a summary of the session — what was discussed, what was found, and what actions were taken. Both are attached to the ticket that the call was initiated from. They are accessible from the ticket detail page in the web app and can be retrieved through the AI assistant using a natural-language query. No manual documentation is required.
Yes. Ticket details can be exported to CSV directly from the platform, or printed as PDF for individual tickets. For deeper integration — automatic syncing of ticket status to your ERP, CMMS, or field service management system — ContinuumAR provides REST APIs and webhook support. Common integrations include SAP, ServiceNow, Salesforce Field Service, and Microsoft Dynamics.
See the full field service platform in action
We demonstrate ContinuumAR using your AR hardware and a workflow that reflects your actual field operations — tickets, checklists, expert calling, and the AI assistant together.