Inbox
One inbox for every channel
Email, LinkedIn, WhatsApp, texting, X, Reddit, Slack and website chat land in the same queue, in order.
Most days the work is not in one place. A reply comes by email, the follow-up comes by WhatsApp, and the person you actually need answers on LinkedIn. The Inbox puts all of it in one list, in order, and a reply goes back out on the channel it came in on.
The channels
Email from Gmail or Outlook. LinkedIn through the extension. WhatsApp from a paired phone. iMessage and texts through the Mac, or the business number. X and Reddit DMs. Slack shared channels. Website chat from the widget. Each is a lane, and All is all of them.
How it behaves
- Linked to records
- Every conversation is tied to the person and company it belongs to, so opening a thread shows the history behind it.
- Replies go back the same way
- Reply to a WhatsApp and it is a WhatsApp. Reply to an email and it threads.
- Who is waiting on whom
- Filter to threads waiting on you, or waiting on them. The first is your morning.
- Tags and status
- Tag a conversation to build a queue. Set a status to hand it to a teammate.
- The side panel
- Open a thread beside the list, or send it to the panel and keep moving through the rest.
- Always-show senders
- People who matter never fall under a filter.
Reading and replying
- The thread on the right, the person’s record one click away, their Catch me up above the composer.
- Reply, forward, schedule, or hand it to the assistant to draft.
- Templates and snippets in the composer, with merge fields already resolved for this person.
- Mark read, archive, star, label. Gmail sees the same.
People and companies lanes
Two more lanes group the queue by who, not by channel: every conversation with a person, across channels, in one thread; and every conversation at a company. A deal’s worth of talk in one scroll.
Around inbox
The parts of the workspace this one works with.
Connect your email
Gmail or Outlook, in one sign-in. Mail syncs in and threads attach themselves to the right people.
Email is the first thing to connect. Almost everything else gets better once it is in: the timeline on a record, the daily brief, sequence stats, support tickets, even receipt parsing in Finance.
Scan a QR code and your chats sync in. Send, receive, react, quote, groups, and WhatsApp steps in sequences.
WhatsApp is where half the world does business. Pair your phone once and your chats are a lane in the Inbox: read, reply, react, and let sequences send from the same number.
Texting
One surface, three ways out: iMessage or a personal text through your Mac, or a business number.
You message a person. The app picks how it physically goes out: an iMessage from your Mac, a personal text relayed through your Mac, or a business text from the workspace number. The person sees one conversation either way.
Slack
Slack threads in the Inbox, linked to people. Notifications to a channel. Tickets mirrored so the team can reply from either side.
Slack is three things here. Shared channels with customers become conversations in the Inbox. Notifications go to the channel you pick. And tickets mirror both ways, so the team replies from Slack and the customer hears back on the channel they wrote on.
Schedule a message
Any channel, any time. A queue you can review, reschedule or cancel before it fires.
An email, a LinkedIn message or a text can go out tomorrow at nine instead of now. It sits in a queue until then, and the queue is a page you can read, reorder and cancel from.
Email signatures
One or several, HTML or plain, chosen per mailbox. The editor is the same one docs use.
A signature is written once and goes out on every email you send from here, including the ones a sequence sends for you. Keep several and pick one per mailbox.
Questions
Is it real time?+
Email, WhatsApp, Slack and website chat arrive as they land. LinkedIn, X and Reddit are pulled through your session, on open and on a schedule.
Can two people work the same inbox?+
Yes. Assign a status, tag a queue, and both see the thread move.
What about a thread with someone not in Records?+
It shows under All. Add them as a person from the thread and it attaches.
Does it read all my mail?+
It syncs the mailbox you connect so threads can attach to records. Only mail with someone in your records shows on a record page, and personal threads stay in the Inbox under you.
Can I disconnect later?+
Yes. Disconnecting stops the sync. What has already synced stays on the records it belongs to.
What about a shared inbox like sales@?+
Connect it as its own mailbox. Pick it as the default sender, or pin it to the sequences that should send from it.
Does my phone need to be on?+
WhatsApp needs the phone to have been online recently. It does not need to be next to you.
WhatsApp Business API?+
Not needed. Pairing uses the same linked-devices flow as WhatsApp Web.
Windows?+
iMessage needs a Mac. The business number works everywhere.
Does the team see my texts?+
Personal texting is personal. Business-number threads are the workspace’s.
Can I text from the iOS app?+
Yes. The iOS app sends from your phone directly.
Does it replace Messaging?+
If the team lives in Slack, keep Slack and connect it. Messaging is there for teams that do not.
Can the assistant read Slack?+
The mirrored channels, yes, with your permissions. It can post to a channel too.
Where is the queue?+
Scheduled messages are listed from the Inbox and on each record under the channel they will go out on.
Can the assistant schedule?+
Send it Monday morning is enough. It picks nine in your zone.
Plain text?+
Yes. A plain signature is sent as text, which some inboxes prefer.
Can a sequence skip the signature?+
A step can be set to send without one, for a short follow-up that should read like a quick note.
Try inbox on your own data
Connect your email, then open a person. Most of the product shows up on that one page once the mail is in.
More in Contact
Email, LinkedIn, WhatsApp, texts and the phone, out of one inbox.
Email, LinkedIn, WhatsApp, texts, calls and X in one sequence, with delays, conditions and branches. Build once, enroll many.
DMs, connection requests, search and engagement run in your browser. Our servers never touch LinkedIn.
The LinkedIn feed inside Everything, posts you draft and publish, and a list of who engaged.
Channels, DMs, huddles, and communities that reach past one workspace.
Dial from a record or a list, record and transcribe, and get the outcome written up for you.