The four ways teams handle replies before they buy an inbox
Forward everything to one Gmail. Keep thirty tabs open. Wire a sequencer webhook into Zapier, Slack and a Sheet. Build your own. Every one of these came up on calls this year, and every one breaks in the same places.
Free 7-day POC. Unlimited users on every plan. Bring the stack you have; we connect to it.
Four stacks, four failure points
Each one is a reasonable first move. Each one stops working at the same moment: more mailboxes, more clients, or one missed reply that cost a deal.
Thirty sending mailboxes, one master Gmail per client, twelve tabs. Threads break because the forward is a new message, prospects see odd headers, provider forwarding limits hit, and the reply you send goes out from the wrong address. One founder weighing exactly this asked whether an inbox was worth it against a forwarded Gmail. The honest answer is on this page.
Operators watching 30 to 40 inboxes each in Wavebox or plain tabs. No one knows who owes a reply, speed to lead is whatever the operator happens to notice, and DNC is a manual chore in the sequencer.
The sequencer posts a reply event, Zapier routes it to Slack and appends a Sheet row. It misses forwards, CC and new-address replies because the sequencer never saw them, it breaks on every schema change, and the Slack message has no draft and no thread. Three agencies described their Zapier or Make chains as brittle, one as the reason their client reporting kept failing.
A Telegram script, an Airtable and Claude pipeline, a Supabase inbox. One agency built its own unibox and gave it up because maintenance cost more than the tool it replaced. Another's Airtable pipeline lost the full message log.
The same five things break every time
Whichever stack you run, the calls describe the same failures. This is what an inbox built for outbound replies has to solve, and what Master Inbox does about each.
| What breaks | In the DIY stack | In Master Inbox |
|---|---|---|
| Threads | A forward is a new message. Context is lost, the prospect sees a stranger's headers, and the reply leaves from the wrong mailbox. | The mailbox is read in place. One Master Thread per prospect across every mailbox, subject line and channel, and the reply goes out through the mailbox that received it. |
| Coverage | Webhook chains only carry what the sequencer attributed. Forwards, CC and new-address replies never enter the chain. | Every mailbox is a source. Internal data puts the replies a sequencer never reports at roughly 12% of the total. |
| Who owes a reply | Nobody knows. Bold, unread and a Sheet column are the state machine. | Labels carry an obligation flag. Needs Reply, waiting on me and 48 hours silent are saved views, and the SLA clock runs on business hours. |
| Speed | Forwarding adds latency; one agency measured lower booking rates from it. Slack alerts arrive without a draft. | The Slack card carries the drafted reply and an Accept button. Reply agents answer in minutes with a human in the loop. |
| Maintenance | Every schema change breaks the Zap. Every new client means new Zaps, new Sheet tabs, new forwarding rules. | Workflows are inside the inbox on every plan. Clone a workspace for the next client. |
| Proof to clients | A monthly Notion page and a Loom, assembled by hand. | Per-workspace reporting, a scheduled view report, or forwarded positives, with no client login required. |
Is it worth it?
The forwarded Gmail is free. The missed reply is not.
A founder weighing Master Inbox against a forwarded Gmail inbox asked us that directly. It is the right question, and the answer depends on one number: what a reply is worth to you.
- One agency founder put a single reply at twelve to fifteen thousand dollars of contract value, and knew of at least one that had been missed.
- An agency that sells booked meetings, not free offers, called catching the missed replies a no-brainer for the same reason.
- Pricing is per client workspace or per mailbox with unlimited users, and it starts with a free 7-day proof of concept on your own inboxes, so the count of caught replies is yours before the invoice is.
Bring the stack. We connect to it.
Nothing you run has to be thrown away on day one.
- Zapier, Make and n8n. Keep them for what is not reply handling. An Incoming Webhook trigger and webhook actions connect the two while you move workflows across. See workflows.
- Sheets and Airtable. Tables run on live inbox data, and a Google Sheet row is still an action if a client insists on the Sheet.
- The forwarded Gmail. Connect the sending mailboxes directly and the forwarding rules can be switched off one client at a time. Forwarded duplicates are folded into the original thread meanwhile.
- Your own scripts. The API covers inbox, prospects, labels, views, workflows and workspaces, with webhooks for every event. See the API.
Explore more: Workflows, The better unibox, Missed replies, pricing
Questions we get
Why not just forward every mailbox to one Gmail?
Our sequencer webhook already posts to Slack. What is missing?
We built our own inbox. Why switch?
Can we keep Zapier for other things?
What does it cost against a free stack?
See it on your own inboxes
Book a demo and bring your current setup. We will show you which replies it is dropping, on your own inboxes.
Book a demo