The model coordinates the customer experience
The model interprets what the person wants, decides what information is missing, and uses available tools when the task needs data or an action. The page presents the relevant state of that work, such as a set of options, a calculation, or an editable plan.
The Builder creates the experience and its available capabilities. The published agent then operates within that configured experience. Updating the page during a visit does not mean the agent is rebuilding or republishing its application for every message.
What can change during a visit
- The questions and choices shown for the customer’s situation.
- Tables, summaries, cards, charts, files, and other relevant results.
- A calculation or plan after the customer changes a requirement.
- The next available action based on information collected so far.
A revised renovation estimate
A homeowner asks to keep the existing cabinets and spend more on the countertop. The agent uses the configured estimating rules to revise the scope and preliminary total on the page. The result explains the change, rather than leaving the homeowner to combine a chat answer with an outdated estimate.
Design the result and its limits
Tell the Builder what a useful customer result should contain and how it should look. The agent can use your branding and task-specific components. A floating text or voice input lets the visitor continue while working with the result.
A live price, booking, or external update requires the relevant connection and successful action. A generated result alone is not evidence that a reservation was made or a payment was collected.