Add live chat to GitBook. DeskCrew support widget
GitBook published sites allow no custom scripts, so DeskCrew installs beside GitBook. The widget on your main site, the help center linked from your docs.
One paste on GitBook
One script tag. No build step, no package to maintain, nothing that can break on a platform update. The exact steps are below.
AI drafts, humans approve
The AI drafts replies grounded in the knowledge base you publish, and every draft waits in an approval queue until a human sends it.
Every conversation is a ticket
Widget chats, emails, and board posts land in one dashboard with full history; visitors who leave get their answer by email.
Free plan, no card
The free plan includes the chat widget, a public knowledge base, and ticketing. Start free and upgrade only when you outgrow it.
How to install DeskCrew on GitBook
GitBook doesn’t allow custom code (HTML, CSS, or JS) on published sites, on any plan, so no third-party chat widget can load inside GitBook-hosted pages.
Install DeskCrew on your main website instead: paste the snippet below into its <head> (the Next.js, Astro, Nuxt, and static-site guides have the exact one-liner).
Then link your DeskCrew help center and board from your GitBook site’s navigation or pages, so readers reach support in one click.
<script src="https://deskcrew.io/desk.js" data-key="pub_YOUR_KEY" data-board="your-board" defer></script>
pub_YOUR_KEY and your-board are placeholders. Your real widget key and board slug are in your DeskCrew dashboard under Install (free signup, no card).
Note: The snippet below is for your main site, not GitBook. GitBook accepts no third-party scripts on published sites. That’s a GitBook platform restriction, not a plan tier.
DeskCrew vs the usual suspects
| DeskCrew | Tidio | Crisp | Zendesk | |
|---|---|---|---|---|
| Free tier | Yes. Free plan, no card | Yes (limited) | Yes (basic) | Free trial only |
| AI included | Yes. AI drafts on every plan, human-approved | Paid add-on | Higher plans | Paid add-on |
| Setup | About 2 minutes. One script tag or plugin | Minutes. Script tag | Minutes. Script tag | Longer. Full workspace setup |
| Price floor | $0 free plan · paid from $29/mo | Free plan; paid tiers above | Free plan; paid tiers above | Per-agent pricing, no free plan |
Competitor cells generalize their public pricing pages. Always check current plans.
DeskCrew has a free plan with no card. Chat widget, public knowledge base, and ticketing included. Every new workspace starts with full Team features free for 14 days, and paid plans start at $29/mo. Full details on the pricing page.
FAQ. add live chat to GitBook
Can I add a live chat widget to a GitBook site?
Not by pasting code. GitBook doesn’t support editing HTML, CSS, or JavaScript on published sites, on any plan. Chat tools only get in through GitBook’s own marketplace integrations; arbitrary scripts like a widget tag aren’t possible.
Does any GitBook plan allow custom scripts?
No. The restriction is platform-wide, not plan-gated. GitBook’s help center states custom code (CSS, HTML, or JS) can’t be inserted into a GitBook site.
How do I offer support to my GitBook readers then?
Two working paths: install the DeskCrew widget on the main website your docs belong to, and link your hosted DeskCrew help center and feedback board from your GitBook navigation, both are one click away for readers.
Can DeskCrew still answer questions about my documented product?
Yes. Publish the answers you want automated into your DeskCrew knowledge base (your GitBook stays the deep reference), and the AI drafts replies grounded in what you publish there, with a human approving each one.
Is the DeskCrew widget free?
Yes. DeskCrew’s free plan includes the chat widget, a public knowledge base, and ticketing, no card required.
Where do my readers’ tickets go?
Every conversation, from the widget on your main site or your public board, becomes a ticket in your DeskCrew dashboard. The AI drafts a reply grounded in your knowledge base, and a human approves it before it is sent.