Installation steps
Check what your GitBook plan supports
Review GitBook's current integrations and custom domain controls for your workspace. Do not assume that adding a script to a markdown page or custom CSS field can run JavaScript on hosted docs. Check the workspace settings for an explicitly supported app or embed before asking an administrator to change plan permissions.
Use a supported fallback
Place the widget on your marketing or app site, then add a visible support link from the GitBook navigation or relevant docs pages. This gives visitors a reliable route without relying on an unsupported script injection. In the space navigation editor, label the destination “Contact support” and use its complete HTTPS URL because the chat page is hosted outside GitBook. Add the same link near authentication and quickstart instructions where a setup problem is likely to occur.
Keep the handoff useful
Link to the specific API or troubleshooting page where possible. Test the support link and make sure the team can receive and answer the conversation in Slack, Telegram, or the web inbox. Open a published GitBook page while logged out, follow the link, and confirm it lands on the chat-enabled hostname rather than an editor preview. If the destination opens without its launcher, approve that exact origin in MivoChat Install settings → Allowed websites; if the link is hidden on mobile, check the space navigation at a narrow viewport and repeat the task from an API reference page.
Before you change the setup
workspace administrator access to review integrations, a support URL, and a clear owner for incoming conversations
GitBook's supported integrations and page links; hosted GitBook may not permit arbitrary JavaScript injection
do not promise an embedded widget unless the current GitBook plan and product expose a supported script integration
Test the support boundary
- Where is the API authentication guide?
- How can I verify a webhook signature?
- What support route is available if this page has no answer?
Frequently asked questions
A script pasted in markdown displays as text
Markdown code blocks are content, not executable page injection; link to your chat-enabled app or marketing support page instead.
A custom CSS field has no widget
CSS controls presentation rather than loading JavaScript; use a supported integration if available or publish a visible support link.
The link sends readers to a generic homepage
Point GitBook navigation to the exact support page or contact route and test it while logged out as a reader.
Visitors cannot open the linked chat
Allow the destination website's origin in Install settings → Allowed websites and verify the link target is publicly reachable.