Use Cases

Process Documentation Software

Use Guide Agent as process documentation software when repeatable workflows need product screens, clear instructions, and reusable context.

Document processes from captured workflows

Process documentation explains how work moves from one step to the next. For software teams, that often means documenting product workflows, internal tools, customer-facing processes, and handoffs across teams.

Guide Agent helps turn captured workflows into process documentation that shows what happens on screen and explains why each step matters. That makes the process easier to learn, repeat, and update.

This use case is broader than SOPs. It can cover support handoffs, onboarding processes, operations playbooks, customer success workflows, and internal product administration.

Problems this solves

Process docs explain the policy but not the screen-level workflow.

Teams document handoffs in scattered docs and ticket comments.

New teammates cannot tell which steps are required and which are context.

Processes change when the product changes, but documentation lags behind.

Process documentation workflow in Guide Agent

Step 1

Capture the workflow path

Bring in the product screens or internal tool screens that show the process from trigger to completed state.

Step 2

Name roles and handoffs

Ask the agent to explain who performs each part, what information is needed, and what happens after each step.

Step 3

Clarify required decisions

Add notes where users must choose between paths, check account state, or escalate to another team.

Step 4

Publish as a reusable process guide

Share, embed, or export the process documentation so teams can use it where work happens.

Example: approval process documentation

An operations team needs to document an approval workflow that involves a request form, an admin review screen, and a final customer notification.

Guide Agent can turn the captured workflow into process documentation that explains each role, required decision, and final state.

Show where the process starts and what triggers it.
Document the handoff between roles.
Include the final state that confirms the process is complete.

What you can create

Process documentation

Workflow documentation

Operational playbooks

Internal process guides

Customer-facing process guides

Step-by-step process documents

When to use it

A process depends on software screens or internal tools.
Several teams need to understand the same workflow.
A handoff or decision point causes confusion.
The process needs to be shared, embedded, or exported.

Why Guide Agent

Process documentation starts from the actual workflow, not memory.
The agent can explain steps, handoffs, and decisions in plain language.
Reusable screen context helps update process docs when tools change.
Teams can create internal and customer-facing versions from the same flow.

Example prompts

Document this approval workflow for the operations team.

Create process documentation from these captured product screens.

Rewrite this process guide for a customer support audience.

Add handoff notes for the parts owned by different teams.

FAQ

How is process documentation different from an SOP?

An SOP usually standardizes exactly how a task should be done. Process documentation can also explain handoffs, roles, context, and how a workflow works end to end.