Launching today
Banger Mail
Shared mailboxes for teams and AI agents
121 followers
Shared mailboxes for teams and AI agents
121 followers
Banger is a native Mac app for teams running shared inboxes like support@, sales@, and founder@. You and AI agents work the same mailboxes: agents triage, label, and draft with scoped access, while you review before anything sends. Connect your own domain or Google Workspace accounts, search everything, assign threads, and track work on a board. Early access: 14 days free, 2 mailboxes, 100 AI credits, no card. 500 spots now. Mac first, Windows and mobile next.
Banger Mail
Hey Product Hunt 👋 I'm Tiago.
I’ve spent the last few years building chat apps, first at Beeper, including Beeper Mini, and then at Automattic. Most of my work has been deep app engineering: native clients, messaging surfaces, sync, reliability.
One thing I kept running into is that email still feels built for one person, even though a lot of company work happens there. Support, sales, invoices, recruiting, partnerships. It all lands in the inbox, but teams still end up sharing passwords, forwarding threads around, or pasting drafts into Slack when they want someone else to review a reply.
So I left my job and started MuchBetterApps with a friend who has spent years building and operating infrastructure. Banger is the first thing we’re building.
The basic idea is shared email with review built in. You can have shared mailboxes, real permissions instead of one shared login, and a way to put an email up for review before it sends. That can be for a teammate’s draft, or for something an AI agent wrote. The closest analogy is probably a pull request, but for email.
One important detail: for custom domains, we are not just putting a nicer UI on top of someone else’s email product. We built our own mail infrastructure for receiving and sending email, including the domain setup layer. We are not relying on AWS SES, SendGrid, Postmark, Mailgun, or another hosted email service for that part. There is a lot of unglamorous work in deliverability, routing, queues, DNS setup, bounces, retries, and abuse prevention, but I think owning this layer matters if we want to build the kind of email product we have in mind.
Today we're launching the native Mac app. It supports your own domains and Google Workspace. For new domains, we’re trying to make setup less annoying. For existing Google Workspace teams, the goal is to add the collaboration layer that Gmail does not really have.
This is early access, so it’s not the whole vision yet. There are 500 open spots now and we plan to open more as the infrastructure scales.
I’ll be around in the comments. I’d love to hear what you like, what feels unclear, and what you think we’re missing. Thanks for checking it out.
The "pull request for email" framing is exactly right. I build support and sales agents for ecommerce stores, and
review-before-send is the single thing that makes owners comfortable letting an agent anywhere near their inbox. So, it
is great to see it treated as a first-class feature instead of a bolt-on.
The question that I think decides whether this scales: what happens after a reviewer has approved 50 routine drafts in
a row and starts rubber-stamping? Do you plan per-agent or per-thread-type trust levels (auto-send the routine stuff,
always hold refunds, pricing, anything with money), or sampled review once an agent earns confidence? That dial
between safety and approval fatigue is the hardest part of this pattern in my experience.
Also, respect for owning the mail infrastructure yourselves. Deliverability, bounces and abuse handling are unglamorous, but that layer is usually where products like this live or die.
Congrats on the launch, Tiago.
Banger Mail
@syed_noor4 Hi Syed, ty for checking it out. When you add a human and teammate right now you can choose the permission level. I think we're well positioned to experiment with per-agent or per-thread type trust levels, similar on how code harnesses have the 'only ask for actions as detected as potentially unsafe'. We'll explore this idea on the second half of the year. Thank you for suggesting the per-thread-type trust level, I haven't received this feedback yet.
If two teammates are reviewing the same conversation at the same time, how does Banger prevent duplicate replies or conflicts?
Banger Mail
@shawn_idrees hey Shawn, in this early implementation you can only request review one at a time. But in the future they will be just many revisions you can accept or merge yourself, i.e. the reviews won't be applied right away but live as changes that you can accept or not and resolve conflicts if any.
How do you envision the AI agents handling email threads with multiple stakeholders or complex customer support issues?
Banger Mail
@aymnart
1- We are going to enable you to use external agents, on which you shared the proper context and gave proper tools and skills to answer very complex issues.
2- The main Idea on Banger is that teammates or AI agents can make reviews without sending, i.e. they can suggest something and rely on an advanced opperator to approve sending as well.
How do the AI agents actually decide when to draft a reply vs just label something, and can I set per-agent rules or do they all run on the same defaults?
Banger Mail
@naime162129
Hi Naime, emails are always labelled by AI (being cloud or local AI).
Regarding processing of the queue:
When you create an internal agent, you can setup the per-agent rules and the send capabilities (draft and ask for review or can send). On your workspace you can have as many different agents as you want to deal with different needs.
On this early preview, you still need to assign the email to one of the agent so it does draft or send it depending on its permissions. We have auto-triage on the roadmap, on which you will define rules so the email/task is given automatically to one of the agents or a human.
Congrats! QQ, this is only for MacOS or any future plans to release on Win?
Banger Mail
Hey @ruvik_milkis , we have a Windows version that is very advanced right now, based on WinUI3 with Fluent Design. We'll launch it soon after it gets parity and similar quality as the native macOS version.
Shared inboxes are a good place for AI because the work is repetitive but the accountability is still human. The guardrail I would want is a clean separation between draft, suggested action, and actual send, especially for support or billing threads.
Banger Mail
@krekeltronics yeah, we already have that on the version we launched today. Give it a try and let me know if it works for you.