OXYGENOXYGEN

Reachable by phone

Mobile phone finder with the whole chain in one column

Mobile numbers are the most expensive field on a contact row, so the chain that finds them should stop early and skip the rows nobody was ever going to call.

try
Start freeRead the docs

A phone waterfall is an economics problem before it is a data problem. Each lane costs more than the one before it, coverage thins fast outside the United States, and running it across a whole list is the quickest way to spend a month of credits in an afternoon.

The column handles the order and the stopping. Providers fire in sequence, a row stops at the first number that comes back, and a lane that finds nothing releases what it was holding. What you configure is which rows are allowed in at all, and that is where the real saving lives.

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.

  • Only the accounts worth calling

    find mobiles for contacts at accounts we marked tier one and that already replied to an email

    A run condition keeps the chain off rows nobody will dial, which matters more here than lane order.

  • Numbers for a WhatsApp motion

    get mobile numbers for these 80 contacts so I can message them on WhatsApp instead

    A resolved mobile is what makes a messaging seat usable, and that seat is priced monthly, not per send.

  • Fill the blanks in the CRM

    our contact records have no phone filled in, fix the ones attached to open deals

    Running on empty cells only, in the object-backed table, leaves the numbers you already trust untouched.

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.

  • Only the accounts worth a call

    Phone spend lands on the contacts a human is genuinely going to dial during this week.

    1. Tables
    2. Records
    1. 1Filter to the tier and stage that justify a call, then run the column on that slice alone.
    2. 2Promote the numbers onto contact records so the next campaign does not buy them twice.
    oxygen find phone

  • Mobile as a messaging channel

    Contacts with a resolved mobile become a WhatsApp step instead of another ignored email.

    1. Tables
    2. Sequences
    1. 1Resolve numbers for the shortlist, then check which are mobile rather than a switchboard line.
    2. 2Enroll the mobile rows into the sequence that owns the WhatsApp step and its cadence.
    oxygen sequences enroll

  • Backfill the contacts on open deals

    Contacts attached to live opportunities gain a number, with the answering lane and its cost recorded.

    1. Records
    2. Tables
    1. 1Open the object-backed table behind your contacts. A record is that row, so a column run there writes onto the record itself.
    2. 2Target only the rows attached to an open deal with an empty phone field, and run in small batches reading the cost as you go.
    oxygen columns run

Capabilities

What you get

  • One chain, not five vendors

    Lane order, skip conditions, and stop-on-first-hit belong to the column. You are configuring a finder rather than five separate vendor integrations.

  • A miss that costs nothing

    A lane charges when it returns a number. When it returns nothing the hold is released and the row moves on to the next lane in the chain.

  • Cost read before the run

    Preview the chain on your own rows, see the expected draw, and approve a ceiling. Phone is the field where that habit pays for itself fastest.

  • Line type where it is available

    Knowing a number is a mobile rather than a desk line is what decides whether it belongs in a messaging step or in a call task for a person.

Boundaries

What Tables does not own

This is Tables resolving one field. The number becomes truth when you promote it onto Records, the call task that follows belongs to Sequences, and a WhatsApp conversation already under way is Messages.

Data sources

What the data actually comes from

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

  • Blitz API

    Head of the phone chain. Resolving here is what stops the more expensive lanes behind it from running at all.

  • MoltSets

    A bring-your-own-key lane. Connect your own MoltSets key and it runs ahead of the chain on your own account; without that key a managed run never touches it.

  • AI

    AI Ark

    Profile-keyed lookup for contacts you hold as a LinkedIn URL rather than as a name and a company.

  • LeadMagic

    A mid-chain mobile lane, cost-ordered after the cheaper verified lookups and ahead of the premium tail.

  • BetterContact

    The aggregator sits last on purpose and only ever sees the residual that nobody upstream resolved.

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

  • Mobile coverage is strongest in the United States and thins quickly elsewhere. Expect a real share of rows to come back empty, and design the campaign so a missing number is not a blocker.

FAQ

Questions people ask first

Why is a phone lookup dearer than an email?
The underlying data is scarcer and vendors price it that way. The chain is built to stop early for the same reason, and skip conditions matter more here than they do anywhere else.
Do I pay when no number is found?
No. A lane bills when it returns a number. A lane that comes back empty releases its hold and passes the row along, so a list with thin coverage costs less than a full one.
Can I tell a mobile from a landline?
Where the source reports line type it lands on the row. That field decides whether a contact belongs in a messaging step or in a call task queued for a human.
Should I run this across a whole list?
Rarely. Phone is the field to resolve last, on the slice that has already cleared qualification, because the chain is costly and most rows on a cold list will never be dialled.
Does a number let me message on WhatsApp?
It is the prerequisite. Sending needs a connected WhatsApp number on a paid plan, which is a monthly seat at $30 with no per-message charge added on top of it.
Where does the number end up?
In a cell, with the answering provider and the cost beside it. Promoting the row writes it onto the contact record with that provenance, so a later campaign reuses it rather than repurchasing it.

Run mobile phone finder with the whole chain in one column 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