Adoption is the difference between a CRM you pay for and a CRM you use. We train each role in your company on the few tasks it does every day, then measure usage weekly and coach the gaps until the habits hold. Sessions are remote and recorded.
Training by role
Each role gets its own session, built around its own daily tasks. Nobody sits through screens they will never open.
| Role | What they learn |
|---|---|
| CSR / call taker | Find or create the customer, pick the job type, capture the required fields, book the visit, log the source |
| Dispatcher | Assign and reschedule, read equipment history before sending a tech, handle emergency priority |
| Technician | Arrive, record equipment and photos, note findings, flag replacement opportunities, close the job |
| Comfort advisor | Build and send the estimate, work the follow-up tasks, record outcome and lost reason |
| Manager / owner | Read the weekly reports, run the quote review, spot data gaps |
The content comes straight from your CRM blueprint, so training and setup always match.
What the service includes
- Role sessions, remote and recorded, using your own CRM with test records.
- One-page checklists for each role, written in plain language.
- Weekly usage checks for an agreed period: required fields completed, tasks closed on time, estimates with next steps.
- Short coaching notes to managers when a person or team is falling behind.
- A new-hire kit: recordings, checklists and a first-week review routine.
Who it's for
This suits any HVAC company launching a new CRM, rolling out a changed setup, or rescuing a system people have quietly abandoned. It is particularly useful when:
- the office uses the CRM but technicians don't;
- each advisor tracks quotes differently;
- a few power users do all the data entry for everyone else;
- previous training happened once, at launch, and was never repeated.
How adoption is measured
We measure behaviour, not attendance. Typical weekly checks:
- share of jobs closed by the technician in the CRM, rather than by the office afterwards;
- share of new calls with source and job type filled in;
- estimates with a next-step date;
- overdue tasks per person;
- time from job completion to invoice.
When a number stalls, we look at the screen involved before blaming the person. Often a field is in the wrong place or a step is unnecessary.
What a role session looks like
A technician session, for example, runs like this. We open the CRM on a phone, using a test customer. The tech finds today's job, marks arrival, adds the furnace to the site record with a photo of the rating plate, writes a finding, flags a replacement opportunity, and closes the job. Then they do it again on their own while we watch, and the questions that come up become the checklist.
Office sessions follow the same pattern: a real-looking call, start to finish, then repeat without help.
The internal champion
Every rollout needs one person inside your company who answers daily questions. It is usually an office lead or service manager, not the owner. We train the champion first and in more depth, and they become the person who keeps the habits going after our weekly checks end. Choose someone patient who already knows how the shop runs.
Timeline
Training follows configuration and import, because people should learn on the real setup with real-looking data. A typical rollout is: managers first, then office roles, then field roles, then a period of weekly checks. Dates are set in your proposal.
Mistakes to avoid
- Training before the setup is finished. People learn the wrong screens and then unlearn them.
- One big session for everyone. Techs tune out the office content and vice versa.
- No owner inside the company. Pick one internal champion who answers day-to-day questions.
- Measuring logins. Logging in isn't using it. Measure completed fields and closed tasks.
- Letting the owner opt out. If the owner asks for reports by text instead of reading the CRM, everyone notices.
The 90-day adoption plan guide sets out the full sequence week by week. Questions about scope are welcome on the contact page, and costs are on the pricing page.
Frequently asked questions
Is training in person or remote?
Sessions run by video with screen sharing and are recorded for new hires, and consultations can be in person or by video call. The format and schedule are written into your proposal.
How long are the sessions?
Short. Most role sessions run under an hour, focused on the five or six tasks that role does every day. Long sessions get forgotten; short ones followed by real use stick.
Our technicians hate paperwork. How do you get them on board?
Keep their part small and useful. Techs usually need to confirm arrival, record equipment, add photos and close the job. If the CRM saves them a call to the office, they'll use it.
What happens when we hire someone new?
They watch the recorded session for their role, work through a short checklist, and their first weeks of entries get a quick review. We leave you with the recordings and the checklists.