Guides
Start with the customer’s task, not an empty diagram.
A wardrobe enquiry shows how questions, conditions and a human handover fit into one scenario.
Chawo is preparing for launch. We are taking early-access requests; AI and channel connections are not available yet.
Start with the request
A customer asks for a fitted wardrobe in a narrow hallway and wants room to walk past it. Before suggesting a model, the conversation needs to establish the available space and whether the niche has been measured. That practical decision gives the scenario its starting point.
Name the decision
Write down the condition that changes the next reply: dimensions known or dimensions missing. One branch can prepare a selection; the other should lead to a measurement request. Keep both routes visible so that a polite answer does not accidentally send the customer towards an unsuitable next step.
Prepare the handover
The designer needs the wardrobe requirements and the customer’s preferred time to continue the request. A wish to meet after work is useful context, but the visit still needs to be agreed. Describe that next action beside the handover, so nobody mistakes an enquiry for a confirmed appointment.
Read the same steps two ways
Chawo’s local development build shows the steps as a diagram and a synchronized list. The diagram makes a split visible; the list lets a reviewer read the questions in order. Both describe the same scenario, so a change can be checked without reconstructing the conversation from scattered notes.
Review the future AI draft
We plan AI creation from a written task, with dictation as a further input. You will describe the wardrobe enquiry and review the proposed questions and conditions with the person who handles these requests. Their knowledge of missing measurements and practical constraints will still matter when assessing the draft.
Prepare a separate trial
Choose a familiar request now for a trial when early access opens, while keeping your existing bot running. Compare one changed condition against the same example rather than rewriting everything at once. A useful first result is a clearer question or handover that your team can explain and assess.