The connected support workflow

From a support request to a verified handback.

Forge connects the parts of device support that usually drift apart: the customer's problem, authorized access, technical work, evidence and the case record. The technician defines the outcome and boundaries; Whisper or a local agent carries the work forward.

Is Forge right for your team?

Start with one real support case.

A good fit when
You support Windows or Linux devices and want agents to perform scoped technical work without losing customer context or technician oversight.
Start with
Create a workspace and one case, then enroll a supported device or prepare an attended Rescue handoff before assigning a bounded task.
Know before you start
Forge is not remote desktop or unattended repair assurance. Devices must be reachable, permissions still apply and physical work stays with people.

From conversation to useful work

See the findings. Understand the next step.

FORGE / WHISPERIllustrative demo workspace
Whisper investigates slow startup without changing the user's machine.
Actual Forge interface · fictional scenario, not a live repair record.
01 / THE WORKFLOW

Connect the request to the right context

Record the customer, contact and reported problem in a case. Link the device when it is known; a case can start before access exists. Customer contacts do not become Forge technicians.

02 / THE WORKFLOW

Establish explicit device access

Use persistent Forge Daemon enrollment for ongoing support or an attended Rescue session for a temporary handoff. Windows and Linux are supported. The repair Live USB is locally assembled, manually booted media—not a hosted ISO or automatic recovery guarantee.

03 / THE WORKFLOW

Choose Whisper or your local agent

Describe the outcome in browser-based Whisper, or use Forge Agent CLI with the agent and terminal tools you already trust. Both paths use Forge workspace and device authorization; neither bypasses control leases or supplier limits.

04 / THE WORKFLOW

Inspect, verify and hand back

Follow commands, diagnostics and findings, authorize consequential changes and check the result. Keep symptoms, actions, evidence, uncertainty and next steps in the case, then review any customer communication before it leaves your team.

Useful boundaries, up front.

Does Whisper only investigate, or can it repair?

Both. Specify a read-only investigation when users must not be disturbed, or authorize a repair with clear scope. Whisper can execute commands and transfer files, verify results and update cases. AI can make mistakes; review consequential work and do not assume every successful command proves a repair.

What happens when the device is offline or a physical check is needed?

The limitation should be reported rather than worked around with a guessed result. A machine must be reachable for remote work. Physical inspection, replacement parts and confirmation of actual printed output still require someone on site.

Do I need to replace my existing local agent?

No. Use Whisper in the browser or Forge Agent CLI with your local agent. The same workspace and device access boundaries apply. Forge provides command and file access, not screen sharing.

Bring your next support case.

Create a workspace, connect a supported device and start with a clearly scoped task. Choose the plan and AI credit allowance that fit your work.