Custom agents
Buzz answers customers. Custom agents do everything around that: they watch for events, run on a schedule, read what Buzz reads, and write to the tools you already use — with the same guardrails.
Events in the inbox, a schedule, or a webhook from anywhere. The agent gets the thing that woke it — the conversation, the message, the payload — as context.
Knowledge, memory, past conversations, and any connector with an MCP server. A tool preset — read-only, internal writes, or publish — sets the ceiling; you pick per tool.
Articles, files, playbooks and tools are gated by segments, server-side. An agent working a customer’s thread sees exactly what that customer is allowed to see.
Gallery
Watches your releases channel and drafts the help-centre changes before anyone asks.
When a thread closes, keeps what was new — about the customer, and about the product.
Files the ask with product, dedupes against what’s already there, and links the customer.
When the linked issue closes, lists everyone who asked and drafts the outreach.
Anything that publishes, spends, or emails a customer waits for a person unless you say otherwise.
Every step is logged with what it read and what it wrote, in the same timeline you see on a Buzz reply.
What one agent learns about a customer, Buzz and your team see on the next thread.
Output lands as drafts, notes, and threads — nowhere your team isn’t already looking.
Custom agents talk to your team and your tools. Only Buzz talks to customers.
Anything with an MCP server is a tool. Anything with a webhook is a trigger.
Lloyd Humphreys
Founder, Buzzer
Tell us the thing your team does by hand every week. We’ll build the agent on the call.
Book 30 minutes with Lloyd