Skip to main content
The AI Experience Builder helps you design your experience. Agentsy is where you apply that design, test it, and make it available to visitors. Before sharing your experience, review both the configuration and what visitors will actually see.

1. Review the experience brief

Confirm that you can clearly answer these questions:
  • Who is it for? Identify the primary audience and the situations in which they might use it.
  • What does it help with? Describe the questions it can answer or decisions it can help visitors understand.
  • What makes it yours? Identify the expertise, methodology, or perspective that differentiates it.
  • What should it not do? Define boundaries, including topics requiring professional judgment or current information.
  • When should a person step in? Define the moments when a visitor should speak with you or your team.
If any answer is unclear, refine your concept before configuring the assistant.

2. Review the generated configuration

Read the Builder’s proposed system instructions rather than copying them without review. Check that they cover:
  • The assistant’s role, purpose, tone, and intended audience.
  • How to respond to questions and when to ask clarifying questions.
  • How to use your methodology and available knowledge.
  • What to do when information is missing or uncertain.
  • What information must not be requested, disclosed, or invented.
  • When and how to recommend human follow-up.
System instructions guide the assistant’s behavior. They do not replace accurate reference documents or guarantee that every response will be correct.

3. Prepare and check your knowledge

Make sure the material you intend to use is ready for the experience:
  • Include current, relevant information about your services and approach.
  • Separate different subjects into clearly named documents when helpful.
  • Remove outdated, contradictory, or duplicate material.
  • Avoid uploading personal, confidential, or regulated information unless you have an appropriate, approved basis and safeguards for doing so.
  • Identify information that changes frequently, such as inventory, pricing, schedules, or regulations. Do not imply the assistant has live access unless a suitable integration is actually configured.
See Prepare your knowledge for more guidance.

4. Apply the configuration in Agentsy

Sign in to Agentsy and open the AI Experience you want to configure. Use the available settings to apply the relevant parts of your Builder output, including:
  1. Assistant identity and system instructions.
  2. Knowledge documents and retrieval settings, where available.
  3. Website content, branding, and calls to action.
  4. Visitor access and registration settings.
  5. Human follow-up options, such as a booking link, if configured.
The exact labels and available settings may vary by account and product updates. Save your changes and verify them in the visitor-facing experience.

5. Test like a real visitor

Don’t test only with ideal questions. Try realistic, incomplete, and unexpected requests.
Test on both desktop and mobile. Check the opening message, readability, links, buttons, registration flow, and the conversation itself.

6. Complete the launch review

Use this checklist before sharing your AI Experience:
  • The audience and purpose are clearly defined.
  • The assistant’s instructions have been reviewed.
  • Knowledge documents are accurate and appropriate to share.
  • The assistant handles uncertainty and out-of-scope requests well.
  • The brand, website copy, and calls to action are correct.
  • Visitor access and registration behave as intended.
  • Any booking or contact link works.
  • Privacy notices and applicable disclosures are in place.
  • Key conversation scenarios have been tested.
  • The experience works on mobile and desktop.
For a broader pre-launch review, see the Launch checklist.

7. Publish and share

Once your checks are complete, use the publishing or access controls available in your Agentsy account to make the experience accessible to the intended audience. Confirm that the visitor-facing URL works in a private browser window, especially if you expect public access. Start by sharing the experience with a small group of trusted testers or prospects. Their questions can reveal gaps in your knowledge base, confusing language, or missed opportunities for human follow-up.
Do not assume an experience is public merely because you can open it while signed in as an administrator. Test the link as a visitor without an active account session.

8. Improve after launch

Launching is the beginning of an improvement cycle. Review the conversations and engagement information available to your organization, subject to your privacy practices. Look for recurring questions, incomplete answers, and moments when visitors are ready to speak with a person. Use those observations to refine the knowledge, instructions, website messaging, and handoff process. Re-test whenever you make meaningful changes.

What’s next?

You’ve completed the AI Experience Builder journey. Continue with: The goal is not simply to launch a chatbot. It’s to create an experience that helps visitors understand your expertise and makes the next human conversation more meaningful.