Skip to Content
Getting StartedLaunch Checklist

Launch Checklist

Run this checklist on the actual production website, not only in AI Demo.

Knowledge

  • The pages that answer your most common questions are active.
  • Old, duplicate, private, and irrelevant pages are disabled or removed.
  • Uploaded files show as active and contain selectable, readable text.
  • Important policies have one current, unambiguous source.

Answers and behaviour

  • Ten real customer questions have been tested, including paraphrases.
  • Missing-information questions produce an honest limitation instead of a guess.
  • A visitor prompt-injection attempt does not override the agent’s role or source boundaries.
  • Suggested questions represent useful starting points, not marketing slogans.
  • Tone and handoff instructions match how your team actually works.

Safety and privacy

  • Every production and staging hostname that needs the widget is allowed.
  • A request from an unlisted hostname is rejected.
  • Lead capture asks only for information your team needs and is entitled to collect.
  • Workspace members and admins have been reviewed.
  • No secret API keys or credentials have been placed in prompts, FAQs, or website content.

Publishing

  • The widget script is installed once in the shared site layout.
  • The launcher works on desktop and mobile.
  • A live chat appears in Conversations with the correct page context.

Ownership

  • One person owns answer quality and source updates.
  • Someone will review negative feedback and low-confidence conversations.
  • The team knows who replies to escalated conversations and within what timeframe.
  • Lead alerts and the weekly digest are configured for the right recipients.

Final live test

  1. Open the production site in a private window.
  2. Ask two related questions and confirm they stay in one conversation.
  3. Submit the lead form and confirm the contact appears in Engine 64.
  4. If lead-capture handoff is enabled, confirm the conversation is marked Escalated and a team member can reply.