An agent that keeps our CRM up to date after every call
Summary, dated next action, project stage: after every call, the agent prepares the CRM update. A person approves it at a glance.
The agent at a glance
- Fathom
- Twenty
The problem
After a call, you move on to the next one. The note is never written, the follow-up is not dated, the project stays at the same stage for three months. At the week's sales meeting, we reconstruct the story from memory, and everyone has their own version.
Everyone knows it should be entered. Nobody does it while it is fresh, because while it is fresh there is always something more urgent.
What the agent does
When a recorded call ends, it reads the transcript, finds the company and the project in the CRM, and prepares three things: a summary note with the decisions, the objections and the commitments on each side; a dated follow-up task; the project's new stage, if the call moved it forward.
It presents everything in a single block. Nothing is written to the CRM until a person has said yes, edited a line or refused.
Participants are always told that the call is being recorded.
How it decides
Four rules, written down rather than left to intuition:
- The company first. Everyone names their projects their own way. The agent finds the company, then everything attached to it, rather than searching for a label and creating a duplicate.
- No follow-up without a date. "Get back in touch soon" is not a task. If the call set no deadline, the agent flags it: a call that ends without a date has not really moved forward.
- Commitments on both sides. What we promised matters as much as what the client promised. A forgotten shipment costs more than a late follow-up.
- It proposes, a person approves. The CRM is shared by the whole team. A mistake spreads through it: a human eye looks at it before it goes in.
What it looks like
The proposal that arrives right after an imagined call (illustrative example, fictional company):
- Note. Call with the operations director. Need confirmed: automate the entry of delivery notes. Objection: the team has just been through a software change and fears a new project. Decision: a short scoping, with no commitment on what follows.
- Commitments. Us: send a scoping proposal before Friday. Client: provide ten anonymized delivery notes.
- Task. Send the scoping proposal, due Friday.
- Project stage. Moves from "Discovery" to "Proposal".
What we learned
- The approval holds because it takes a few seconds. Reviewing a well-made proposal is easy; writing a note from scratch, nobody does it.
- Spotting what is missing is worth as much as summarizing what was said. The agent that flags "no date set" changes the way we end calls.
- The CRM becomes a source we trust again, and the sales meeting is about facts rather than memories.
Take it to your company
The same pattern works wherever a tool depends on an after-the-fact entry: support tickets after a client call, a technician's visit report, site follow-up, a candidate's file after an interview. The agent reads what was said, prepares the update in your tool, and a person approves it before it goes in. At our place, the tool is Twenty; at yours, it will be the CRM, the ERP or the business software your team already uses.
About the author
The tasks that keep coming back and follow rules are ones an agent can take on: less repetitive work for your team, fewer things forgotten.
It works inside your tools, with limited rights, and a person approves the steps that matter.
And if you do not need an agent, we tell you.
More episodes
An agent that files our meeting transcripts
Every recorded meeting ends up in the right Drive folder, with nobody touching it. Here is what this agent does, how it decides, and what we learned.
An agent that prepares our sales meetings
The evening before a meeting, a one-page brief: who the company is, what we have already said to each other, and what to learn during the call.
An agent that runs our AI watch every morning
About twenty video channels, blogs, forums, newsletters. Every morning, a note of the day in the Drive and a three-paragraph email for the team.