OXYGENOXYGEN

Unified inbox

One inbox for email, LinkedIn, and WhatsApp replies

Replies never arrive in the tool that sent them. The shared inbox merges three channels into one stream, and every thread carries the sequence, the step, and the record it belongs to.

try
Start freeRead the docs

Outbound breaks at the reply. Sends are automated, then the answers land in a mailbox, a LinkedIn tab, a phone, and a sequencer's own inbox, and somebody is supposed to notice all four. This surface exists because a conversation is a fact about a person, and a fact deserves exactly one home.

Every channel adapter writes the same envelope: direction, thread, participants, linked record, the enrollment behind it, delivery and read state, provider ids, and the run that authorized the send. One merged read therefore answers a question across three channels without them drifting apart.

Example searches

Ask for it the way you'd say it

Every search below runs on the same hosted Tables, with the cost previewed before anything is spent.

  • The morning pass

    list everything unread across email, linkedin and whatsapp, newest first

    One merged stream with channel, sequence, and current status on each row, so no line needs a second tab to read.

  • Only the interested ones

    show conversations classified as interested that nobody has answered yet

    Classification labels are inbox state rather than pipeline stages, 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 assigned, 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 stays honest.
    oxygen inbox list

  • Draft first, human sends

    Replies arrive with a grounded answer already written, and a person still presses send.

    1. Knowledge Graph
    2. Agents
    3. Messages
    1. 1Turn on the drafting agent so inbound conversations get a queued reply for review.
    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 messages query

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 conversation carries the sequence and step that produced it, the linked company and person, and the run that authorized the send. Answering needs no reconstruction.

  • Drafts that cannot send themselves

    The reply-drafting agent writes into a review queue and is held to draft-only by a database constraint rather than a prompt. A human accepts, edits, or rejects it.

  • Bulk actions with two honest shapes

    One acts on ids you picked. The other sweeps a filter in bounded batches, previewed first, and says when work remains so a long clean-up can resume where it stopped.

Boundaries

What Messages does not own

Messages stores what was said. It does not decide who gets contacted next: cadence, enrollment, sender rotation, and suppression belong to Sequences. A reply that should trigger something downstream is recorded as a Signal, and Workflows acts on it.

Data sources

What the data actually comes from

Every value lands with its provider and cost recorded on the cell.

  • LinkedIn

    DMs and InMail from connected seats, 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.

  • Instantly

    Replies to campaigns still running on an Instantly workspace are pulled into the same stream rather than left behind.

  • Smartlead

    The same for a Smartlead campaign, so a phased migration never means watching two inboxes for a month.

Run these on Oxygen's managed credits, or connect your own provider keys and pay the vendor directly — the same columns, the same runs, the same provenance either way. See every integration.

Limits

Where this stops

  • Classification labels are inbox state, not pipeline state. An interested label is a triage hint; moving a deal forward stays a decision somebody makes on the record.
  • Email and DM threads still live in two table families behind the merged read, so message-level features such as full-text search and the status taxonomy are implemented per arm until the physical unification lands.

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 envelope contract lets the sequencer, the record timeline, and reporting read the same conversation without anyone reconciling copies. Email and DM threads still sit in two table families behind that merged read, which the unification slice is closing, and a new channel arrives as an adapter rather than another version of the truth.
Can an agent answer for me?
It can draft. The reply agent writes a proposed answer into a review queue and is prevented from sending by a database constraint, not by instructions. Approving is a human action every time.
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 that scope is a setting on the sender.
Does reading the inbox cost credits?
No. Listing, searching, syncing, and tagging by hand are unmetered. Credits are drawn by the model call behind analysis, classification, and drafting, and sending needs a connected channel on a paid plan.

Run one inbox for email, linkedin, and whatsapp replies on your own workspace

Sign up, get a working workspace with a one-time credit grant, and run the first play from the web app, the CLI, or your AI assistant over MCP.

Start freeSee pricing