One unified inbox for every reply, from every account.

An inbox where the replies from every channel and every account land in one list. In GetSales it is Unibox: LinkedIn and email from every sender profile side by side, each reply marked with the channel it came on, and a filter keeps one channel, one sender profile or one workflow when you want it.

For answering every reply from one place. A team that writes from several LinkedIn accounts and mailboxes reads and answers all of them in one list, and no reply waits in an account nobody was watching.

Nothing gets missed, and every answer has its context: the whole thread across both channels, the person's stage and workflow on the card beside it, and filters that show only the replies that need you. By default a reply also pauses that person's follow-ups in their workflows.

A team inbox, or shared inbox, is one inbox the whole team works, for every account it sends from. In GetSales it is Unibox: everyone sees the same list of replies and answers in a thread as the sender profile it belongs to. A sender profile can name a task assignee, and when the AI SDR hands one of its threads over, it can email that teammate a link to it, or the workspace owner when nobody is named. An agency that gives each client its own workspace gets a Unibox per client, so one client's replies never sit in another client's list.

Every LinkedIn account and mailbox your sender profiles hold. A sender profile is the identity your team sends as: a LinkedIn account and its mailboxes. Mailboxes sign in with Google or Microsoft, or connect over IMAP and SMTP, and the replies of all of them land in the same list.

Yes. When the same person writes to you on both channels, merge the two threads and they become one: the messages and emails of both, in the order they happened. The thread also shows what the person did between the messages, such as an accepted invitation, an opened email or a visit to your site that Signals picked up.

Open Needs you, one of the four saved filters that come ready, or add chips for the stage, the classification, the company or the workflow and save the set under a name. Snooze a thread you cannot answer yet and it comes back when you said, or as soon as they reply. From the keyboard, the arrow keys walk the list, U shows only unread, E closes a thread and H snoozes it.

Each workflow's After a reply setting decides, and by default it hands the replies to the AI SDR. The AI SDR drafts each answer, and each scenario sets whether it sends on its own or waits for your OK. Any thread it should not answer alone comes to you. Every choice but Continue the sequence pauses that person's steps, and a reply reaches every live sequence of that person, each by its own setting. The four choices are on the multichannel sequences page. Write in a thread yourself and the AI SDR drops what it had not sent there and, by default, plans its follow-ups around your message.

Not directly. When the person is in a playtable, each reply lands in their activity there. A webhook, set up through the API or the MCP server, can tell your own URL about each new reply, so your CRM or your own tools can pick it up, and the same MCP server lets your own AI agent search the threads, read them and answer.

Unibox has no price of its own: it holds the replies of the LinkedIn accounts and mailboxes your sender profiles connect. Sending a reply spends no credits. AI work does: the AI SDR's work on a thread, and speech turned into text, when you dictate an answer or a lead sends a voice message. Sign up free: Playtables stay free with your own API keys, and LinkedIn and email come with a 7-day trial. What LinkedIn accounts, email capacity and credits cost is on the pricing page.