CRM adoption and operating routines

Make CRM use part of the customer work people already do. Agree what the next colleague must find, when a record changes, who updates it, and how exceptions are resolved. Logins prove system access, not that a customer commitment has an owner.

Set the handover standard

Choose the moments when a record matters: an enquiry is accepted, a conversation changes a proposal, an opportunity needs a decision or an account changes hands. For each moment, ask the person receiving the work what they need to know and do.

An open sales item generally needs the intended customer and work item, a responsible owner, the current position, and a next action or review point. A closed item needs an accurate outcome. Leave an unconfirmed decision date or buyer role uncertain, with someone responsible for resolving it when necessary. The exact fields depend on the work and the CRM.

CRM Record Requirements by Handover Moment

Attach updates to the work

Whoever makes a customer commitment should record it before the next handover. An opportunity owner should update a changed proposal on the relevant deal. Before a review, owners should check the records the group will discuss. After the review, name who will correct each agreed exception.

Some work cannot be entered immediately. Agree on a temporary route for an urgent commitment and who will reconcile it with the CRM. If staff keep the same open work in a private spreadsheet, find out why both steps exist and which record is authoritative. Training can explain a useful routine; it cannot remove duplicate entry.

Review decisions and friction

Use group reviews to settle customer and process questions. Ask what event supports a deal's current position, what remains uncertain and who will act next. Discuss a shared recording rule with the group; handle individual coaching and sensitive account details privately.

When the same gap recurs, inspect the work behind it. An unclear rule, inaccessible screen or missed handover may call for a process change. Give the change an owner and check the affected task with the people who use and receive the record.

Pros and Cons of Using CRM vs. Private Spreadsheets

Build a feedback loop around changed work

When introducing a changed process or training people in a new routine, make feedback part of the follow-up. Gather it through surveys, interviews or direct observation of training sessions. These methods help the team hear how users are reacting and assess the outcome of training.

Look for resistance, hesitation to adopt the process and skill issues, including where these occur across particular user groups or processes. Treat these signals as prompts to investigate what is making the work difficult, rather than assuming that a missed CRM update is simply a matter of effort.

Analyse the issue before choosing a response. If the training approach does not match the difficulty, adapt the model to the level of risk; the response may differ for a group that needs more practice than for one facing a process obstacle.

For a high-risk user group or process, consider hands-on, in-person training from a supervisor or another trusted person. Reinforcement, encouragement and support that empowers users may also help address the risk. Check the relevant task with the people doing it and receiving its output.

If difficulties are severe, options include transferring responsibility to another user group or acquiring a larger skill set. Use what feedback reveals to decide whether the routine, its training or the allocation of work needs attention, then check the affected process again.

Feedback Loop for CRM Adoption Improvement

Check whether the records help

Select a defined population, such as open opportunities due for review this week. Check whether a colleague can identify the customer, current position, owner and next action. Record unresolved exceptions alongside the share that meets the local standard, and keep the population and rule with each result.

Compare roles and periods only when the work and eligibility rules make that comparison meaningful. Also check whether the customer commitments or next actions due in that population were completed, so the review tests whether CRM use helps move the work forward.

For organisations subject to the Australian Privacy Principles, the recording rule should account for limits on collecting personal information. A larger note is not automatically a better record.

For an organisation covered by APP 3, collection of personal information must be reasonably necessary for its functions and activities. Sensitive information has additional requirements: collection must meet those conditions and have the individual's consent unless an exception applies, and information must be collected by lawful and fair means.

Compliance and Record-Keeping Requirements (ATO & APP 3)