CRM ACTIVITY & HISTORY
Carry the customer’s story through every handover.
Read recorded interactions and trace changes to the customer record, so a new owner can understand what happened and what needs attention next.
Customer confirmed the scope of the new project.
Recorded by · Alex WinterResponsible owner changed to Jamie Lee.
Recorded by · Jamie LeeA handover needs more than the latest field values
The current phone number or deal stage tells you where a record stands. It does not explain the conversation that led there. Customer work needs both: a readable activity history and a trace of changes to important records. Tsumira brings these into the CRM context, helping a colleague distinguish the customer conversation from the administrative changes made after it.
Record the interaction where it will be needed
Log an interaction against the relevant contact or company, including its channel, content and occurrence date. A telephone conversation, visit or brief memo can become part of the same customer history. Write a factual note about the request, commitment or open question. That gives the next reader useful evidence instead of a vague indication that someone contacted the customer at some point.
- Dated customer activity
- Communication channel and written context
- Connection to the relevant person or company
Distinguish activity from a record change
Activity describes business interactions. Change events describe actions taken on the CRM record: the actor, event time and fields affected. Seeing those together makes the timeline easier to interpret. A revised contact detail is not another customer call; a stage update is not proof that the customer accepted a proposal. Keeping the distinction clear helps the team explain what is known without turning an internal update into a customer promise.
- Separate activity and change events
- Recorded actor and occurrence time
- Changed-field information
Give a new owner a practical starting point
Before taking over a customer, review recent interactions, open next actions and the relevant record discussion. Read access still follows the current person’s permissions. History does not provide a shortcut around private files or inaccessible related records. Use the visible material to identify what is already agreed, what is uncertain and which colleague can clarify it. A handover then becomes an informed next step rather than a fresh investigation.
- Recent interactions in the record context
- Next-action information alongside the history
- Permission-aware access
A concrete workflow
Identify the right customer
Open the contact or company involved in the interaction instead of creating a detached note.
Record what actually happened
Choose the appropriate channel and occurrence date, then describe the request or agreement in factual language.
Review administrative changes
Check whether ownership, contact details or deal information changed after the interaction.
Prepare the next handover
Leave a concrete next-action note so the next responsible colleague knows what remains open.
An illustrative working example
Illustrative workflow: a customer changes their brief
A design studio receives a phone request to reduce a project’s scope. The account manager logs the request against the customer and updates the next follow-up. Later, the deal details are revised. A colleague preparing the next conversation can distinguish the customer’s recorded request from the subsequent field changes. They can ask the right question about the revised scope without treating an internal adjustment as an already accepted agreement.
Questions about this topic
Is activity history the same as change history?
No. Activities describe customer interactions such as calls or notes. Change events describe actions on the CRM record, including the actor and affected fields.
Can I record when the conversation occurred?
CRM activity includes an occurrence date. This helps distinguish the actual interaction from the time somebody entered or updated information.
Does history give everyone access to the customer?
No. History is shown in the record’s access context. The current person still needs the appropriate permission to read the customer and related material.
Does a deal-stage change prove customer acceptance?
No. A stage change is an internal record event. Review the customer communication and any relevant quotation or document before relying on an agreement.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
