CRM means customer relationship management: organising work with customers and prospects. To assess a system, ask whether the next person can understand the recorded history and what needs attention.
What a relationship record can organise
Salesforce’s CRM guide describes storing contact information, tracking sales opportunities and recording service issues.
HubSpot’s documentation calls individual items records, stored fields properties, and links between records associations. Its contact records can hold details and logged emails; notes and tasks hold context and planned actions.
The software is one part of how you manage the relationship. Decide who records a conversation, where an update belongs and who checks unresolved information. Give a field or dashboard a clear purpose in that work, so another person knows how to use it.
A fictional change in customer preference
Imagine a fictional picture-framing studio. An earlier note requests oak; a later message requests black. The team proposes to keep the latest preference and the earlier context, with finish availability still to confirm. The following entries describe that chosen record.
| Record item | Proposed content | Source or unresolved check |
|---|---|---|
| Latest request | Black finish requested. | Later message; availability unconfirmed. |
| Earlier context | Oak finish discussed. | Earlier note retained. |
| Next action | Check finish availability. | Staff member to confirm. |
Keep the earlier statement available for context, and ask about any unresolved conflict before presenting a field value as confirmed.
Check what reached the record
Follow a sample interaction from its source to the record. Check what was captured, which related record it appears on and whether the person handling the handoff can find it.
During that review, identify which information someone entered and which arrived through a connection. Check the chosen setup rather than assuming a message was saved because it was sent. If an update is missing, establish the cause before asking a colleague to rely on the history.
Agree who corrects an inaccurate entry and how a colleague can see the basis for the correction. Keep a reported customer statement distinct from a staff member’s interpretation. When using a clearly marked test record, compare the intended record with what is actually available to the relevant user.
CRM and CDP
The CDP Institute’s 2026 definition emphasises a persistent unified customer record available to other systems, with responsibility for maintaining customer identity and record structure.
Compare the actual relationship-work and data-sharing requirements. The names alone do not establish which capabilities a particular product includes.
Choose from the work you need to support
Salesforce also includes implementation, training and customisation in its explanation of CRM costs.
List the records and actions your team needs, who will use them and what must connect to them. Ask a prospective supplier to demonstrate that workflow in the relevant plan. Include migration and ongoing upkeep in the decision rather than choosing from a feature count alone.
If you use reports, state which recorded facts they summarise. Check missing records and changes in field meaning before interpreting a difference as changed customer behaviour. A tidy dashboard still needs a clear basis for its totals.
Review the next handoff
Pick a record another team member needs to use. Can that person identify the current customer statement, its source, the earlier context and the next unanswered question? Use any gap to decide what to correct or clarify before the next conversation.
For an individual opportunity’s stage, owner and next action, see Pipeline. The broader CRM record can hold the context used during that work.
Sources
Salesforce supplies the general CRM explanation; HubSpot supplies the product examples; the CDP Institute supplies its definition.