Buzzer

Docs

How Buzzer works, a feature at a time. Each page starts with why it’s worth having and ends with everything you need to set it up.

Agents

Who does the work

  • Support AgentComing soonAnswers your customers on chat and email, from what you’ve given it.
  • BuzzerComing soonYour team’s assistant, in the app and in Slack.
  • Your own agentsComing soonAgents with their own instructions, tools and email address.
  • HandoffComing soonHow an agent knows when to stop and pass to a person.
  • AutomationsComing soonAgents that run on a schedule or when something happens.

Surfaces

Where it shows up

  • Email draftsEvery email arrives with a reply already written.
  • Email threadsComing soonReplies that land back in the right conversation.
  • Email addressesComing soonYour support address, your own domain, and agent addresses.
  • Chat widgetComing soonAnswers on your site and in your app.
  • Help centreComing soonYour articles, published and searchable.
  • SlackComing soonAsk about customers without opening Buzzer.

Context

What it knows

  • KnowledgeComing soonArticles, files and synced websites it answers from.
  • PlaybooksComing soonWhat to do in a specific situation, like a refund.
  • MemoryComing soonShort notes about a person or company, read before every reply.
  • Suggested editsComing soonGaps in your docs, spotted from real conversations.

Connectors

What it can reach

  • ConnectorsComing soonStripe, Shopify and the other apps your team uses.
  • Linear and GitHubComing soonTurn a conversation into an issue.
  • MCP serverComing soonUse Buzzer from Claude and other AI tools.
  • API and SDKsComing soonBuild on Buzzer from your own code.