Prove the replies were worked, without building a report by hand
Leadership wants to know two things: what came back and what the team did about it. Most teams answer that with a spreadsheet and a Loom once a month. Master Inbox answers it from live workspace data, on a schedule, in Slack, or in a login scoped to one team.
Book a call See pricingUnlimited users on every plan, never priced per seat.
How does leadership see that every reply was worked?
Three ways, picked per audience: forwarded positives and a scheduled report with no login, a Slack channel, or a login that stays in its lane. Most executives will not learn a new tool, so none of these asks them to.
A workflow forwards each interested reply to its owner, last message only. A scheduled view report sends the week's positives as one email.
Interested and meeting-request replies post to the channel with the drafted answer. Leadership sees the replies that matter and nothing else.
A member invited into one workspace sees that inbox, its labels and its reports, and nothing from other teams.
The four numbers a pipeline review needs
Computed per workspace from live data, so the monthly review is a filter, not a project.
Of every reply that needed an answer, the share that got one. Resolved obligations over total obligations.
Of every prospect who came into play, the share that turned positive. Effort and result side by side.
Average first response and total response, against the SLA and business hours you set for the team.
Booked through Cal.com, Calendly, Chili Piper, GoHighLevel, Google Calendar or HubSpot, attributed to the workspace and the rep.
Missed replies are on the same screen. The honest number is the one that gets fixed; the hidden one is the deal that went quiet.
What teams told us on calls
Paraphrased, names left out.
- Obligations, not vanity metrics. An in-house team running 250 mailboxes wanted to see who owed a reply, not how many emails were sent.
- Present every lead without forcing a login. One team's reporting broke whenever its Zapier and Drive chain did, and it still needed every lead in front of the people who own the deals.
- Only the interesting ones. Teams wanted owners notified for interested and meeting-request replies and nothing else, so nobody asks about every out-of-office.
- Response speed by rep, by channel. Sales leads wanted throughput, labels and adherence to process per rep, to hold every SDR to the same standard.
- The monthly review, without the Notion page. One team assembled a Notion page and a Loom every month by hand. Tables and the scheduled view report replace both.
Set it up once per team
Then clone the workspace for the next one.
Workspace and SLA
One workspace per team with its timezone, business hours and the response time you promised. Workspaces.
Views and channel
A positives-only view, a Needs Reply view for your reps, and the leadership Slack channel wired to the Interested label. Workflows.
Report and review
The scheduled view report goes out weekly. Reporting and Tables carry the monthly review. Reporting.
Explore more: Workspaces, Reporting, Master Inbox for RevOps, Workflows
Questions we get
Can leadership get reports without logging in?
Can I show only the positive replies?
Can one team see another team's replies?
Our agency runs outbound for us. Can it report from here?
How do I run the monthly review?
See it on your own inboxes
Book a call and we will set up the scheduled report and the Slack channel your leadership will actually read.
Book a call