You hang up. The call was good. You open the transcript and the buyer’s name is wrong — again.

Not “slightly off.” Wrong enough that a naive CRM write invents a second contact. Six weeks later your pipeline has two people who are one person, two company records that are one firm, and a follow-up email that went to the ghost. For a 2–25 person US consulting shop, that is not a data-hygiene hobby. That is lost trust, wasted hours, and a board you cannot trust before the next proposal.

Cockpit treats that moment as a product problem, not a cleanup weekend. Meeting ingest runs entity match (including typo-tolerant search), then a human confirms the person or company in the approvals inbox before the CRM sticks. No silent duplicate contacts.

The failure mode principals already know

Small professional-services shops do not lose deals because they forgot a feature flag. They lose clarity because the system of record got ahead of the human.

Typical loop after a discovery or delivery call:

1. Recording → transcript lands with ASR spelling damage
2. Someone (or a bot) creates/updates HubSpot or Salesforce from the text
3. “Jordan Mendez” becomes “Jordan Mendes,” or the account name picks up an extra LLC suffix
4. Next week a teammate matches the real domain, creates the correct contact, and now you have twins

You can paper over it with merge tools. You cannot paper over the week where the SDR emailed the duplicate and the principal looked careless on a live account.

The fix is not “better transcription.” Transcription will keep misspelling. The fix is match, then confirm, then write.

What Cockpit does on meeting ingest

When a meeting lands in Cockpit, ingest does not blast contacts into CRM. It:

1. Pulls the meeting into the work surface (the call is a first-class object, not a chat paste)
2. Runs entity match search against people and companies you already have — including near-matches when the transcript mangled a name
3. Queues a human confirmation in the approvals inbox: is this the same person, a new person at a known company, or a net-new company?
4. Only then does the CRM-facing record stick

That order matters. Search without a gate still invents rows when confidence is soft. A gate without search dumps every misspelling on you as a blank form. Together: the system proposes candidates; you decide; the write follows the decision.

Entity match is for typos, not magic merges

Entity match here is practical, not mystical.

Transcripts drop middle initials, swap vowels, truncate last names, and invent company spellings from accent and crosstalk. Match search is there so “Mendez / Mendes / Menendez” surfaces the contact you already sold — or shows you cleanly that this is new.

What it does not do:

• Auto-merge two contacts because the first names rhymed
• Quietly attach a call to the wrong account because the domain was close
• Skip you when the system is unsure

If the match is obvious, confirmation is fast. If it is not, you still get a deliberate choice instead of a duplicate. For a principal who is also the CRM admin, that is the difference between a thirty-second approve and a thirty-minute archaeology dig next quarter.

The approvals inbox is the control plane

Cockpit’s approvals inbox is where those confirmations live — alongside the other decisions you already refuse to leave unsupervised (merges, contact creates, task start/close, outbound drafts).

Same posture every time:

• Agents and ingest propose
• You dispose
• The system of record updates after the swipe

For consulting principals, that maps to how you already run the firm. You do not let a junior open a SOW without a look. You should not let a transcript open a CRM contact without a look. The inbox is that look, in one place, instead of Slack screenshots and “did you mean this HubSpot URL?” threads.

A Monday morning that stays clean

Picture a 12-person boutique. Three principals take calls. Two analysts handle follow-ups. Nobody has a full-time RevOps seat.

Without a gate, Monday starts with three new contacts that are actually two buyers and one misspelled account. Someone spends the afternoon merging. Pipeline reports disagree with the project board. The next proposal pulls the wrong email.

With Cockpit meeting ingest + entity match + approvals:

• Each call’s people/companies show up as match candidates
• A principal or ops lead confirms in the inbox before CRM sticks
• Follow-up work references the same contact the proposal will use
• You do not discover the duplicate when legal asks for the master contact list

You still spend attention. You spend it before the damage, not after.

What this post is not claiming

Shipped and fair to name here: meeting ingest, entity match (including typo cases), and the approvals inbox that makes confirmation real.

Not claimed here: hook/execution logs tied to live sessions, streaming agent UI, Claude CCMA as a runtime option, or a client handoff that embeds an agent. Those are labeled coming soon on the product page. This how-to stays inside what you can run today.

Put the gate where the names land

If your shop is small enough that the principal still feels every CRM bruise, start with the post-call path:

1. Land meetings in Cockpit instead of “transcript → paste into CRM”
2. Let entity match propose people and companies — including near-matches from bad spelling
3. Confirm in the approvals inbox before anything sticks
4. Only then let follow-up, proposals, and project work inherit that record

That is how you keep agent help without silent duplicate contacts.

See how the loop fits the rest of the OS on cloudbeast.io/cockpit. If you want this gate on your own discovery and delivery calls, book a discovery call.