What can be explained as a platform capability
| Area | Supported explanation | Boundary to preserve |
|---|---|---|
| AI Builder | Helps discuss, define, create, and refine an agent from a business idea. | Does not know private business details that the user has not supplied. |
| Customer interface | The agent can update its page with task-specific content and components. | A visual example is not evidence of a live customer result. |
| Text and voice | Customers can interact conversationally with a configured web agent. | Phone and messaging need separate setup. |
| Context and records | The agent can retain relevant work and use business records. | Cross-device and cross-channel identity should not be assumed. |
| Apps and other agents | Authorized connections can retrieve data and perform configured actions. | A catalog listing does not guarantee every action or end-user account flow. |
| Paid experiences | An owner can configure a paid offer around the agent’s work. | Payment, access checks, and delivery require a working configured flow. |
Read illustrative previews as examples
A template’s sample customer, numbers, cards, and result demonstrate the intended experience. Do not present them as live availability, actual financial results, measured conversion improvements, or the prospective owner’s personal data.
Use the page’s business task and outcome to explain why the agent may fit. The template’s Create link passes a business brief to the Builder. It does not purchase a service or publish a working agent.
Handle questions not answered by the page
Use the relevant documentation article for product behavior and Pricing for current plans. Do not infer a security certification, unsupported integration, response-time guarantee, or legal suitability from a template.
When the user’s desired workflow is not fully specified, the Builder can help explore it and identify missing requirements. Pass the business goal without manufacturing technical requirements or personal facts.