Tired of messy shared logins for support@? Banger Mail brings Git-like Pull Requests and AI-driven drafts to your team inbox with human-in-the-loop approvals.
Is your team’s support@ or sales@ inbox a complete dumpster fire? Sharing passwords, forwarding threads like it’s 1999, or copying drafts to Slack for a sanity check because you don't trust the new intern? Today, let's look at Banger Mail, a fresh utility hot off the Product Hunt press that wants to turn your shared mailboxes into a Git-like repository complete with AI helpers and built-in "Pull Requests."
The brain behind this project is Tiago, a veteran dev who previously built chat apps at Beeper (yes, including that Beeper Mini iMessage reverse-engineering stunt) and Automattic. After years of deep app engineering, he noticed a glaring problem: email is fundamentally designed for one person, yet a massive chunk of startup collaboration happens in shared aliases.
Fed up with the hacky workarounds, he quit his job and co-founded MuchBetterApps to build Banger. Here’s the core feature set of this native macOS client:
Currently, Banger is operating a native Mac client with 500 early-access slots available, while Windows and mobile builds are in the pipeline.
The dev community immediately picked up on the "Git for Email" framing.
Most seasoned engineers expressed massive respect for the decision to run their own mail servers. One user noted: "I appreciate that you built your own email infrastructure instead of just adding another interface on top of existing services. That is a much bigger undertaking than most people realize."
However, a highly practical concern raised by an e-commerce AI tools developer hit the nail on the head regarding "approval fatigue":
"The question that 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 routine stuff, always hold refunds)?"
Tiago welcomed the feedback and confirmed that they plan to experiment with per-thread-type trust levels and confidence metrics later this year to avoid burning out human reviewers.
Another user jokingly asked how the system prevents duplicate replies or conflicts if two agents or team members review the same thread simultaneously. Tiago clarified that while the early beta limits reviews to one person at a time, the roadmap includes true Git-like revision merging.
Let’s face it: treating email collaboration like code review is a stroke of pragmatic genius. It directly addresses the biggest barrier preventing businesses from adopting generative AI in customer service: the fear of a rogue hallucinating chatbot ruinously firing off an email to a valuable client.
Two key takeaways for us devs:
Does your team still handle support emails using stone-age techniques? Would a Git-style approval system save your sanity? Let us know in the comments!
Source: Product Hunt
