AI knowledge base
A knowledge base that stays up to date.
Buzzer spots what’s out of date and suggests a fix.
Your help centre, your internal wiki and the knowledge the Support Agent answers from, all in one place. Every change is saved as a version, and you choose who can see each article.
Suggested edits
Your inbox keeps the docs up to date.
When a few customers run into the same gap, Buzzer notices. It drafts an edit, shows you what would change and links the conversations that prompted it. You can accept it, tweak it or dismiss it.
Nothing goes live without you
Every suggestion comes with the changes marked and a reason for them.
Buzzer can write, too
Ask it to “turn this into an article” in a thread and you’ll get a draft that links back to the conversation.
Fixed for next time
Once you accept an edit, the next customer who asks gets the right answer, from the Support Agent or from search.
Retries run for 24 hours with exponential backoff.
Failed deliveries are dropped after that.
After 24 hours the batch is paused, and you can replay it from Settings → Webhooks.
Behind a proxy, allow-list hooks.usebuzzer.com or retries time out.
Version control
Every change is saved.
Several people can edit the same article at once without overwriting each other. Each time you publish, a new version is saved that you can compare or roll back to.
Edit together
See each other’s cursors, with no “someone else is editing” lock.
Compare and roll back
See what changed between any two versions and restore one with a click.
Drafts stay drafts
Articles are checked before they publish, so a broken draft can’t go live.
- v14Live
Proxy timeout fix
Buzzer · Today, 09:12
- v13
Reworded intro
Grace · Mon
- v12
Added backoff table
Buzzer · 12 Aug
- v11
First published
Ada · 3 Aug
Audience & language
Choose who sees each article.
Articles can be public, internal or limited to a segment, and each language version can have its own setting. The Support Agent, search and the help centre all follow it, so an enterprise runbook won’t turn up in a public answer.
Translations
Write an article once and publish it in every language you support. The Support Agent replies in the customer’s language.
Limited to a segment
Restrict an article to a segment and only those people can see it, in the help centre, the widget and the Support Agent’s answers.
Safe by default
If a restriction can’t be worked out, the article is treated as staff-only, so it won’t end up public by accident.
- EN · DE · FR · ES
Getting started
Public
- EN · DE
SSO with Okta
Segment: Enterprise
- EN
Refund escalation
Staff only
Import
Start with the docs you already have.
Point it at your existing help centre, upload files, or import straight from Zendesk, Help Scout or Intercom. Formatting is kept and links are updated to match.
Crawl a site
Give it a URL and it follows your sitemap.
Files
Markdown, HTML and Word files are converted properly, formatting included.
Searchable straight away
Imported content is indexed for the Support Agent and the widget right away.
- Imported
help.acme.com
Website · 212 pages
- Imported
Zendesk Guide
84 articles
- Imported
Onboarding.docx
File
- Importing…
Notion · Runbooks
Internal · 31 pages
Retries run for 24 hours with exponential backoff.
Failed deliveries are dropped after that.
After 24 hours the batch is paused, and you can replay it from Settings → Webhooks.
Behind a proxy, allow-list hooks.usebuzzer.com or retries time out.
Everything else you’d expect
Hosted help centre
Your docs on your own domain, fast wherever your customers are.
Search everywhere
The help centre, the widget, and the Support Agent all search the same index.
Collections & nesting
Group articles however your product is shaped.
Files as knowledge
PDFs and docs the Support Agent can read but customers never see.
Cited answers
The Support Agent links the article it used, so customers can read more.
Internal wiki
Playbooks and runbooks for your team, next to the public docs.
Lloyd Humphreys
Founder, Buzzer
We’ll import your help centre on the call.
You’ll see the Support Agent answer questions from your own docs, and Buzzer will probably spot the first thing in them that needs fixing.
Book 30 minutes with Lloyd