Write a PC service report with the AI assistant

Export an AI session as an HTML, Markdown, or text report, or run the Technician Service Report workflow, in S.A.K. Utility.

To write a service report with the AI assistant in S.A.K. Utility, finish the job on the AI Assistant tab, then press Report above the chat and choose where to save. You can save it as HTML, Markdown, or plain text. For a report written by the AI for a customer, run the Technician Service Report workflow first.

When to use this

  • You finished a repair with the assistant, and need a record of what was found and done.
  • You are handing a PC back and want to explain the work.

What you need

  • A chat in which a local action or workflow has produced results. Report stays greyed out until then, so a plain question-and-answer chat usually has nothing to report.
  • For the workflow: your OpenAI API key. Report itself makes no AI request.

Steps

Export the session

  1. Open the chat you want. The Chat session list on the right has your recent chats.
  2. Wait for the assistant to finish. Report is greyed out while it works.
  3. Press Report, above the chat.
  4. In Save AI Report, choose a folder and a type: HTML Report, Markdown Report, or Plain Text Report.
  5. Press Save. S.A.K. Utility opens the report for you.
AI Assistant tab with Details, Artifacts, and Report buttons above the empty chat, with Report greyed out
Report stays greyed out until a chat has results

Have the AI write a handoff report

  1. In the same chat as the job, open the Workflow list and pick Reporting - Technician Service Report (5 phases).
  2. Press Add, then Send. It asks for no extra details.
  3. When it finishes, press Artifacts to open the folder holding the chat's output.
Workflow section with Technician Service Report selected and its details panel open
The report workflow uses evidence from the current chat

How it works

Report builds the file from what the chat recorded. It is titled AI Session Report, and starts with its status, date, chat name, tool call count, and token count. It then has sections such as:

  • Executive Summary
  • Key Findings
  • Evidence Snapshot
  • Recommended Next Steps
  • Evidence Limits and Risks
  • Work Performed
  • Evidence Notes
  • Evidence Artifacts
  • Sources
  • Appendix: Raw Transcript Excerpts

A workflow run also adds a Workflow Timeline.

The Technician Service Report workflow goes further, in five phases. It collects the chat's evidence, drafts the report, has a second AI review it for secrets, personal data, and unsupported claims, finalizes it, and tidies up its scratch files.

Good to know

Read a report before you send it. The appendix holds raw excerpts from the chat, and the AI's privacy review can miss things. Reports include file paths from the PC. Remove anything your customer should not see.

  • A report only covers this chat. If the work was split across chats, export each one.
  • The report shows what the session recorded. It can be wrong if the AI misread something, so check its claims against the evidence section.
  • Artifacts opens a folder only once the chat has saved a file.
  • This is separate from the Scan Report on the Benchmark and Diagnostics tab, which covers hardware scans and has fields for technician and ticket details. See the diagnostic report guide below.