Skip to main content

Use case

An AI agent for CRM upkeep

The agent turns calls, emails and meetings into structured records without anyone typing them: who was spoken to, what was agreed, what happens next. It works from what was captured somewhere. What was never said out loud, or was said in a car park, stays lost — and no tool changes that.

By Gorden WübbeAutomation, agents and search visibilityUpdated 10 August 2026

The CRM problem is not the CRM

Every company of this size has bought a CRM, and most are disappointed by it. The software is rarely the reason. The reason is that keeping it current is administrative work assigned to the people with the least patience for administrative work, at the end of a day when they have already done their actual job.

So records get filled in from memory on Thursday for a call on Tuesday, or not at all. Then someone builds a report on that data and everyone quietly agrees not to trust it.

What the agent does

  • Creates the record from the conversation — from the email thread, the call transcript where one exists, the appointment that was booked.
  • Fills the structured fields: who, what was discussed, what was agreed, what the next step is and when.
  • Links related items, so the enquiry, the call and the quote sit on one record instead of three.
  • Flags what it could not determine rather than leaving a field silently blank — an empty field and an unknown value look identical later, and they are not the same thing.

The hard limit

An agent cannot recover what was never captured. A conversation in a car park, a decision made in a corridor, a customer’s reservation that someone picked up on but never wrote down — none of that reaches the CRM, and no amount of capability changes it.

That matters for expectations. This use case makes existing information structured and complete. It does not make undocumented knowledge appear, and a project sold on the second promise fails on contact with the first month.

Recording is a legal question first

Call transcripts make this use case considerably stronger, and recording calls requires consent from both sides in the EU and in many other jurisdictions. That is a decision to settle before anything is built, not a detail for the launch checklist. Where recording is not appropriate, the agent works from written material and delivers less — which is still more than the current state.

What stays with people

The factual layer is the agent’s: who, when, what was said, what was agreed. The assessment layer is not. Whether the deal is likely, whether the customer sounded uneasy, whether it is worth another call — those are judgments from someone who was present, and a confident-sounding automated guess in that field is worse than an empty one.

What it connects to

The CRM with write access, the email system, and the phone system where transcripts are in play. Calendar too, since appointments are part of the record.

How to tell whether it worked

  • Field completeness on records from the last 30 days.
  • Time between a conversation and its record existing.
  • Contacts with no record at all — the number most people have not looked up.
  • Time the team spends on CRM admin per week.

Record the first three before starting. They are the argument for doing this at all, and they are the only way to show afterwards that anything changed.

What people ask about CRM data

Where does the agent get the information from?
From what already exists in written or recorded form: emails, call transcripts, meeting notes, the booking that was made. It cannot recover what was never captured anywhere — a conversation in a car park stays lost, and no tool changes that.
Does this mean recording every call?
Only where that is lawful and disclosed, which in the EU means consent from both sides. Where it is not appropriate, the agent works from what is written down instead. This is a question to settle before building rather than after.
Will the records be accurate?
More accurate than the current state, which in most companies of this size is a mix of half-filled fields and notes written from memory three days later. The realistic comparison is not against a perfect CRM but against the one you actually have.
What should stay manual?
Assessment. Whether a deal is likely, whether a customer is unhappy, what the next step should be — those are judgments and belong to the person who was in the conversation. The agent handles the factual layer underneath them.
How do we measure it?
Field completeness on records created in the last 30 days, how long after a conversation the record appears, and how many contacts have no record at all. The third is usually the number that surprises people.

Read next

How many contacts have no record at all?

Most CRMs can answer that in a filter. The number is usually higher than expected, and it is where this conversation starts.

Book a scoping call