Using a Copilot
What a Technician does inside a copilot — ask, hands-free, resources, tasks, Periscope Mode, escalation, and the two tabs that differ between products and assets.
Opening a product or an asset puts you inside its copilot. From there the work is the same whichever one you came in through: ask a question, open a document, or run a task. Two tabs differ — a product has Current Data, an asset has Configuration.
| Page | What it covers |
|---|---|
| Asking Questions | The Ask tab, how an answer is built and how to read it, the sources behind it, and the controls under it |
| Hands-Free Operation | Asking by voice, hearing the answer read aloud, and opening the references behind it |
| Viewing Resources | The Resources tab, what is filtered out and why, the document viewer, and what is held on the device |
| Running a Task | Finding a task and running it step by step, recording data, branching, and closing it out |
| Current Data | Products only — the copilot's technical metadata |
| Configuration | Assets only — the identity and variables of one specific machine |
| Periscope Mode | Turning a task into an outline, so you can jump straight to any step |
| Escalate | Routing a job to support, or handing it to another Technician with a handoff code |
The tab strip sits across the top of the copilot, and stays available while a task is running.
| Tab | Product | Asset |
|---|---|---|
| Ask | ✓ | ✓ |
| Resources | ✓ | ✓ |
| Tasks | ✓ | ✓ |
| Current Data | ✓ | |
| History | ✓ | |
| Configuration | ✓ | |
| A tab per question | ✓ |
On a product, each question opens its own named tab to the right of Current Data, so several open questions stay side by side. On an asset the conversation stays on the Ask tab itself.
Updated 1 day ago
