# Banger: the agentic email system for your entire company Canonical URL: https://bangermail.com/ Language: English Reference updated: 2026-09-29 > Create mailboxes, send transactional email, and run marketing campaigns automatically. ## Run all your email on autopilot with AI agents. Create mailboxes, send transactional email, and run marketing campaigns automatically. ## Who is Banger for? ### SaaS & App Builders Turn signups into active users. Build welcome Journeys, announce new features with Broadcasts, and stay close to users through your Mailboxes. ### Ecommerce Turn first purchases into repeat customers. Send timely order updates, build cart recovery Journeys, and personalize your next product drop. ### Marketing Professionals Go from campaign idea to Broadcast in a conversation. Tailor messages to each audience, learn from the results, and make the next send better. ### Automation Teams Help companies bring their email together. Audit the existing setup, connect scattered inboxes and tools, and build automated workflows across Mailboxes, Journeys, and Broadcasts. ## Example agent workflows These are example requests from the landing page. Workflows involving external systems require the corresponding integrations and permissions. - Set up billing@, send a test receipt, and confirm it was delivered. - Wire the signup event to a welcome sequence and preview the first email. - Turn this changelog into a launch campaign. - Summarize the replies, find churn risk, and draft the right follow-up. - When an invoice is past due, send a recovery sequence and alert finance if the customer replies. - Find trial accounts that stopped using the product and create a win-back campaign. - Compare campaign traffic with signups in Google Analytics and draft the next experiment. - Recover abandoned carts with a timed sequence, then stop it the moment an order lands. - Send booking confirmations and reminders from success@, with replies in the shared inbox. - Route qualified form submissions to the right owner and send a personalized introduction. - Turn this Figma campaign into a responsive launch email and subject variants. - Escalate unresolved support conversations, open engineering tasks, and keep customers updated. - When a VIP ticket breaches its SLA, notify support and draft the customer follow-up. - When a launch milestone slips in Linear, email the stakeholders from projects@ and collect replies there. - Query the warehouse for dormant enterprise accounts and create a safe reactivation segment. - Detect users who missed activation and send the next best onboarding message. - Replace auth emails with branded templates and monitor delivery from day one. - When a production deploy fails, email the incident list and post the same status in Slack. - Turn this launch brief into a campaign, audience, and subject variants. - Send every new booking a tailored prep email and put replies in the right mailbox. ## Product reference Banger combines company mailboxes, transactional email, lifecycle Journeys, and marketing Broadcasts in one system. Agents operate through MCP and programmatic interfaces; people use the visual web app at https://app.bangermail.com/ to inspect, edit, review, and take over. Banger does not currently offer standalone Banger desktop or mobile apps. ### Workspaces and products A workspace is the access boundary. Products organize individual businesses, stores, brands, newsletters, or applications within it. Agents can list products, create or update a product, read company context, and inspect setup progress. Select the intended product before changing its content, domains, audience, or sending configuration. When several products exist, write operations need an unambiguous product target. ### Company mailboxes and shared inbox work Create native mailboxes on connected domains, inspect existing provider connections, list mailboxes and threads, read message bodies, search mail, and retrieve workspace work queues. Agents can summarize conversations, prepare replies, send from a selected mailbox, and mutate thread state. Labels and triage rules help organize incoming work: preview a rule, enable or disable it, apply it to past mail, inspect its actions, and undo supported triage changes. The mailbox is a real sending identity. Mail sent through a mailbox uses its actual address; it is not silently rewritten to a product's transactional subdomain. Inbound replies and outbound work remain available to the team in the web app. ### Domains and sending infrastructure Native domain tools create and inspect sending domains, provide verification state, verify required DNS records, and inspect domain activation proofs. Product-domain setup and migration workflows connect domains to the right product. Teams can inspect sending health and pause or resume sending lanes when necessary. A starter-mailbox flow supports onboarding and verification before a full domain setup. These authenticated infrastructure capabilities are part of Banger. They are separate from the retired public website domain-checker tool. ### Transactional and product email Send receipts, sign-in messages, alerts, confirmations, and other product notifications through the API or an agent. The email tool accepts recipient lists, subject, HTML or text, optional template/content inputs, and an idempotency key. Read the specific tool signature for required mailbox and reply-to fields. A successful submission is not proof of delivery. Inspect send records and delivery status to distinguish accepted, queued, delivered, bounced, or failed work. Banger applies identity readiness, suppression, allowance, and policy checks. Free or cancelled paid accounts can have a small “Sent with Banger” line added at delivery; paid plans remove that line, including for queued messages. ### Journeys and lifecycle automation Journeys connect product events and audience activity to email sequences. Use them for welcome, activation, nurture, reminders, retention, and win-back flows. Agents can create or register a keyed Journey, inspect and update its definition, preview and render messages, simulate execution, manage status, enroll contacts, and inspect executions. Managed API Journeys are the default for new registration. They carry source-language HTML, typed variables, and sample values; Banger prepares additional languages asynchronously. Existing code Journeys remain supported. A draft does not send anything. A Journey's first activation requires a human review of its sending setup. Subsequent execution remains bounded by the reviewed scope and saved policies. ### Marketing Broadcasts Broadcasts cover newsletters, launches, announcements, and other audience sends. Agents can create and update drafts, preview audiences, check readiness, schedule or send, and inspect recipients and timeline events. Pause, resume, cancel, archive, and delete operations have distinct meanings and should be selected intentionally. Before sending, inspect the actual audience, rendered content, sender, exclusions, schedule, and readiness result. A saved draft, an audience preview, and a scheduled send are different states. Agents and people work on the same product objects rather than maintaining separate copies of a campaign. ### Contacts, lists, segments, and imports Maintain contacts and custom fields, manage contact lists and list membership, and build reusable segments. Preview a segment to understand whom a rule selects before attaching it to a Broadcast or Journey. Contact import tools support mapping proposals, validation, import requests, and status inspection. Contact records and eligibility rules inform targeting; appearing in a list does not override suppression or sending policy. ### Signup forms Build inline forms, popups, bars, slide-ins, or hosted signup experiences. Forms can define fields and consent settings, with popup triggers such as delay, scrolling, and exit intent. Preview a form before using it and manage the form against its intended product and audience workflow. Creating a form is distinct from activating an email Journey for its subscribers. ### Brand, templates, assets, and visual design Read the saved brand before designing email. Reuse its colors, typography, tone, and footer details. Create, update, duplicate, and preview templates; generate or revise email designs; upload email images and assets; and render previews for review in a supported agent host. An unsaved design preview saves and sends nothing. Review the actual rendering and sample variables, then revise it before scheduling or activating the associated workflow. Tool results can provide preview artifacts or links when a client cannot display an embedded preview. ### Managed content, localization, and shared layouts Managed content separates editable email content from the application code that triggers it. Create and update content, render it with variables, inspect translations, review translated content, publish revisions, and restore earlier revisions. Product content settings govern localization behavior. Shared layouts provide reusable email structure. Inspect versions, preview approvals, and assess impact before publishing a layout that other content uses. Publishing content or a layout is a separate operation from editing a draft; inspect the affected messages and returned publication state. ### Experiments Test two to four variants of a subject, design, content, or from-name. Broadcasts can test on a sample first and send the winning variant to the remaining audience. Journey steps and automations can split continuously. Supported outcome signals include human-only opens, clicks, replies, and Journey goals. Agents can inspect experiments, recommend arms, decide or stop experiments, and manage split decisions. Automatic decisions use minimum samples and a confidence threshold; a configured deadline can promote the current leader even when the confidence threshold was not reached. Inspect the decision basis when interpreting a result. ### Communication policy and deliverability Product-wide policies coordinate recipient frequency caps, message spacing, and delivery windows across Journeys and Broadcasts. A read-only simulation can show how fixed requests would be scheduled without sending or reserving slots. Policy updates use concurrency checks. Urgent messages can bypass frequency caps, but not delivery suppression or expiry. Health and deliverability tools expose sending state, recent hard bounces and complaints, logs, and delivery outcomes. Suppression, unsubscribe handling, domain readiness, limits, and freeze state constrain execution independently of what an agent asks to do. ### Connections and incoming webhooks Inspect available connections, confirm setup, and query an authorized connection to use relevant business data in an email workflow. Incoming webhooks create an endpoint and durable connection that a Journey can reference. Inspect webhook state, test integrations, and check receipt evidence before treating the integration as working. Credentials are handled through private setup panels where supported, or the Banger web app. Creating an incoming webhook does not activate a Journey or prove that an event arrived. Webhook creation is not idempotent: repeating it can create another endpoint. Secret URLs and bearer tokens belong in the sending application's secure configuration. ### Permissions, review, and human control OAuth grants and API keys scope access to a workspace and permitted operations. Agents can inspect connected agents and API keys; authorized users can revoke access. The server enforces authorization independently of the language model. A tool being described in this document does not guarantee it is available to every connection. Current action behavior allows draft and send operations to execute directly under the applicable policy; the first Journey activation requires human review. Stricter saved policies still apply. Do not assume that every send waits for approval, or that an agent can bypass a required review. Read readiness, policy, approval, and execution results for the concrete action. ### Billing and support Billing tools report the current plan, usage, sending allowances, storage, and available pricing, and can open upgrade or billing-management flows. Use those live results and the pricing page for current limits rather than relying on fixed numbers in this reference. Agents can submit feedback, report a bug, suggest a feature, and attach supporting material through the corresponding tools. ## Agent access and developer interfaces The remote MCP endpoint is `https://api.bangermail.com/mcp`. Connect through a supported Banger integration, authorize the intended workspace, and grant the required scopes. The [client setup guide](https://bangermail.com/banger-mcp/) covers Claude, Claude Code, ChatGPT, Codex, and other MCP clients. Clients such as Cursor, Hermes, and OpenClaw need compatible remote MCP and authentication support; setup and embedded UI support vary by client. Use MCP for agent-driven discovery and operations, the HTTP API for application integration, and the CLI/SDK surfaces where available in your environment. This documentation does not imply that an internal package name is publicly installable. - [All 191 MCP tools and typed inputs](https://bangermail.com/mcp.md) - [API authentication, examples, and transport](https://bangermail.com/api.md) - [MCP client setup](https://bangermail.com/banger-mcp/) - [Complete product, API, and MCP reference in one file](https://bangermail.com/llms-full.txt) ## Open source: Bangerverse Bangerverse is Banger's open-source home for companion apps, integrations, and email templates. Fork a project, customize it with your agent, contribute an improvement, or use its integration contract to build something new. - [Pulse](https://github.com/bangermail/bangerverse/tree/main/apps/pulse): a beta desktop companion for macOS, Windows, and Linux with watched-mailbox alerts and one-time-code copying. It keeps a short recent-alert list in memory and does not store email bodies. Pulse is a companion project, not a standalone Banger desktop email app. - [mailG](https://github.com/bangermail/bangerverse/tree/main/apps/mailg): a beta Gmail-style web inbox for reading, composing, labeling, starring, and archiving Banger mail. Fork and customize the UI; check the project's README for current authentication and rollout requirements. - [Email templates](https://github.com/bangermail/bangerverse/tree/main/templates): 70 templates across eight styles, with briefs and responsive, email-safe HTML that can be adapted to a brand's colors and fonts. - [Integration contract](https://github.com/bangermail/bangerverse/blob/main/docs/integration-contract.md): guidance for applications built around Banger. - [Repository and contributions](https://github.com/bangermail/bangerverse) - [License](https://github.com/bangermail/bangerverse/blob/main/LICENSE): MIT unless a project specifies otherwise. Bangerverse contains open-source projects around Banger. It does not contain the hosted Banger server or the complete hosted web application. ## Documentation scope This product reference was assembled on 2026-09-29 from the landing-page source, Banger's connected MCP tool catalog, repository integration documentation, and the public Bangerverse README. Availability depends on workspace access, permissions, product setup, plan, and client support. The live MCP catalog and operation responses take precedence over this static snapshot. Canonical site: https://bangermail.com/ Web app: https://app.bangermail.com/ Pricing: https://bangermail.com/pricing/ Trust and security: https://bangermail.com/trust/ Privacy: https://bangermail.com/privacy/ Terms: https://bangermail.com/terms/ Contact: hello@team.bangermail.com ## Frequently asked questions ### Does Banger handle both inbound and outbound work email? Yes. Banger keeps inbound and outbound in one system. The inbox reply stays connected to the transactional send, lifecycle flow, or campaign that started the conversation, sharing context, identity, deliverability, and control. ### How does Banger achieve best-in-class deliverability? Deliverability is a core part of Banger. We are deliverability experts, and we built proprietary checks for authentication, domain health and reputation, bounces, complaints, suppression, unsubscribes, and sending limits. You get expert guidance and guardrails even if deliverability is not your specialty. ### Can agents use Banger from Claude Code, Cursor, ChatGPT, Hermes, or OpenClaw? Yes. CLI, MCP, SDK, and API give agents a stable interface to read, prepare, and operate email inside the permissions you define. ### Does Banger have a public API, SDK, webhooks, and MCP? Yes. The platform is built to be integrated by developers and operated by agents, with API, SDK, CLI, webhooks, and MCP as surfaces of the same system. ### Can I use Banger for transactional and marketing email? Yes. Connect company domains once, create mailboxes for teams, workflows, projects, customer queues, or agents, send sign-in codes, receipts, alerts, onboarding, and notifications by API, automate welcome, nurture, activation, retention, and winback from events, and run newsletters, launches, announcements, segments, and performance analysis. ### Is Banger headless, or can my team manage email in a visual app? Agents work through MCP, SDK, or API, and your team can use the same visual web app. Read and reply to email, edit templates and campaigns, manage audiences, and track delivery across your company mailboxes. ### Is my email content used to train models? No. Banger does not sell your data or use your email content to train models. Personally identifiable information (PII) is removed before any call to an AI provider. ### Who decides what an agent can access? You do. Access is scoped by workspace, mailbox, and action. An agent can draft for support@ without seeing founders@ or receiving permission to send. ## Run all your email on autopilot with AI agents. Plug in your domains. Let Banger handle what happens next. [Open Banger](https://app.bangermail.com/) · [Pricing](https://bangermail.com/pricing/) · [AI-readable index](https://bangermail.com/llms.txt)