# Introducing Banger: company email your AI runs Canonical URL: https://bangermail.com/blog/introducing-banger-mail/ Banger is company email your AI runs. Your assistant sets up your domain, creates mailboxes, prepares product email, and operates Broadcasts and Journeys through an MCP server. Your software connects through an API. You review consequential work in the Banger web app. The agent cannot approve Banger Approvals. We built this for the solo builder launching a product on a fresh domain. The same assistant helping you write the product can help establish its email operation. You provide the product facts, audience, and decisions; Banger provides the email tools and the place to review their results. ## One product's email, from the beginning A launch starts with a small set of concrete needs. You want an address people can reply to. Your software needs to send account messages. People who subscribed to updates expect an announcement. New subscribers may need a short introduction over several emails. Those jobs share a company identity, but they are not interchangeable. A password reset has a different purpose from a newsletter. A subscribed contact is different from an address that simply appears in your records. A drafted sequence is different from a live one. Banger gives an agent tools for those distinct jobs within your company email operation. It covers domain setup, mailboxes, product and transactional email, Broadcasts, Journeys, contacts and consent, signup forms, delivery status, and logs. The company behind the product is BangerMail Inc. The product is Banger. This launch post describes Banger as it stands on September 28, 2026, following our August 13 pivot. ## How it works ### 1. Connect the assistant you already use Start with the [Banger MCP guide](/banger-mcp/). The remote server is **https://api.bangermail.com/mcp**, with OAuth and dynamic client registration. Connect from ChatGPT, Claude, Codex, Cursor, or another MCP client and review the scopes you grant. Add Banger as a connector or custom connector using the server URL, then complete OAuth. The [ChatGPT guide](/blog/how-to-send-email-from-chatgpt/) and [Claude guide](/blog/how-to-send-email-from-claude/) walk through the starting workflow. ### 2. Establish the company's sender identity Tell the agent which domain belongs to the product and what mailbox you need first. Ask it to prepare the DNS setup and explain any action required from the domain owner. SPF, DKIM, DMARC, and MX each have a role; setup is complete only when the relevant configuration is verified and ready. Publishing records depends on the available DNS access. Banger can guide the process, and the agent should give you the exact records or supported publishing path. It should not assume it can change any registrar account merely because it knows the domain name. ### 3. Prepare the first useful email For a first session, choose one message and one recipient you control. Have the agent prepare the sender, subject, and content. Inspect the result, proceed under your workspace's policy, and check the delivery status. Then move to the product's actual requirements. Application-triggered account messages belong in product email. A launch newsletter belongs in a Broadcast. A timed introduction can become a Journey. Our guide to [transactional and marketing email](/blog/transactional-vs-marketing-email/) explains that distinction. ![An agent, company email hub, and review card connect domain setup, contacts, and email sequences.](/assets/blog/introducing-banger-mail/inner.webp) ### 4. Review before consequential work goes live Journey activation requires an Approval that a person decides in the web app. Sends that workspace policy gates also become Approvals. The agent can prepare the work and explain what is waiting; it cannot approve. Use that review to check the full operation. Check the sender, recipients, copy, links, and timing. For a sequence, read every step. An agent's ability to build a workflow does not make it the right judge of whether that workflow should contact your customers. ### 5. Check results Ask for delivery status and logs after sending. Investigate holds and refusals before retrying. Keep contacts and consent current, and respect suppressions instead of asking the assistant to route around them. Your application can use the [API reference](/docs/api/) for software-driven email while the assistant helps operate the surrounding setup. The web app remains the place for human review. These are three ways to work with the same product. ## Start small, with clear limits Inboxes are free and unlimited on every plan. Free includes 3,000 emails a month, up to 100 a day. Sends beyond Free's daily cap go out the next day, so plan a launch around when messages will actually leave. Paid plans refuse sends beyond their monthly allowance until renewal or upgrade. There are no overage or usage fees. See [pricing](/pricing/) for current allowances, storage, and billing options before choosing a plan for your expected volume. A mailbox count is not a sending allowance. Creating separate addresses for support and product notices can help clarify identity, but it does not create extra capacity or an exception to policy. Plan around the whole company's operation. ## Consent belongs in the launch plan Bring an audience that agreed to hear from you. Banger's signup forms use double opt-in by default. When contacts are added as subscribed through an import, API, or MCP, consent must be confirmed; a Broadcast cannot be released to subscribed contacts without confirmed consent. Hard bounces, complaints, and unsubscribes are suppressed across the workspace. Marketing messages need an honest sender identity and the required company footer. Read the [acceptable-use policy](/acceptable-use/) before importing contacts or scheduling announcements. For a useful first launch brief, tell your assistant: “Set up email for this product, prepare a welcome message for confirmed subscribers, and show me every outstanding setup step and Approval.” You can then work through actual decisions instead of an undefined request to automate everything. ## FAQ ### Who is Banger for? Banger is for solo builders launching a product on a fresh domain who want their AI assistant to set up and run company email, with a web app for human review. ### Which AI assistant can I connect? ChatGPT, Claude, Codex, Cursor, and other MCP clients can connect through Banger MCP. Follow the setup guide and complete the client's authorization flow. ### Can I use Banger from my application? Yes. Banger has an API for software integrations, including product email. MCP serves the assistant workflow, while the API serves explicit application integrations. ### Does the agent have final approval authority? No. A person decides Journey activations and policy-gated sends in Banger's Approvals. The agent prepares and operates within its granted permissions.