Unified inbox

One inbox for email, LinkedIn, and WhatsApp replies

Replies land in a mailbox, a LinkedIn tab, and a phone. The unified inbox merges those three channels into one stream you read and answer from. Email replies also filter by the campaign that sent them.

try
Start freeRead the docs

Outbound breaks at the reply. The sends are automated, but the answers land in a mailbox, a LinkedIn tab, a phone and a sequencer's own inbox, and someone has to notice all four of them.

Every channel lands in the same message shape: direction, contact, sending account, body, time, status, and tags, plus the campaign on email. One merged read then answers a question across three channels, such as every reply you have not answered this week.

Example searches

Ask for it the way you'd say it

Each example is a request in plain words, with what it returns underneath.

  • The morning pass

    list every conversation where they wrote last, across email, linkedin and whatsapp, newest first

    One merged stream with each row's channel, status, tags, and unread count, so no line needs a second tab to read.

  • Only the interested ones

    show conversations classified as interested that nobody has answered yet

    Labels mark inbox state, so a promising thread surfaces without moving a deal.

  • Everything from one account

    find every message we have exchanged with anyone at this company, any channel

    Messages link to the record wherever identity resolves, so the account timeline answers it without three searches.

Plays

Three motions you can run this week

Each one is a chain of OXYGEN primitives: the same hosted objects your workspace already has, composed.

  • Triage the queue in one pass

    A morning of replies ends up labelled, tagged, and either answered or archived, with nothing left ambiguous.

    1. Messages
    2. Tags
    3. Records
    1. 1Open the primary view across the channels you actually run and work it newest first.
    2. 2Tag by campaign and outcome, then archive what is finished so the list shows only open work.
    oxygen inbox list

  • Draft first, then send

    Email replies, and LinkedIn ones once you add that channel, arrive with a draft in the voice page you pinned, and the agent that wrote it cannot send it.

    1. Knowledge Graph
    2. Agents
    3. Messages
    1. 1Turn on the drafting agent so new email replies get a queued answer for review. Add LinkedIn to its channels for those too. The agent skips WhatsApp, where oxygen whatsapp draft writes one on request.
    2. 2Edit or reject in the drafts queue; the agent is held to draft-only by the database.
    oxygen inbox drafts list

  • Answer from the record

    Whoever replies sees the whole history with that account, not only the thread in front of them.

    1. Records
    2. Messages
    1. 1Open the company or person record and read its linked conversations across channels.
    2. 2Reply into the existing thread so the exchange stays one conversation.
    oxygen crm connections companies acme.com

Capabilities

What you get

  • Three channels, one stream

    Email, LinkedIn, and WhatsApp merge into a single list you narrow by channel, status, or campaign tag. Switching channel is a filter, not a switch into another product.

  • Context attached to the thread

    Each thread carries its status and tags, and an email reply links to the campaign that sent it. A company or person record lists the conversations its people's email and LinkedIn identities link to, each naming the sequence that started it, if any.

  • Drafts that cannot send themselves

    The reply-drafting agent writes into a review queue, held to draft-only by a database constraint, not a prompt. A draft goes out when you send it, or ask an Oxygent, OXYGEN's in-app AI agent, to send it. An Agent, a workspace AI worker you configure, can send one too with Full access.

  • Bulk actions in two shapes

    One sets a status on, archives or unarchives up to 100 conversations you picked. The other marks a whole filter read in batches, shows the count first and says when more remain.

Boundaries

What Messages does not own

Messages stores what was said; Sequences decide who gets contacted next, when, and from which rep, and who must never be contacted. Once a reply is classified, it emits a workspace event that a workflow you build can trigger on.

Data sources

Data sources and CRM connections

  • LinkedIn

    DMs and InMail from connected accounts, scoped to the conversations this workspace started unless you widen the sender.

  • WhatsApp

    Chats from a connected number, with per-chat history backfill so an older thread becomes readable here too.

  • Zapmail

    Zapmail mailboxes you import into OXYGEN sync their replies into this stream. Connect your own Zapmail key on a paid plan, import its mailboxes, and grant Zapmail's Onebox consent.

Use managed credits where available, or connect a supported provider key on an eligible paid plan. Your provider bills its calls; OXYGEN adds a per-call platform fee. Signed-in CRM connections such as HubSpot have no per-call fee. Connected sending accounts reserve monthly credits. See pricing and supported integrations.

Limits

Where this stops

  • Classification labels are inbox state, not deal stages. By default, once a sequence is live, an interested label also moves the person's lead stage to engaged, and a clear no to disqualified; moving a deal stays a person's decision.
  • Replies to campaigns another sequencer sends reach this inbox only from a mailbox you also connect here. Move that sending into OXYGEN Sequences so those replies count toward reply rates and stop the sequence.

FAQ

Questions people ask first

Does this replace my normal email client?
For outbound conversations, yes, and that is the point: the reply belongs beside the campaign and the record that produced it. For internal mail, keep the client you already use.
Why one merged inbox instead of three tabs?
Because one message shape lets the sequencer, the record timeline, and reporting read the same conversation. A filter by channel, status, or sender works across all three channels, and a saved view keeps it for the whole team. A tag filter shows email threads only.
Can an agent answer for me?
The reply agent only drafts; a database constraint stops it sending. You send a draft, or ask an Oxygent to: in the workspace's shared Oxygent chat you start on Auto-approve, so switch to Ask for approval to check each send. An Agent with Full access can send one too.
What does the primary view actually filter?
Every conversation on the selected channels whose status is not in the negative tier, which covers not now, not interested, lost, and bounced. The all view keeps everything ordinary in one place.
Do LinkedIn threads from before I connected appear?
Not by default. A new sender admits only chats this workspace opened or invites it sent, which keeps personal history out of a shared workspace. Widening it is a sender setting.
Does reading the inbox cost credits?
No. Listing, searching, and tagging by hand cost no credits, and nothing is charged per sync. Each connected mailbox or account reserves its monthly price in credits, and connecting one needs a paid plan. Drafts and AI classification draw credits per model call, unless a mailbox's price includes its analysis.

Try Messages in your own workspace

Sign up free with a one-time credit grant, and an in-app AI agent researches your company and proposes your first plays. Pick a plan to run one from the web app, the command line, or an AI assistant you link over MCP.

Start freeSee pricing