For SDR leaders

Run an SDR team on one inspectable pipeline

Two SDRs (sales development reps), four mailboxes and a spreadsheet nobody trusts. The fix is one pipeline where the list, the senders and the replies share a database.

try
Start freeRead the docs

An outbound team of three breaks on coordination, not on effort. Two reps work the same account from different exports. A mailbox quietly starts bouncing. Somebody writes to a customer who churned last month. Buying another sequencer does not fix any of that.

Sequences own what must be central: the cadence (when each step goes out), enrollment, which rep sends to which lead, and daily limits. Suppression (a do-not-contact list every sequence obeys) and reply-stop (a reply ends that lead's steps) live there too. A sender profile is one rep's mailboxes and accounts under one name and picture.

Who this is for
The person running outbound for the GTM (go-to-market) team at a company that sells to other businesses. Usually a head of sales or an SDR (sales development rep) lead. Two or more reps work named accounts on a proven offer.
What it looks like today
Coordination eats the week. Lists get copied, two reps work the same account, a mailbox degrades unnoticed, and a churned customer gets a cold email. The sequencer knows none of it.
What changes
Cadence, enrollment, sender assignment, suppression and reply-stop are enforced centrally rather than remembered. Each lead keeps one rep as its sender, and replies land in one inbox.

Example searches

Ask for it the way you'd say it

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

  • Split a list between reps

    split this list between my two reps and make sure neither one writes to the other's leads

    Put both reps' sender profiles on one sequence. Each new lead goes to the rep with fewer leads, unless the other already wrote to them on LinkedIn, and stays with that rep.

  • Which mailbox is about to fail

    which of my sending mailboxes are bouncing or dropped out of warmup this week

    The health read ranks sending domains worst first by rejections and bounce rate, and counts mailboxes by warm-up state. Warm-up is slow, rising volume that builds a new mailbox's reputation.

  • Protect the customer list

    suppress everyone at a company we already sell to before this campaign starts sending

    A company-domain entry blocks every lead whose row carries that domain, in every sequence.

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.

  • One list, two reps, two identities

    Each lead hears from one rep, under that rep's own name and sending limits.

    1. Tables
    2. Sequences
    3. Messages
    1. 1Build a sender profile per rep with their mailboxes and LinkedIn account, and attach both to the sequence.
    2. 2Enroll the list once. Each lead gets the rep already talking to them on LinkedIn, or the rep with fewer leads, so the from name and reply thread match.
    oxygen senders profiles create

  • Deliverability as a standing check

    A bouncing mailbox pauses before a bad domain becomes the team's problem.

    1. Sequences
    2. Observability
    1. 1Attach domains and mailboxes, keep warm-up on, and read the health list weekly.
    2. 2Let thresholds pause a mailbox. A lead already contacted from it waits for that mailbox to recover instead of switching sender.
    oxygen mailboxes health

  • Replies that end in a stage

    Every human reply is triaged and written back to the record, not left in a mailbox.

    1. Messages
    2. Records
    3. Dashboards
    1. 1Work the merged inbox in bulk, label the buckets, archive the noise.
    2. 2Log the outcome on the person and the deal so the pipeline view stays honest.
    oxygen inbox bulk

Capabilities

What you get

  • Suppression that covers everyone

    Do-not-contact lists block an email address, a company domain or a LinkedIn company page in every sequence. A company entry checks the lead's company fields, never their email.

  • Per-rep identities, one shared list

    A sender profile groups one person's mailboxes, LinkedIn account and WhatsApp number under one name and picture, so a list can go out as three people.

  • One inbox across three channels

    Email, LinkedIn and WhatsApp replies land in one inbox with labels and bulk actions, so triage is a single session instead of four tabs.

  • Sending infrastructure on one bill

    Domains, mailboxes, warm-up and monitoring are bought and run here. A LinkedIn account or WhatsApp number reserves a flat amount of credits each month, with no per-action charge.

Instead of

The stack this replaces

Native, on one contract and one credit balance, not another tab wired to the last one.

Data sources

Data sources and CRM connections

  • Blitz API

    Heads the work-email chain, keeping the pricier lanes behind it idle.

  • LeadMagic

    Fills the gaps the first lane leaves, including mobiles worth a call.

  • MillionVerifier

    Grades each address before enrollment, so a bad list is caught at build time.

  • Instantly

    Keeps an existing campaign workspace usable while the list and suppression move over.

  • People Data Labs

    Supplies the size and industry facts a rep filters on before deciding where the week goes.

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

  • Connecting a mailbox to send from your own identity needs a paid plan. Setting up a list and previewing a cadence is free; sourcing and enrichment draw credits.
  • Warm-up and monitoring reduce risk; they do not remove it. A new domain still needs weeks to ramp up, and a bad list damages a sender whoever sends it.

FAQ

Questions people ask first

Can two reps work the same list without colliding?
Yes. Attach both reps' sender profiles to one sequence and enroll the list once. Each lead gets one rep and keeps them. A lead that a sender outside the sequence already wrote to on LinkedIn is skipped. Suppression is workspace wide, and a reply stops that lead's steps.
What happens to a mailbox that starts bouncing?
It pauses. Thresholds sit on the sender, and the pause and its reason show on the health list. A lead already contacted from that mailbox waits for it to recover instead of switching sender, so fix that mailbox first.
Do LinkedIn steps carry a per-action cost?
No. A connected LinkedIn account reserves one flat amount of credits a month, listed on the pricing page, and invites, messages, profile visits and follows carry no charge at use. WhatsApp is the same shape.
How do we move off the sequencer we use now?
In stages. Keep current campaigns running while the list, records and suppression move across, then attach domains and cut one sequence at a time.
Where do replies actually live?
In one inbox that email, LinkedIn and WhatsApp share. A reply stops that lead's steps and shows up there, ready to label or bulk-archive with the rest.
Can I see what a rep sent without asking them?
Yes. Every send is logged with its sender, time, status and message, stored once. Sequence analytics and the run log are readable on your own, without asking anyone.

Put your GTM motion on one stack

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, and it sources the buyers, writes the sequence, and enrolls them. Connect the mailbox or LinkedIn account it sends from, and it is ready to send.

Start freeSee pricing