Manage replies from every mailbox in one inbox
Connect Gmail, Outlook or cPanel accounts over IMAP. Rules and a model label each thread, and AI drafts wait for your approval.
Want to see it first? Book a demo
- 90 days of history on first sync
- Rules first, model second
- Unlimited seats on every plan
The short answer
- SalesCrew pulls replies from every connected mailbox into one unified inbox. Each thread sits on the contact record it belongs to, next to that contact's deals and cadence, so you never hunt across accounts for a reply.
- Rules classify first because they are free and explainable. A model labels only what the rules missed, and it applies a label without acting on the thread.
- Draft with AI writes a reply into the composer for you to edit and send. The SalesCrew Inbox agent sweeps the inbox every 15 minutes and parks its drafts in the approval queue.
- A reply pauses that contact's cadence, and an unsubscribe or a bounce writes to suppression. Both run on their own by default.
Why replies go missing across many mailboxes
When you run outbound on ten or forty mailboxes, replies scatter. Each one lives in a different login, and the person who owns the deal rarely owns the mailbox that caught the answer. A yes can sit unread for two days.
SalesCrew fixes this by keeping the reply where the work is. The thread lands on the contact, the cadence stops, and the label tells you whether to act now. Seats are unlimited, so every rep and assistant works the same queue without a licence count deciding who sees what.
What happens to one reply
From the moment it arrives to the moment someone answers it.
- 1
Mail arrives over IMAP
Gmail, Outlook and cPanel mailboxes sync into one thread list. The first sync brings in 90 days of history, and nothing is moved or deleted in the mailbox itself.
- 2
Rules label it first
Pattern rules you write assign a category. Out-of-office replies, unsubscribe requests, bounces and vendor noise are the easy wins, and they cost nothing to run.
- 3
A model labels the rest
Threads no rule matched get a model label, such as interested. It's a filter for your attention, so read the thread before you treat it as a verdict.
- 4
Automatic consequences fire
An unsubscribe or a bounce writes to suppression. A reply pauses the cadence for that contact. You'd want both every time, so both run in auto.
- 5
A draft gets written
Click Draft with AI and a reply appears in the composer, ready for you to edit. Or let the Inbox agent draft on its sweep and queue the draft for review.
- 6
A person sends it
You approve the queued draft, or reject it with a reason that feeds the agent's next run. Every send and every decision goes to the audit log with the actor named.
What you configure
Six settings, and why each one is there.
| Setting | What you set | Why |
|---|---|---|
| Mailboxes | IMAP and SMTP details per account, with credentials held in the vault | One queue only works when every mailbox is in it |
| History window | Days of mail to backfill on first sync; 90 by default | Open conversations arrive with their context |
| Categories | Regex rules and the label each one applies | Deterministic and free to run, so they go first |
| Model fallback | On or off, and the model class | It labels the leftovers, which keeps AI cost in proportion |
| SLA and snooze | Response targets and snooze behaviour | Overdue threads stand out before they go cold |
| Inbox agent mode | Off, draft, review or auto | Review keeps every outgoing reply behind a person |
What you control
Sending stays with you. Any external send is review in the default policy table, and the Inbox agent follows it. You move the agent to auto only when you choose to, and a draft below its confidence threshold falls back to review even then.
Access follows your roles. A person or an MCP token sees the channels, profiles and areas they're scoped to, and nothing past them. So a client's assistant can triage that client's mailboxes without reading anyone else's.
Questions
- How do I manage replies from many cold email inboxes in one place?
- Connect each mailbox to SalesCrew over IMAP and SMTP. Replies from every account land in one unified inbox, threaded on the contact they belong to. Rules label them, a model labels what the rules miss, and a reply pauses that contact's cadence.
- Do old emails come across when I connect a mailbox?
- Yes. The first sync backfills the last 90 days of the mailbox's INBOX folder, and you can change that window per mailbox. Later syncs pick up new mail as it arrives.
- Can the Inbox agent send a reply on its own?
- Only if you move it to auto. You switch the agent on from the Agents page and pick its mode: draft, review or auto. In review, every draft waits in the approval queue, and the kill switch stops every agent at once.
- Why do rules run before the model?
- A rule is free and you can read why it fired. Out-of-office replies, unsubscribe requests and bounces match a pattern every time, so the model only labels the threads a rule could not place.
- Which plan includes the unified inbox?
- Every plan. Core at $299 a month includes the inbox, Draft with AI and unlimited seats, so your whole team works one queue.
Put every reply in one queue
The unified inbox is part of Core at $299 a month, with unlimited seats.
Want to see it first? Book a demo