Knowledge base
Docs that fix themselves.
Buzz spots what’s wrong, and suggests the edit.
A help centre, an internal wiki and Buzz’s source of truth, in one place. Every change is a version. Every article knows who it’s for.
Self-healing
The docs learn from the inbox.
When three customers hit the same gap, Buzz notices. It drafts the edit, shows the diff, and tells you which threads made it think so. You accept, tweak, or dismiss.
Suggestions, not surprises
Nothing publishes itself. Every proposed change is a diff with a reason attached.
Buzz can write, too
Ask it in a thread — “turn this into an article” — and a draft appears, cited to the conversation.
Closes the loop
Accept an edit and the next customer with that question gets the right answer, from Buzz or from search.
Retries run for 24 hours with exponential backoff.
Failed deliveries are dropped after that.
After 24 hours the batch is paused, not dropped — replay it from Settings → Webhooks.
Behind a proxy, allow-list hooks.usebuzzer.com or retries time out.
Version control
Every change is a version.
Edits are collaborative and live — several people in one article, no lock, no overwrite. Behind that, every publish is a version you can diff and roll back to.
Multiplayer editing
Cursors, presence, and no “someone else is editing” lock.
Diff and rollback
See exactly what changed between any two versions. Restore one in a click.
Drafts stay drafts
A broken draft can’t go live — publishing validates the article first.
- v14Live
Proxy timeout fix
Buzz · Today, 09:12
- v13
Reworded intro
Grace · Mon
- v12
Added backoff table
Buzz · 12 Aug
- v11
First published
Ada · 3 Aug
Audience & language
Each article knows who it’s for.
Public, internal, or restricted to a segment — the same article can be all three in different languages. Buzz, search and the help centre all respect it, so an enterprise runbook never leaks into a public answer.
Translations
Write once, publish in every language you support. Buzz answers in the customer’s.
Segment-scoped
Restrict an article to a segment and it only exists for those people — in the help centre, the widget and Buzz.
Fail closed
If a restriction can’t be resolved, the article is staff-only. Never accidentally public.
- EN · DE · FR · ES
Getting started
Public
- EN · DE
SSO with Okta
Segment: Enterprise
- EN
Refund escalation
Staff only
Bring what you have
Start with the docs you already wrote.
Point it at your existing help centre, upload files, or pull straight from Zendesk, Help Scout or Intercom. Formatting survives; links get rewritten; nothing is lost.
Crawl a site
Give it a URL and it walks the sitemap.
Files
Markdown, HTML, Word — converted, not pasted.
Searchable on day one
Imported content is indexed for Buzz and for the widget immediately.
- 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, not dropped — replay it from Settings → Webhooks.
Behind a proxy, allow-list hooks.usebuzzer.com or retries time out.
And the rest.
The parts a help centre should just have.
Hosted help centre
Your docs on your domain, rendered fast at the edge.
Search everywhere
The help centre, the widget, and Buzz all search the same index.
Collections & nesting
Group articles however your product is shaped.
Files as knowledge
PDFs and docs Buzz can read but customers never see.
Cited answers
Buzz 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
Bring your help centre. We’ll import it live.
Thirty minutes. Watch Buzz answer from your own docs, and watch it find the first thing they get wrong.
Book 30 minutes with Lloyd