Messaging channels
WhatsApp outreach in the same cadence as email
Plenty of buyers answer a message faster than an email. A connected number is a $30 monthly seat, and a WhatsApp step sits inside the same sequence as the email that came before it.
In a lot of markets a message is simply the channel a buyer reads. Bolting on a separate messaging tool means a separate list, a separate meter, and a separate pile of replies. Here it is another step type inside a sequence you already wrote, with the same enrollment, the same suppression, and the same exit on reply.
The channel only works when the number is right, so the phone waterfall runs first. A mobile is resolved from the profile or the record, checked for line type, and written back with the lane that answered and what it cost. A landline never reaches a messaging step.
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.
Find the mobile first
get a verified mobile number for every contact in this table before we message anyone
The waterfall bills only when a number comes back, and each cell names the lane that resolved it.
Message after email silence
if nobody opens the second email within a week, send a short whatsapp note instead
The branch is a step in the same sequence, so there is no second campaign to keep aligned.
Screen out the landlines
drop anyone whose number is a landline before the messaging step runs
Line-type validation runs as its own column, so the sequence never queues a send that cannot land.
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.
Verify the mobile before you use it
Only rows carrying a real, validated mobile reach a messaging step, which keeps the channel clean.
- 1Run the phone waterfall on the rows you intend to message, reading the preview cost first.
- 2Check line type, then filter the table to mobiles before enrolling anybody.
oxygen find phoneEmail first, message on silence
A quiet prospect gets one short note on a channel they check, instead of a fifth email nobody opens.
- 1Order the steps so the messaging touch sits after the email that went unanswered.
- 2Let reply-stop exit anyone who answers on either channel.
oxygen sequences enrollKeep the conversation on the record
Every chat attaches to the company and person it belongs to, rather than living on somebody's phone.
- 1Sync the connected number so chats and their history land in the workspace store.
- 2Read the thread from the record timeline beside the email and LinkedIn touches.
oxygen whatsapp history
Capabilities
What you get
A number priced as a seat
A connected number is $30 a month, and sending or replying on it draws no per-message credits. You plan around the account's own limits, not around a per-send price.
A phone chain that bills on a hit
Mobile lookup runs as an ordered waterfall and charges only when a number comes back. Preview the cost on your own rows, then read which lane answered each cell.
Warm sends with real limits
Daily volume, spacing, and quiet hours live on the sender. The sequence proposes a step and the sender decides when it goes, which keeps a young number from looking mechanical.
One thread, one store
Chats, backfilled history, read state, and labels land in the same message store as email and LinkedIn, so a buyer's whole conversation reads in one place.
Boundaries
What Sequences does not own
Sequences owns the cadence and the dispatch. The conversation itself belongs to Messages, and a one-off answer into an existing chat is an inbox action rather than an enrollment. A number becomes durable truth only once promoted onto a Records object.
Data sources
What the data actually comes from
Every value lands with its provider and cost recorded on the cell.
WhatsApp
Your connected number. The seat is the price; sending, replying, and history sync carry no per-message charge.
Blitz API
LinkedIn company and profile reads that pin down who a row actually is before the phone chain runs on it.
LeadMagic
Mobile and company enrichment for the rows a profile read alone cannot resolve, billed only where a number comes back.
ClearoutPhone
Validates the number and its line type, so a landline or a dead line never reaches a messaging step.
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
- This is warm messaging on a connected number, not a broadcast API with template approval. Volume stays modest by design, and a number that behaves like a blaster gets treated like one by the platform.
- A cold first touch, where the lead has no chat with your number yet, runs only when the sequence carries an explicit cold-initiate opt-in. The connected-account protocol is unofficial, so the account risk is yours to accept and the warm-up ramp caps the volume either way.
- Outside a sequence the direct send is warm-only: a raw number with no prior conversation is rejected rather than dialled, so a one-off note needs the chat to exist first.
FAQ
Questions people ask first
Is this the business API or a personal number?
What does a message cost?
How do I get mobile numbers in the first place?
Can a messaging step follow an email step?
Where do replies show up?
Do I need a paid plan for this?
Run whatsapp outreach in the same cadence as email 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.