One workspace per team. Each team sees only theirs.
Give each team, region, brand or product line its own mailboxes, LinkedIn accounts, labels, members, timezone and limits. Clone a workspace to launch the next one, scope each login to its own workspace, and keep a leadership view across all of them at once.
Book a call See pricingUnlimited users on every plan, never priced per seat.
What does a workspace contain?
Its own mailboxes, LinkedIn accounts, labels, members, timezone and limits, and nothing from any other workspace. What should stay separate between teams lives inside the workspace. What should be shared lives above it.
Connected per workspace, with limits per workspace, so one region's 300 mailboxes never crowd another team's view.
Each team or brand can run its own taxonomy, its own prompt and its own AI settings.
Managers across many workspaces; each team's reps inside their own.
Needs Reply for this team, the team's Slack channel, its HubSpot pipeline.
Business hours per workspace, so the SLA clock matches the team's region, not head office.
Coverage, response times and meetings booked, per workspace, ready for the weekly pipeline review.
Three ways people see their replies
Not everyone who needs a reply works in an inbox all day: account executives, founders, the owner of a brand. So there are three levels.
A workflow forwards each interested reply to the owner's inbox, last message only, and a scheduled view report sends the week's positives. See workflows.
Interested and meeting-request replies post to the team's Slack channel with the drafted answer. Nothing else does.
A member invited into one workspace sees that inbox, its labels and its reports, and nothing from the other teams.
Launching the next team
Clone, connect, go
Clone a workspace and the labels, views, lists, exclusions and AI settings come with it. Connect the team's mailboxes, in bulk from Zapmail, InboxKit or HyperTide or by CSV, and the first replies are labeled the same afternoon.
Workspace defaults carry your standard workflows, reply agents and webhooks into each new workspace.
The leadership view
Managers should not switch workspaces to find out who owes a reply.
- All workspaces, one queue. A manager covering three regions works one Needs Reply view across all of them, with the workspace name on every row.
- Per-rep accountability. Reporting shows response times, coverage and missed replies per rep across workspaces, on the same SLA rules.
- Limits you set. Mailboxes, LinkedIn accounts and members per workspace, so no team can quietly connect 200 more inboxes.
- Partners run one per customer. If an agency runs your outbound as a Master Inbox partner, it works inside your workspace and you keep ownership. Find a partner.
Explore more: Master Inbox for outbound teams, Reporting, Workflows, Master Inbox partners
Questions we get
Can a rep log in and see only their team's replies?
Can people get replies without logging in?
How are workspaces priced?
Can I clone a workspace for a new team?
Can each team run a different sequencer?
Can an agency run a workspace for us?
See it on your own inboxes
Book a call and we will set up your first two workspaces live, including a scoped login.
Book a call