A Flow orchestrates several steps, in a defined order, within a single response experience. Each step is a woku or an NPS, CSAT or CES tool. It is the right tool when a single question is not enough to understand what happened.
Composition
A Flow is made up of:
- Name: identifies the Flow internally.
- Ordered steps: from 1 to 20 steps. Each step is a woku, an NPS tool, a CSAT tool or a CES tool of your company, in the order in which you want the customer to answer them. A tool appears only once.
The tools that make up the Flow must already exist: you first create them in the usual way and then combine them inside a Flow. A closed woku, or one set to one review per customer, cannot be a step. A Flow does not live inside folders.
Flows that already existed, an optional NPS at the start followed by wokus, keep working the same way and are read as steps in that same order.
Order of the sequence
Order matters. Each step builds on the previous one, and the customer perceives it as a coherent journey. Some rules that work well:
- Start with the general and end with the specific, or the other way around. What matters is that there is a logic to it.
- Do not mix moments that are too different in the same Flow. If a customer is going to evaluate an event, keep the Flow focused on that event.
- Keep it between 2 and 5 steps. Beyond that, the completion rate starts to drop.
Order in the customer experience
The customer goes through the steps in the order you defined. If the first step is an NPS, it captures the recommendation question while they have not yet stopped to think moment by moment.
A CSAT or a CES in the middle of the journey measures satisfaction or effort right after a specific step.
Progress bar
While the customer moves through the Flow, they always see which step they are on, for example “Step 2 of 4”. This reduces the feeling of “I do not know when this is going to end” and increases the chance that they complete the whole journey.
Customer identification
If the customer decides to identify themselves with their email in the first step, that same email is automatically associated with the responses of the following steps (whether wokus, NPS, CSAT or CES). This lets you reconstruct the complete journey of a single customer without asking them to repeat their information.
If the customer decides to answer anonymously, all steps remain anonymous.
Sharing
Sharing a Flow works the same as a woku or an NPS:
- QR code: to print or show on a screen.
- Link: to send by chat, WhatsApp, or paste on your site.
- Bulk email send: by pasting a list from a spreadsheet.
The customer is given a single link, not one per woku. It is the Flow that handles advancing step by step.
Reports
The responses of each step are saved in their own tool (woku, NPS, CSAT or CES). This means that:
- Individual reports by woku, NPS, CSAT and CES keep working as always.
- The Flow view shows you how many people started and how many completed the journey.
Editing and deleting
You can edit a Flow to change the name or replace its list of steps: add or remove tools and reorder them. The changes affect new customers who open the link, not those who already answered.
Deleting a Flow does not delete the tools that made it up, nor the responses already captured. It only deactivates the chained experience.
API, SDKs and MCP
A Flow is managed with GET, POST, PATCH and DELETE on /v1/flows, with woku.flows in the JavaScript and Python SDKs, and with create_flow, update_flow and get_flow on the MCP server. All of them use the ordered list of steps (steps, each { type, toolId }).
For an nps step, your company id as toolId means the company-level NPS. More in the API integration guide. Última modificación el 12 de octubre de 2026