1. Purpose and audience
- The experience clearly explains who it is for and what it helps them do.
- Its opening message invites a useful conversation rather than overwhelming visitors with questions.
- The assistant stays within its intended role and expertise.
- The experience makes clear what it cannot do, when relevant.
2. Assistant behavior
- System instructions reflect your approach, methodology, and tone.
- The assistant asks clarifying questions only when they help the visitor.
- Responses are understandable and useful, not unnecessarily long or promotional.
- The assistant does not invent facts, credentials, guarantees, inventory, or outcomes.
- It recognizes when a request requires a human expert or a process outside the chat.
3. Knowledge and answer quality
- Relevant documents and reference materials have been added.
- Important information is current and consistent.
- Uploaded files are readable and organized around the questions visitors are likely to ask.
- The assistant handles questions that are not covered by its knowledge without guessing.
- You have tested questions whose answers depend on your uploaded materials.
4. Website and branding
- The experience name, logo, and colors represent your brand.
- The headline and supporting text explain the benefit to visitors.
- Images look good on desktop and mobile.
- Buttons and links lead to the intended destinations.
- Contact and business information are accurate.
- If you use a custom domain, it opens correctly and securely.
5. Visitor access and registration
- You have selected the intended access mode, such as public or invite-only, where available.
- You have tested the visitor experience in a private or incognito browser window.
- Any guest-chat or registration steps behave as intended.
- Visitors understand when they need to create an account or sign in.
- The experience does not unintentionally expose private content.
6. Human follow-up
- Visitors have a clear next step when they want to speak with you or your team.
- Any scheduling, contact, or call-to-action links have been tested.
- The assistant knows when to suggest a human conversation without pushing visitors too early.
- The assistant does not claim a meeting has been booked, a request has been submitted, or a person has been notified unless that action actually occurred.
Agentsy is designed to create better human conversations—not to replace every human interaction. A good handoff helps an interested visitor move forward with context and confidence.
7. Privacy and expectations
- Your privacy notice and other applicable disclosures are available where needed.
- Visitors are not encouraged to share passwords, payment-card details, medical information, or other sensitive data in ordinary chat.
- The assistant accurately describes its role as AI rather than pretending to be a person.
- Any industry-specific legal, professional, or compliance requirements have been reviewed by the appropriate person.
- You understand who can access conversations and visitor information in your organization.
8. Final conversation tests
Before publishing, test the experience as if you were a new visitor. Use at least these five scenarios:
Repeat your most important tests on desktop and mobile. If you change system instructions or knowledge after testing, retest the affected scenarios.
9. Publish and review
Once the essential checks above are complete:- Confirm that your AI Experience is configured for the audience you intend to reach.
- Open its visitor-facing website and test it one last time.
- Share the link with a small group of trusted users or prospects.
- Review their questions and feedback to identify unclear instructions or missing knowledge.
- Improve the experience incrementally as you learn what visitors need.
Ready to launch: Visitors understand the experience, receive dependable guidance, and have a clear next step when they want human help.

