support@ lands in the same inbox.
Threads stay threads. Buzz drafts the reply before you open it.
Forward your support address and every email becomes a conversation next to chat — same queue, same customer record, same Buzz.
Receive
Forward it. Done.
One forwarding rule from your existing address and mail starts arriving as conversations. Replies go back out from your address, so customers never see ours.
Your address, both ways
Receive at support@you.com, reply as support@you.com.
Loops and noise filtered
Out-of-office bounces, auto-replies and duplicates never reach the queue.
Same customer, same record
An email from elena@globex.com joins the Elena who chats through the widget.
- Forwarding verified
- Replies sent as support@acme.com
- Auto-replies and loops filtered
Threads
Shown like email, because it is.
Email conversations look different in the inbox on purpose: the latest messages open, the older ones collapsed to a line, attachments where you’d expect them. No quoted-reply soup.
Collapses like a mail client
The last few messages stay open; the rest fold to a single line each.
Attachments stay attached
PDFs, images and inline screenshots, stored with the thread and readable by Buzz.
Original kept
Every raw email is archived, so nothing is lost in rendering.
Dan Okafor· Re: Seats on the Q2 invoice- DanHi — the invoice shows 40 seats but our contract…12 Aug
- GraceThanks Dan, looking into this now.12 Aug
- DanAny update? Finance is asking.14 Aug
Following up — attached the signed agreement. Section 4.2 caps us at 25 seats for the year. Can you credit the difference?
Buzz drafts
The reply is waiting when you get there.
Email is slower than chat, so Buzz uses the time. Every inbound email gets a draft — grounded in your docs, the customer’s account and the attachments — for a person to send, edit or discard. It never sends email on its own.
Reads the attachments
The signed contract in the PDF is part of the answer.
Yours to send
A draft, not a reply. Edit a word or the whole thing; it goes when you say.
Signature included
Your team signature is appended to every outbound reply, automatically.
To Dan Okafor · from support@acme.com
Hi Dan,
Thanks for the agreement — you’re right, section 4.2 caps the account at 25 seats. I’ve asked billing to credit the 15 extra seats on the Q2 invoice; you’ll see the adjusted invoice within two business days.
Sorry for the back-and-forth.
Grace
Compose
One composer. It knows it’s email.
The same box you reply to chat with — saved replies, help-article links, @-mentions, internal notes — with one extra line on email threads: exactly where this reply is going and what address it leaves from.
No wrong-address surprises
Recipient and sender are shown above the box, every time.
Saved replies and articles
Type / for a saved reply, # to link a help article.
Notes stay internal
Switch to Note and it never leaves the building — amber, so you can’t mistake it.
- Forwarding verified
- Replies sent as support@acme.com
- Auto-replies and loops filtered
Email, handled properly.
The boring parts, done.
Threading that holds
Replies join the right conversation, even weeks later.
Rate-limited ingest
A misconfigured script can’t flood your queue.
Inline images
Screenshots pasted into an email show up in the thread, not as attachments.
Classified on arrival
Topic, urgency and mood, tagged before anyone opens it.
Labels and assignment
Route billing emails to billing. Same rules as chat.
One queue
Email, chat and Slack in one list, sorted by what needs you.
Lloyd Humphreys
Founder, Buzzer
Forward one email. Watch the draft appear.
Thirty minutes. Bring a real support email and we’ll run it through end to end.
Book 30 minutes with Lloyd