Getting your team to use the CRM: a 90-day adoption plan

Before day one: three decisions

Three things need to be settled before anyone is trained.

1. The setup is finished. Fields, stages and job types are agreed and configured, as described in the fields and stages guide. Training people on a system that will change next week wastes their goodwill.
2. The data is in. Customers, sites and equipment have been imported and checked, following the import guide. People judge a CRM the first time they search for a customer they know.
3. There is a champion. One person inside the company, usually an office lead or service manager, who answers daily questions and is trusted by both office and field staff.

Pick a launch date in a shoulder season if you possibly can. For most Canadian heating companies, that means avoiding the first cold weeks of the year.

Weeks 1–2: champion and managers

Train the champion first, and in more depth than anyone else. They should be able to do every role's daily tasks and fix small problems, such as a misfiled job or a duplicate customer.

Then train the owner and managers on the views they'll use: open estimates, today's jobs, overdue tasks, maintenance visits due and calls by source. Agree on one rule above all: managers ask for updates by looking at the CRM, not by asking people. This is the habit that pulls everyone else in.

Weeks 3–4: office roles

Train CSRs and dispatchers next, in separate short sessions built around their daily tasks.

• CSRs: search by phone, create or find the site, choose the job type, complete required fields, book the visit.
• Dispatchers: assign, reschedule, check equipment history before sending a tech, handle emergencies.

Each session should end with the person doing a full scenario alone, start to finish, on a test record. From the first day live, the office works only in the new system. Keep the old one read-only so nobody slips back.

Weeks 5–6: technicians and comfort advisors

Field staff come in once the office is steady, because they need the office to be feeding them good jobs.

• Technicians: open today's job, mark arrival, check history, record equipment with a rating-plate photo, note findings, flag replacement opportunities and close the job. Keep it to the handful of steps they repeat on every call.
• Comfort advisors: build and send quotes, work their follow-up tasks each morning, and record outcomes and lost reasons.

Ride-along style training doesn't need to be in person. A short video session where the tech shares their phone screen while working through a test job does the same work.

Weeks 7–12: measure, fix, repeat

From launch onward, check a few numbers every week and share them with the team.

When a number stalls, look at the screen before blaming the person. Often a required field asks for something the person doesn't know, or a step takes too many taps on a phone. Fix those, announce the change, and watch the number again.

Handling resistance

Resistance is normal and usually reasonable. Common forms and what helps:

• "It's slower than the old way." Time it. If it really is, simplify the screen. If it isn't, show them the timing.
• "I don't have signal in basements." Check how your CRM handles weak connections and teach the workaround, such as completing notes after leaving the site.
• "I already know my customers." Fine, but the next hire doesn't. Equipment history protects the company, and the tech, when people move on.
• "The office will fix it anyway." Stop the office fixing it. If the office keeps cleaning up after the field, the field never changes.

Praise in public using the numbers. A short note in the weekly meeting about the tech with the most complete equipment records costs nothing and works.

The owner's role

The owner decides the outcome more than any setting. Three habits matter:

1. read the CRM's views instead of asking for updates;
2. run a 20-minute weekly review of open estimates from the CRM;
3. refuse side spreadsheets once launch is done.

If the owner keeps a personal quote list in a notebook, everyone else will too.

After day 90

By the end of the third month, the weekly numbers should be holding without prompting. Move to a monthly check, keep the champion as the first point of contact, and give every new hire the recorded session for their role plus a short checklist. Review the blueprint once a quarter and make changes deliberately, with a note to everyone affected.

A one-page adoption scorecard

Print or pin a simple scorecard for the first 90 days. Each week, fill in the five measures from the table above, mark each as improving, flat or slipping, and write one sentence on what will change next week. Share it at the Monday meeting. The scorecard keeps the rollout visible, gives the champion something concrete to report, and makes it obvious when the job is done.

Common mistakes

• training everyone in one long session;
• launching before the import is checked;
• measuring logins instead of completed work;
• letting the old system stay writable;
• treating launch day as the end of the project.

If you want help running this plan, see the training and adoption service. For the reminder and follow-up habits that depend on good adoption, see maintenance reminders and estimate follow-up.