Your team may already have an AI assistant it likes. The useful question is not whether to replace it. It is whether that assistant can help with the actual device work and leave something the next technician can use.
OpalSpan starts with Mech, the built-in AI technician in your browser. Choose an authorized device, describe the job and review the result. There is no CLI installation needed to work with Mech.
If you prefer your own assistant, OpalSpan Agent CLI gives that assistant another route into authorized support work. You provide intent and review; the assistant operates the CLI.
Keep the team context
The current release lets authorized agents find customer and case context, add findings, correct notes with their earlier revisions retained, and work with case collaborators. These are shared work records, so the useful handoff can be the finding and next step rather than another transcript to reassemble.
For example, ask for an investigation of an intermittent connection, then a case note separating what was observed from what remains uncertain. A clean check today is not proof that an intermittent problem has disappeared. This is an example task, not a reported customer result.
Mech’s private conversations and files do not automatically transfer to an external assistant. Use the authorized case record for the context the team needs to share.
Prepare the reply. Keep the human decision.
A customer draft is separate from an internal note. With Mech or your external assistant, review the exact recipient, subject and body before approving that version for private text export.
Changing the content or recipient invalidates the earlier review. Neither route sends the message: your team uses its own communication tool when it is appropriate to send.
That makes the handback useful without turning a model’s suggestion into your approval.
Read the Case and review one exact customer draft
Mech reads an appointment note attributed to an example external assistant. The technician reads the full recipient, subject and body before approving the example revision for private export.
Source
Current shared Mech and Case components, generated 5 October 2026 with fictional names, recipient and content. Offline illustration: no external assistant is connected, no account or device is accessed, and nothing is exported or sent. The Case records an appointment request, not a repair. Any edit invalidates review. Private Mech conversations and files do not automatically transfer to another assistant; the same user permissions still apply.
Same people, same permissions
An assistant does not become an unrestricted administrator. Case work follows the signed-in person’s existing rights. Team invitations, workspace settings and billing remain Admin actions; Mech presents consequential changes for the authorized person’s decision.
Paid plans for new DKK orders have no per-person charge. Mech uses OpalSpan AI credits; an external assistant keeps its own account and model costs. Actual device work uses the same shared work-session rule through either route.
Windows and Linux are supported; macOS is a technical preview, in active development. Normal signup, plans and Help are the starting point, with optional support if you want it.