Publish chatbot guide
Prepare a tested education chatbot for live sharing with clear route, readiness, and troubleshooting checks.
What publishing means
Publishing makes a chatbot ready for the public live chat experience after you have configured it, tested it in preview, and confirmed it should be available to users. A live chatbot should be active before you share its public link.
Preview mode vs live mode
- Preview mode uses /chat/preview for authenticated creator or stakeholder testing before launch.
- Live mode uses /chat/live for public access to active chatbots only.
- Do not use a legacy /chat route or query-string mode switch for chat experiences; the mode belongs in the pathname.
Preconditions before publishing
Chatbot status
Confirm the chatbot is ready to be active before sharing it. Public live access should only serve active chatbots.
Public live route checks
Confirm that public traffic uses /chat/live and that visitors can start without authentication when intended.
Authenticated preview checks
Use /chat/preview for internal QA and stakeholder review flows that require authentication before access.
Credit and balance readiness
Check that the workspace has enough AI Credits for the usage you expect after launch. Avoid publishing if you already know usage cannot be supported.
Knowledge file readiness
Make sure knowledge packs contain current, approved files and that old versions or drafts have been removed.
Model and reasoning validation
Re-test the selected model and reasoning settings in preview after major prompt or knowledge changes.
Publish workflow
1) Finish the create guide checklist
Confirm persona, welcome message, model settings, and knowledge packs are ready before treating the chatbot as launchable.
2) Validate preview conversations
Test expected questions, edge cases, and unsafe or out-of-scope prompts on the authenticated preview route.
3) Confirm readiness blockers
Check status, credit or balance readiness, knowledge-file quality, and model or reasoning validation before publishing.
4) Publish and verify active availability
After publishing, verify that the chatbot is active and that the live route opens the intended public experience.
5) Share the live chatbot link
Share the /chat/live link only after live verification. Use surrounding page copy or onboarding text to explain what the chatbot can and cannot help with.
6) Monitor and improve
Review early conversations, update knowledge packs, and refine persona instructions when users ask recurring unanswered questions.
If publishing or live access fails
Publishing fails
Re-check required chatbot fields, active/readiness state, balance readiness, model settings, and whether knowledge files are still processing or need cleanup.
Live chatbot is unavailable
Confirm the chatbot is active, the shared link uses /chat/live, and the chatbot has not been unpublished or restricted by workspace configuration.
Live answers differ from expectations
Return to preview with the same examples, then adjust persona instructions, source files, or model/reasoning settings before re-sharing widely.
Privacy and data questions
For formal privacy details, review the Privacy Policy rather than relying on informal guide copy.
Pre-publish checklist
- Chatbot is set to active before sharing the public live route.
- Core user questions are answered accurately and consistently in preview.
- Out-of-scope and sensitive prompts trigger safe fallback behavior.
- Team members know where to track usage, quality trends, and user-reported issues.
Publishing starts the improvement loop. Use early traffic to prioritize practical updates.