Three connected messages sit inside a graphite tray under a glass cover.

Guides

Review a scenario without messaging a customer.

What a local conversation review can tell you, and where the prepared example ends.

Chawo is preparing for launch. We are taking early-access requests; AI and channel connections are not available yet.

Request early accessRead the security boundaries

Separate the scenario and the channel

Before changing a customer conversation, separate its questions and decisions from the channel that delivers messages. A prepared example lets a team discuss the route without presenting it as a live bot. For a wardrobe enquiry, the first useful check is whether missing dimensions lead to a measurement request.

Prepared example data connects to a local message tray, apart from the source records.
A local review uses prepared examples, separate from production data.

Know the source of the example

Chawo’s local development build reads prepared redacted or synthetic records on one computer; it is not open for public download. The build has no production database access or live messaging connection. For a new example, enough detail means the customer’s task and relevant constraints, without their actual contact details.

Do not mistake a record for an action

The wardrobe example can show a branch for missing dimensions and a recorded handover. It does not arrange a real visit or notify a designer, even if the text describes those next steps. When discussing the example, distinguish the customer’s preferred evening from the appointment that still needs confirmation.

Know what resets

Local analytics compares the prepared records, with its in-memory view returning to those records on restart. It is therefore unsuitable as a report of current sales activity. A review can explain why an example followed a branch, while claims about actual appointments need evidence from the system handling them.

Understand the local boundary

The local process accepts requests from the same computer through loopback. This boundary belongs to the development build, rather than defining every future Chawo deployment. The planned hosted service will need operator authentication and separation between organisations, which are not part of this local build.

Request access deliberately

Use the early-access request to hear when access opens; it records an email without uploading conversations or creating a product account. You can prepare a synthetic enquiry now and note what the team wants to check. Keep the existing customer process in place while deciding what a later trial should cover.