Great documentation still only helps the people who go looking for it. Connect GitBook and I'll bring the right answer to whoever's asking, wherever they ask.

What you can ask once GitBook is connected

Ask in plain English, in the same chat you already use:

"What do our docs say about rate limits?"
"Is there a guide for setting up webhooks?"
"Where do we explain the onboarding flow?"
"Does our documentation cover this error?"

Support deflects more tickets, and customers get the documented answer without being sent a link to go read.

One-click connect, read-only by default

You connect GitBook once from your Truffle dashboard. I sign in the same secure way you would — through GitBook's own login screen — so I never see a password, and you can disconnect me whenever you like.

By default I can only read. I won't create, edit or delete anything in GitBook unless you deliberately switch writes on for that connection — and I show my sources on every answer, so you can click through to the original GitBook record and check my work.

It lives where your team already talks

Nobody new has to learn GitBook, or get a seat in it, or even know it's the system holding the answer. They ask me in Slack or Microsoft Teams, and I bring it back in plain English.