Smartlead's built-in inbox, and Master Inbox.
Smartlead's inbox is a tab inside Smartlead: the replies to campaigns it sent, in the workspace you are looking at. Master Inbox is a standalone product that reads every mailbox you send from, in every workspace and every tool, and works the replies. Most teams run both.
Free 7-day POC. Unlimited users on every plan. Smartlead stays your sending tool.
What Smartlead's tab does well
Credit where it is due. For one workspace, running campaigns from Smartlead alone, the tab is fine.
Every reply to a Smartlead campaign shows up next to the campaign that earned it, with the lead's status a click away.
Interested, meeting booked, not interested and the rest, plus canned replies, without leaving the sending tool.
A solo operator or a single in-house team sending from one workspace can live in it.
The trouble starts when replies arrive that Smartlead did not send for, or when there is more than one workspace.
Six replies the tab never shows you
Every one of these came up on a sales call in the last six months. None is a Smartlead bug. The tab can only show what Smartlead sent for.
Your prospect forwards the email to a colleague, who replies from their own address. Smartlead has no campaign for that address, so the reply is not a reply.
Master Inbox: reads the mailbox, threads it to the original prospectThe prospect adds their assistant, or answers from a second account. Same conversation, different sender, invisible to campaign attribution.
Master Inbox: one Master Thread per prospect, whoever writesReplies to the reply-to address on your main domain land in a mailbox Smartlead is not tracking. One in-house team found their reply capture and analytics both broke this way.
Master Inbox: connect that mailbox too, it is just another channelA prospect answers three weeks after the sequence ended, to a step that is no longer active. Agencies running ten Reply or Smartlead workspaces told us these are the ones they lose.
Master Inbox: a reply is a reply, sequence or no sequenceA mailbox drops out of rotation or loses its connection. Replies keep arriving in it. Nothing downstream of the sequencer knows.
Master Inbox: an email_disconnected event, and a reply agent that keeps readingSmartlead to webhook to Zapier to Slack is how most teams hear about a reply. Each hop drops the cases above, and the message in Slack has no draft and no thread.
Master Inbox: a Slack card with the drafted reply and an Accept buttonInternal data across connected workspaces puts the replies a sequencer never reports at roughly 12% of the total. The forward and the new address are most of it. How to count yours.
"You're telling me that all these native platforms, like Smartlead, Instantly, EmailBison, they just miss replies?"Adrian B., agency founder, on a demo call. His team booked from every reply because they sold meetings, not free offers.
Fine at one workspace. Not at twenty.
Agencies do not have a Smartlead inbox. They have twenty of them, one per client, each behind a workspace switch.
- No queue across clients. An inbox manager covering ten workspaces opens ten tabs and asks each one who owes a reply. One agency asked us, straight out, whether there was a master inbox or whether managers had to keep switching. That question is the product.
- Views stop at the workspace. Needs Reply, waiting on me, no reply in 48 hours: Master Inbox runs these across every workspace with the client name on each row, or scoped to one client for a client login.
- Labels stay local. Smartlead categories live in Smartlead. Master Inbox labels are applied by AI on your own key, sync back to Smartlead both ways, and drive views, workflows, reporting and reply agents.
- Reporting counts campaigns, not people. Smartlead reports on sends and reply rates. Master Inbox reports on obligations: who owes a reply, how long it waited, per rep and per client, against the SLA you set.
Side by side
What each one sees and does. Smartlead's own docs describe the tab; the Master Inbox column is what ships today.
| Smartlead's inbox | Master Inbox | |
|---|---|---|
| Replies it sees | Replies to Smartlead campaigns, from the address the campaign wrote to | Every reply in every connected mailbox, including forwards, CC, new addresses and replies after the sequence ended |
| Channels | Email plus LinkedIn from HeyReach, Expandi, Aimfox and native seats, threaded per prospect | |
| Workspaces | One at a time | All at once, or scoped per client for a client login |
| Labels | Smartlead categories | AI labels on your own key, custom taxonomy, synced back to Smartlead both ways |
| Views | Per workspace, per campaign | Needs Reply, waiting on me, 48 hours silent, per client, per rep, saved and shared |
| Automation | Webhooks out to your own tools | Workflows inside: Slack card with draft and Accept button, HubSpot sync, remove from or pause the Smartlead campaign, reminders, forwards, webhooks |
| Answering | Manual, quick replies | Manual, from Slack, from HubSpot, or reply agents with human-in-the-loop, booking on Cal.com, Calendly, Chili Piper, GoHighLevel, Google Calendar or HubSpot |
| Reporting | Sends, opens, reply rates per campaign | Reply coverage, missed replies, response times per rep and per client against an SLA with business hours |
| Client access | A Smartlead client login | A workspace-scoped login, forwarded positives, or a scheduled view report with no login |
| Pricing model | Included with Smartlead | Per client workspace or per mailbox, unlimited users, free 7-day POC |
Keep Smartlead. Add Master Inbox.
Nothing about your sending changes. Three steps on the first call.
Connect
Smartlead by API key or OAuth, plus the mailboxes themselves, in bulk from Zapmail, InboxKit or HyperTide or by CSV. Account-level webhooks act as a second safety net.
Label and sync
AI labeling backfills history on your own key. Label sync runs both ways, and you choose which labels are allowed to push back into Smartlead.
Automate the hand-offs
Meeting booked removes the prospect from the campaign. Not interested unsubscribes everywhere. Interested lands in the client's Slack channel with a draft.
Smartlead stays the sending tool for a reason: unlimited mailboxes, rotation and warm-up are its job. Reply handling is ours.
What Smartlead teams told us on calls
Paraphrased from six months of demos and onboarding calls, with names left out.
- A three-SDR team found replies showing in Smartlead but nowhere downstream whenever a mailbox rotated, and wanted alerts on rotation and disconnects.
- An in-house team's replies to their main reply-to domain never registered in Smartlead, breaking both capture and analytics.
- A PE-focused agency had operators watching 30 to 40 inboxes each in browser tabs, with forwarding chains breaking threads and hitting provider limits.
- An agency asked for exact label parity with Smartlead, plus DNC and booked rules, so reporting would not drift between the two tools.
- Several agencies wanted the meeting-booked event to pause or remove the prospect from the Smartlead campaign automatically. That is one workflow now.
- More than one team's Slack feed came from Smartlead webhooks and was described as messy, with no way to reply from it.
Explore more: Smartlead + Master Inbox, Smartlead alternative, Smartlead integration, Missed replies
Questions we get
Is Master Inbox the same as the inbox in Smartlead?
Does Master Inbox replace Smartlead?
Do labels sync both ways?
Does it read the mailbox or the Smartlead webhook?
What about warm-up emails?
What does it cost next to Smartlead?
See it on your own inboxes
Book a demo and we connect your Smartlead workspace live, then count the replies the tab never showed you.
Book a demo