Get started
Get started with Cohort
Communicate
Read and send mailEmail signaturesShared mailboxes & agent mailMail rulesDirect messagesSpaces & channelsCalls & meetingsCalendarSearchNotifications
Run the work
Home: the Macro PulseBoards and workstreamsDecisions: propose, sign, supersedeApprovals, holds, and signaturesCharters: the authority ladderThe Audit SpineAI colleagues and the FleetDelegate to AI colleaguesEscalations: when agents raise their hand
Organize & create
Directory: people and organisationsReview queue and capture rulesCRM: pipeline, deals and playbooksFiles: upload, organise and shareDocs, Sheets and DecksDesign: the brand foundationBrand templates and the builderOrg memory: the CortexThe org chart
Operate
Books — the money deskInvoices — receivables & payablesPayroll — runs, seats and the approval floorReconcile — bank feeds and held linesTax & Reports — lodgements and signaturesBooks settings — entities, mandates, automationFrom Revenue to the money deskYour settings — profile, notifications, securityGenesis — start a new organisationFleet economics — compute as payroll

Review queue and capture rules

Agents read, enrich and propose; writing the registry is your act. The Review view under Directory is where those proposals wait — records captured from traffic, suspected duplicates, and awareness requests. Nothing in this queue changes a record until you decide.

The review queue with capture cards, a duplicate and an awareness request
Directory · Review

The queue headline states exactly what waits — "5 items wait for you — 3 captures, 1 duplicate, 1 awareness request". The same counts drive the section nav badge and the Overview card.

Approve a captured record

A capture card shows the proposed record, its source ("From mail", "From calls" …) and a confidence figure.

  1. Review the proposal

    The card previews the fields the sweep extracted — name, address, organisation, relationship.

  2. Approve, or edit first

    Approve writes the record as proposed. The pencil opens the proposal for editing — fix the name or relationship, then approve.

  3. Or dismiss it

    Dismissal is permanent for that source: the same address will not be re-suggested. Approving instead writes the record and links back the thread, invite or feed line that proposed it, so the evidence is attached the moment the record exists.

Receipts stay on screen

Everything you resolve moves to a "Resolved just now" list, each line carrying its ledger id — so you can still answer "what did I just approve?" a minute later. The empty state appears only when the queue is genuinely at zero.

Merge duplicates

When resolution finds two records that look like the same party — say a fuzzy name match — it queues a duplicate instead of silently unifying them.

  • The merge modal compares the two records field by field; you pick the surviving value for each field.
  • Records must carry the same awareness to merge — a merge never silently publishes a restricted record.
  • A merge is reversible for 30 days: everything it moves is recorded in a manifest first, and reverting walks the manifest backwards.
  • Agents cannot execute merges. An agent that tries creates a review item here instead.

You can also merge from a person record directly ("Merge into…") — same modal, same rules.

Answer awareness requests

When a seat asks to see a Named record, the request lands here with who is asking and for what. Grant awareness writes a live, revocable grant scoped to that one record; Decline refuses it. Both answers are logged.

Capture rules: what feeds the queue

Capture rules lists the six source lanes that may propose records, each with live figures and a pause toggle.

The capture rules with per-lane figures and pause toggles
Directory · Capture rules

| Lane | What it proposes | | --- | --- | | From mail | New senders and signature blocks propose person records. | | From calendar | External attendees on accepted invites, matched by domain. | | From calls | Participants named in call recordings and recaps. | | From Books | Recurring bank-feed counterparties without a record propose organisations. | | From the pipeline | Deal contacts without a registry record. | | From imports | CSV imports never write directly — every row runs through this queue. |

Pausing a lane gates the queue, not the sweep: agents keep proposing, but a paused lane's proposals stay out of the queue — out of the cards, the counts and the badge — and flow back in the moment you resume it. Nothing is discarded; dismissal remains the only permanent act. Each toggle flip is itself a ledger event, and the current state is read from that ledger.