> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.getzendo.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# See what will happen before it happens, with the flow preview

When you set something up in Zendo, the result usually happens later and somewhere else: a purchase creates an order and a request, a request sends a message, an invitation sends an email. The flow preview shows you all of that while you are still setting it up. It sits on the right of the editor and lists, step by step and in plain words, what will happen and what your client will see, so you never have to sell something just to find out whether it works.

![The flow preview of a request type: what happens when a client submits it, step by step, with Edit links under each step.](https://getzendo.io/wp-content/uploads/2026/11/kb-q13-type-labels-v2.webp =639x465)

## Where you find it

| Editor | The flow preview answers |
|---|---|
| A service, in **Settings › Sales › Services** | What happens when a client buys or subscribes, and at every renewal: the order, the request, the trial, the payment, the invoice |
| A request type, in **Settings › Requests › Request types** | What happens when a client submits it: who can submit it, the form, the first status, who is assigned, the automatic messages |
| An onboarding card, in **Settings › Portal › Onboardings** | Which clients see the card on their dashboard |
| A quote or an invoice, in **Sales › Billing** | What happens when you send it: the email and the portal, the payment, and who marks it paid |
| An Intake Form, in **Library › Forms** | What happens when a client fills it in |
| **Add client**, in **Clients** | What happens when the client joins: the email they get, signing in, and who on your team is told |

In most editors the preview sits on the right, and the flow icon at the top hides or shows it. In the form builder, the flow icon next to **Preview** opens it.

## How to read it

- **The heading** says what the flow is about, for example *When a client submits "Support request"*.
- **Ready** means nothing is missing. Otherwise the preview counts the issues, for example **3 issues**, and the tab that holds the missing setting shows the same count.
- **Each step** says who acts — your client, Zendo or your team — and what happens, using your real names: your services, statuses, team members and the label of the request type, such as *Zendo opens the Ticket*.
- **Client sees it** marks the steps your client sees in their portal or inbox.
- **Edit links** under a step, such as **Edit statuses** or **Edit automations**, take you straight to the setting behind it.

The preview updates as you type, before you save. Change a status, a rule or an automation, and the steps change with it.

## Lists show what is still missing

You do not have to open each editor to find a problem. The **Setup** column in the list on **Settings › Sales › Services** shows what a saved service still needs before a client can buy it, and the **Who can submit** column on **Settings › Requests › Request types** shows who each request type is open to.

## Issues are things that will not work

An issue is a setting that is missing or does not fit, so the flow would break: for example, a client you are adding without an email address, who would never get the invitation. The preview says what is missing and offers a button to fix it, such as **Add account details**. Fix the issues before you save, and the preview switches to **Ready**.

![Adding a client: the flow preview lists what is still missing (3 issues) before the client can join.](https://getzendo.io/wp-content/uploads/2026/11/kb-c1-add-client.webp =666x559)

## Why it matters

Without the flow preview, you would learn how a service is set up from your first client, when they pay and nothing happens. With it, you see the whole path in one place, on the screen where you change it. It is also the quickest way to understand a setup someone else on your team built: open the editor and read the steps.

## Related

- [Decide what happens after a purchase](https://help.getzendo.io/en/article/decide-what-happens-after-a-purchase-kdi63s/)
- [Automate a request type](https://help.getzendo.io/en/article/automate-a-request-type-1m2cf6k/)
- [Create an onboarding card](https://help.getzendo.io/en/article/create-an-onboarding-card-j508us/)
- [Add clients](https://help.getzendo.io/en/article/add-clients-1mfm23b/)
- [Decide who can submit a request type](https://help.getzendo.io/en/article/decide-who-can-submit-a-request-type-1m352cm/)