CRM Meeting Notes: Separate Decisions, Commitments and Open Questions
“Good call. Interested in the workshop. Send information.” A week later, nobody can tell whether the client chose the workshop, asked to compare formats or agreed to another meeting.
Useful CRM notes let someone reconstruct the outcome of a conversation. They distinguish what was decided, what someone promised to do and what remains unanswered. Those distinctions matter more than recording every sentence.
Start with the outcome, then add the context
Write the main result in one or two sentences. Include the task discussed and the change, if any. “No format chosen; client will compare the workshop with a written review after receiving the outline” is much more useful than “positive meeting.”
Record the date, participants and the deal or task concerned. If your notes rely on memory rather than a written confirmation, make that clear. You can link to relevant supporting material without copying the whole conversation into several places.
A note should be short enough for a colleague to use and precise enough to prevent them from acting on an assumption.
Separate four kinds of information
Here is a fictional example from a consultancy's discussion with a client about a planning workshop.
| Type | What happened in the conversation | CRM note |
|---|---|---|
| Decision | Client chose team leaders as the intended audience | Workshop outline to address team leaders |
| Commitment | Consultant agreed to send an outline on Thursday | Alex to send outline Thursday; date confirmed in call |
| Open question | Client had not checked participant availability | Client coordinator to check before dates are proposed |
| Suggestion | Someone mentioned a later session for managers | Possible later session; no request or commitment |
A suggestion can be worth retaining without becoming a task. A decision can be real while another question remains open. Do not force every line into “next action” merely because it sounds useful.
When you are unsure which bucket applies, state the uncertainty and decide whether clarification is necessary. “I understood that we would send the outline first; please correct me if you intended a full proposal” makes the point that needs checking visible.
Give commitments an owner and a finish
For each agreed action, record who will do what and when. Describe an output that another person can recognise. “Work on workshop” is vague. “Send a one-page outline covering audience, topics and information needed to choose dates” is usable.
Separate the action due date from a meeting date or hoped-for decision date. If no date was agreed, write that plainly and assign the next internal step. Do not represent a reminder you set for yourself as a deadline imposed by the client.
If the action depends on an answer, record the dependency. In the fictional example, the consultant can prepare the outline while participant availability remains open. The team cannot honestly describe workshop dates as confirmed.
Send a recap when it helps the work
A recap should focus on the outcome and commitments the other person needs to check. It need not reproduce your internal notes or interpretation of the sale.
For the fictional call, the recap could read:
I will send the team-leader workshop outline on Thursday. You will check participant availability before we propose dates. We have not selected a date or added the possible manager session to the scope.
Check that this matches the conversation before sending it. If the client corrects the recap, update the working note and linked tasks so colleagues can see the current understanding. Keep enough context to explain a meaningful change.
Test the note through another person's next step
Ask a colleague who was not in the meeting to identify the decision, your promise and the unanswered question. If they would send a full proposal when you promised an outline, revise the note before the work moves further.
When evaluating Konekt CRM, try entering this fictional meeting and finding its outcome from the related contact or deal. Check how your intended setup keeps the note, supporting material and actions usable together. Confirm any required functions rather than assuming an automatic recording or summary feature.
The note is ready when the next person can continue the work faithfully, including the points that were left undecided.