Records and CRM

A CRM your agent can read, write, and explain

An AI CRM, the system holding your companies, people and deals, is only worth what it can prove. Edits, enrichment from data providers, syncs and promotions from tables record what wrote each value and in which run, so you can check an agent's change.

try
Start freeRead the docs

Most CRMs assume a human types and a manager reports. This one assumes an AI agent writes and a human checks. Companies, people and deals carry typed fields, relationships, an activity timeline, merge history and provenance, a record of what wrote a value and when.

By default, a person moves new, contacted, engaged, meeting, customer, with nurture, disqualified and unsubscribed off-ramps. Deals move through the pipeline, the stages a deal passes: lead, in progress, then won or lost. Company lifecycle is derived from its people and deals until someone overrides it, and the override is recorded.

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 quiet deals question

    how many open deals have gone three weeks without any activity

    The dashboard summary counts open deals with no linked activity in a window you set, here 21 days; the web uses 14 days.

  • Where did this value come from

    who set this company's headcount and which run wrote that number

    The field names the source, run and time of its current value, and recent changes show old and new values.

  • Clean up the duplicates

    find the companies we have stored twice and merge them without losing history

    The duplicates view ranks likely pairs, shared identities such as a domain first, then same names. Review merge shows the field changes before Confirm merge writes them.

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.

  • Promote a table into records

    A list you qualified in a table updates matching company and person records, and a bind column set to create adds missing ones.

    1. Tables
    2. Records
    1. 1Research in a table, where a row is a candidate and mistakes stay out of the CRM.
    2. 2Bind rows to records by domain or email, preview, then promote only the rows that held up.
    oxygen tables promote

  • Backfill what the record is missing

    With enrichment on, new records fill blank fields from data providers and AI; a backfill covers older ones.

    1. Records
    2. Observability
    1. 1Turn on only the enrichment presets you need; each shows its credit cost per record.
    2. 2Preview the backfill free, then run it under a credit ceiling.
    oxygen crm enrichment backfill

  • Let replies move the lead stage

    People who reply to a sequence, OXYGEN's timed outreach, land in the CRM, and interested, meeting, no and stop replies move their lead stage.

    1. Sequences
    2. Messages
    3. Records
    1. 1Start any sequence live yourself once; that arms one rule for all of them, which files the people who reply.
    2. 2Check it with crm automation rules, then read the stage change on a replier's timeline.
    oxygen crm automation rules

Capabilities

What you get

  • Provenance you can trace

    Edits, enrichment, syncs and promotions record what wrote each value, when and in which run. Tags and the blanks a merge fills are not tracked per field yet.

  • A stage model that ships working

    Person stages, the deal pipeline and a derived company lifecycle come set up for teams selling to businesses. Rename, add or remove stages in Settings.

  • Duplicates merged, not deleted

    A merge keeps the record you choose with its values, fills its blanks from the duplicate, moves the duplicate's links over and marks it merged. Deleting a record is separate, and permanent.

  • One contract, three surfaces

    On the terminal, crm assert writes a record and crm search finds one; an AI assistant gets both over MCP, the protocol AI tools use to call OXYGEN. The web CRM's search bar runs the same search in quick-suggest mode.

Boundaries

What Records does not own

Records holds what your business treats as true. Sourcing, waterfalls (trying providers one after another) and most AI columns belong to Tables, where rows are candidates. Conversations live in Messages; who you sell to lives in the Knowledge Graph.

Data sources

Data sources and CRM connections

  • People Data Labs

    Funding rounds and a revenue band, tried when the first source has none, in table enrichment before you promote.

  • Blitz API

    Work email and mobile phone lookups for people, in the CRM's own enrichment presets.

  • Attio

    The scheduled sync runs one way, from OXYGEN into Attio; Attio changes come in only through a one-off import.

  • HubSpot

    Syncs both ways with a connected HubSpot portal, through your own connection and its request limits.

  • PredictLeads

    Funding, technology and news events per company from market signal search, kept as table rows, off the record timeline.

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

  • A stage edited in the web grid or record panel writes no timeline entry yet; crm assert, the command that writes records, logs the move.
  • Field history is not a permanent audit log: plan on 7 days of past changes.

FAQ

Questions people ask first

Is this a real CRM or a table with a nicer name?
A real one. Records hold each company, person and deal once, with relationships, a timeline and sync state. A table row changes a record only when you promote it, and a bind column adds records only when set to create them.
Can I keep the CRM I already run?
If it is HubSpot or Attio, yes. HubSpot syncs both ways. OXYGEN's scheduled sync writes into Attio one way, and Attio changes come in only through a one-off import. A scheduled sync takes one approval, with row and credit caps.
What stops an agent corrupting my data?
Edits, enrichment and syncs record what wrote each value, so a bad write can be traced. A merge needs a confirm after its diff. Deletes are permanent. In your own chat, an Oxygent, OXYGEN's in-app AI agent, asks before deleting by default. A shared chat starts you on Auto-approve, so switch to Ask for approval.
How is a record different from a table row?
A row is a candidate you are still testing; a record is what the business believes. A bad enrichment run in a table changes no record until you promote it.
Does the CRM itself cost credits?
No. Records, objects, relationships, activities and pipeline views cost no credits on any plan, free included. Enrichment, AI steps, and a sync's or import's steps and own-key calls draw credits, under the cap you set.
How are duplicates handled?
Identity keys stop a re-import from making a second copy: companies match by domain, people by email. The duplicates view lists likely pairs for review; it has no sidebar entry yet, so open /crm/companies/duplicates.

Try Records 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