A CRM is only useful if it is up to date, and the busiest people are the least likely to update it. The improved process checks records before each client meeting, suggests updates from the meeting notes afterwards, and spots duplicates and gaps, so the record reflects what actually happened.
The system suggests. Every change to a client record is approved by the person who owns that relationship.
The job today
After a meeting, the account manager means to update the CRM but goes straight into the next call. Notes stay in a notebook or a document. Contacts change jobs, deals sit at the wrong stage for months, and the same company appears three times with slightly different names. Before a meeting, people check email rather than the CRM because they don't trust it.
Where it breaks
- Records fall behind, so nobody trusts the CRM.
- Duplicate companies and contacts split the history across several records.
- Next steps agreed in meetings are never recorded, so they are missed.
- Reports from the CRM give the wrong picture of the pipeline.
The improved process, step by step
- Check the record before the meetingThe day before a client meeting, the system checks that client's record and lists anything missing or out of date for the owner.
- Read the meeting notesAfter the meeting, it reads the notes or summary that the account manager has saved.
- Suggest the updates AI preparesAn assistant suggests changes: new contacts, changed roles, next steps, dates and the deal stage, each linked to the line in the notes it came from.
- A person approves each change A person approvesThe account manager reviews the suggestions, edits or rejects them and approves the rest. Nothing is written to the CRM without that approval.
- Spot duplicates and gapsEach week the system lists possible duplicate records and records with no recent activity, for a person to merge or tidy.
- Keep a change historyEvery approved change is recorded with who approved it and the note it came from.
Where a person must approve
Every change to a CRM record is approved by the person who owns the relationship. Anything that sends, changes or cannot be undone waits for that approval.
Merging duplicate records is always done by a person, because it cannot easily be reversed.
The data boundary
- The system can read the CRM, the meeting calendar and notes saved for this purpose. It does not read personal email or private calendars.
- It can suggest changes but cannot delete or merge records.
- Only business contact details and meeting notes are used.
- Every suggestion, change and approval is logged.
Checklist before you start
- We have a CRM we are willing to make the single place for client records.
- Meeting notes are saved somewhere the system can read.
- We have agreed what a good record looks like: required fields and deal stages.
- Each client has a named owner.
- We know who decides when two records should be merged.
- Our privacy notice covers the client data we keep.
This is an illustrative walkthrough of a common pattern. It is not a client case study, and the details will differ in your organisation.