> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcdemo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Teach a customer workflow

> Create an onboarding or support guide that helps a reader repeat the task.

An onboarding demo succeeds when the customer can perform a task afterward. Pick one task with a clear starting point and observable result, such as creating a workspace or inviting a teammate.

## Build for the moment of need

1. State the prerequisite and outcome. For example: “You need access to a workspace; by the end you will have invited a teammate.” Use a task and prerequisites that match your product.
2. Capture the shortest real path with safe sample data. Include the confirmation or resulting state, not just the last click.
3. Write one action per step and explain the consequence when it is not obvious. Use the product's actual labels.
4. End by telling the reader how to return to their own account and repeat the task. If permissions or settings can change the path, explain the relevant difference in the surrounding article.

### Example: invite a teammate

In a fictional product, the reader's goal is to invite a colleague to a workspace. Start on the workspace settings screen, show where to open the team area, enter a fictional address, choose a role, and show the invitation's pending state. The result is “an invitation was sent,” not “the colleague has joined”: those are different states and can require different follow-up.

The article around the demo should answer the questions a recording cannot settle for every reader:

* **Before starting:** What access or information does the reader need? Where do they start?
* **At the decision:** How should they choose a role in their own workspace? Link to your product's actual permissions reference.
* **After the last step:** Where can they check a pending invitation, and what should they do if the recipient cannot join?

Use the example only if it matches the product being documented. A task involving deletion, billing, or a permission change needs a clear explanation of its consequences in the written instructions, not just a recording of the clicks.

## Put it in context

Embed the demo alongside written steps in the help article. The text should remain useful if the embed cannot load, and should cover prerequisites, alternative routes, and where to get help. Give any embedded player enough room on mobile and test it in the actual destination.

Review the flow with someone who did not build it. Ask them to explain what they would do next in their own account, then revise any step that requires coaching. After publishing, check the share link and revisit the demo when the product changes. See [Keep a demo current](https://docs.arcdemo.io/guides/maintain-a-demo.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.