Pipeline Design
Part of CRM adoption and operating routines
Defining what must be recorded after a customer conversation
Set a post-conversation recording rule for changed decisions, uncertainty, commitments and the next owner.
Require an update when a conversation changes customer work. Record the relevant decision or request, what remains uncertain, any commitment and who acts next. The rule should help another person continue the work without turning every conversation into a transcript.
Decide when an update is needed
Ask: Would another person act differently if they knew what was said? A changed scope, customer decision, promised response or reason a deal must wait usually warrants an update.
A greeting that changes nothing may need only the activity record required by the team’s process.
Attach the change to the intended customer and work item. If two proposals were discussed, distinguish them.
A useful update filed against the wrong opportunity can misdirect the next person.
Specify the information to carry forward
For a conversation that changes open work, agree on four elements:
- What changed:the customer’s request, answer or decision, distinguished from the salesperson’s interpretation.
- What remains open:a question or dependency, with unconfirmed details left uncertain.
- What was promised:the response or deliverable the customer expects.
- Who acts next:a responsible person and a due date or justified review point.
These are information requirements, not four mandatory CRM fields. Record a completed interaction accurately and assign future work through the team’s task process.
Check that both point to the intended record.
For example, a customer may ask for a revised service scope while its purchasing team has yet to review the proposal. Record the requested revision, the unconfirmed approval and who will send the revision.
Do not turn an assumed approval date into a customer commitment.
Keep detail proportionate
If an approved proposal holds the full scope, the CRM update can identify its version and the material change.
Avoid copying an entire email thread or irrelevant personal detail into a free-text note.
For an organisation subject to the Australian Privacy Principles, collection of solicited personal information other than sensitive information must be reasonably necessary for its functions or activities. Sensitive information has additional conditions.
If an urgent promise is passed outside the CRM temporarily, assign someone to reconcile it with the intended record.
To check the rule, ask a colleague who missed the conversation to find the change, open question and next owner. If they cannot, inspect the rule, record link and access before requiring longer notes.
Privacy considerations under Australian Privacy Principles
- Collection of personal information
- Must be reasonably necessary for functions or activities
- Proportionality rule
- Avoid copying entire email threads or irrelevant personal detail
