Skip to main content
A demo agent can answer questions and help visitors find relevant product information and demos. Start with a narrow job and a clear handoff to a person. The quality of its answers depends on the instructions, sources, and actions you make available—not just its greeting.

Define the job

Write down who the agent helps, the questions it should answer, and what it should do when it cannot answer. For example, a fictional product team might ask an agent to explain the order workflow and surface the relevant demo; it should offer a human follow-up when the question requires account-specific advice. Gather approved, current sources for that job. Avoid adding private customer information or internal-only material to an agent intended for public visitors. Decide which actions, if any, it should be able to take and who owns those connections.

Create a draft

  1. Open Agents and choose New agent, or start from a template that fits the job. Follow the setup prompts and review the resulting draft.
  2. In Profile, review the agent’s identity and instructions. Make its purpose, boundaries, and handoff expectations clear.
  3. In Knowledge, add the sources it needs. Check that processing finishes and that the source is relevant and current. See Manage agent knowledge.
  4. Review Trust and any configured Actions. Give the agent only the capabilities and information it needs for its job. Some features depend on your workspace and plan.

Test before publishing

Use Try it to converse with the current draft. Ask a normal question, a vague question, one that should be answered from a source, and one that should be handed to a person. Check the answer, any surfaced content, and whether the agent stays within its stated boundaries. Restart the test to check the opening experience again.
Test chats are not counted in conversations, analytics, or leads, and do not send follow-ups or notifications. However, actions the agent takes—such as booking a meeting, updating a CRM, or calling your API—can run for real. Use safe test data and review connected actions before testing.
Where available, use Tests to keep repeatable cases for important behavior. Re-run them after changing instructions, sources, or actions. See Test an agent before launch for a starter test set and the different test types.

Publish and check the visitor experience

Use Publish after reviewing readiness. Under Share & embed, choose the channel and follow its setup instructions. A website widget must be published before it can load for visitors; see Put an agent on your website for installation and host restrictions. Test the actual published destination in a separate session, including the greeting, a representative question, any relevant demo, and the human handoff. Review Conversations and Analytics after launch. Investigate unanswered questions and stale material, update the draft, and publish the reviewed changes. For server-side integrations, see the Demo agent API.