Your team won't use software they don't trust. We train every role — dispatchers, CSRs, and field techs — until it sticks.
The most expensive line item in any failed CRM implementation isn't the software — it's the trained team that reverted to doing things the old way. We fix adoption before it fails, with role-specific training built around your actual jobs, your actual dispatch board, and your actual customers.
The real reason CRM implementations fail
The software isn't the problem. Adoption is.
A perfectly configured OpenClaw account with no trained team is a $400/month bill that runs at 15% capacity. The dispatch board shows jobs nobody updates. The mobile app nobody opens. The automations that trigger but nobody responds to.
CRM implementations fail at the human layer, not the technical one. And they fail in a specific way: generic group training that covers everything superficially, so nobody finishes with deep confidence in the tasks they personally need to do every day.
Your dispatcher doesn't need to know how to collect field payment. Your field tech doesn't need to know how to configure reporting dashboards. They each need two hours of training that covers exactly their workflow and nothing else — and they need to practice it on real jobs before they're doing it alone.
What happens without role-specific training
-
Techs revert to paper tickets. The mobile app feels unfamiliar on a job site. The customer's watching. The tech scribbles on paper and says he'll enter it later. He doesn't.
-
Dispatchers build shadow spreadsheets. The OpenClaw dispatch board gets used for booking but a parallel Google Sheet tracks "what's actually happening." Two sources of truth means zero reliable data.
-
CSRs skip the booking workflow. Inbound calls get handled by phone and entered into OpenClaw after the fact — if at all. Notes don't get captured. Lead sources aren't attributed. Follow-up automations never trigger.
-
The owner stops looking at reports. The dashboard shows data nobody trusts. Decisions go back to gut feel and phone calls to the dispatcher.
Who this is for
Built for plumbing companies at the point of go-live
Training is included in every OpenClaw implementation sprint. But it also works as a standalone engagement if your team is already live on OpenClaw but adoption has stalled.
Going live in Week 3
You're completing the RacingMinds sprint. Week 3 is training week. Your dispatchers, CSRs, and field techs get role-specific sessions before your Monday go-live so nobody is learning on the job.
Included in sprintAlready live, adoption has stalled
You're 60–90 days into OpenClaw and the team isn't using it correctly. Techs are back on paper, dispatchers have their spreadsheet, and the software isn't doing what you paid for it to do.
Standalone trainingNew hires who missed original training
You have a new dispatcher or two new techs who joined after the initial training. The recorded sessions help — but you also need someone to answer questions and run a quick live simulation for the new team members.
New hire onboardingRole-specific training modules
Four roles. Four dedicated sessions. Nothing generic.
Every session is built specifically for the role. Dispatchers and field techs never sit through the same training — their workflows are completely different and training them together wastes everyone's time.
What dispatchers learn
Reading and managing the dispatch board
Understanding job status colors, tech positions, schedule gaps, and how to prioritize competing jobs when the board gets busy.
Creating jobs and assigning technicians
Creating jobs from new calls, from inbound leads, and from CSR-booked appointments. Assigning the right tech based on skill match, zone, and availability.
Zone routing and travel time optimization
Using OpenClaw's routing tools to minimize drive time, batch nearby jobs, and keep techs in their primary zones while covering overflow intelligently.
Handling reschedules, cancellations, and no-shows
The exact workflow for each scenario — updating job status, notifying the customer, reassigning the tech, and filling the open slot.
After training, your dispatchers can
What CSRs learn
Inbound call scripts within OpenClaw
How to open a new call, search for an existing customer, pull up their service history, and navigate the booking flow — all while staying on the phone naturally.
Capturing customer info and booking appointments
Creating new customer records correctly, capturing the right fields, selecting the right job type, and booking into the dispatch board without double-booking or leaving gaps.
Callbacks and follow-up handling
Managing callback queues, ensuring missed calls get followed up, and using OpenClaw's task and note system to make sure nothing falls through.
Escalating emergencies
The exact steps for an emergency call — how to mark the job as emergency priority, how to notify the dispatcher, and what to say to the customer while a tech is being assigned.
After training, your CSRs can
What field techs learn
Mobile app — job acceptance and navigation
Seeing their daily schedule, accepting jobs, navigating to the customer's address, and marking their status so the dispatcher always knows where they are.
Capturing photos and job notes
Taking before and after photos, adding notes that protect the business in disputes, and logging parts and time on the job — from the field, not the office.
Collecting payment in the field
Running cards, recording checks, processing deposits, and confirming the invoice is sent — so the job is fully closed before the tech leaves the driveway.
Closing the job and requesting reviews
Marking the job complete, triggering the automated review request, and closing the loop with the customer — the right way, every time.
After training, your field techs can
What office managers learn
Reporting dashboards and KPI review
Reading the weekly dashboard — jobs completed, revenue by tech, open invoices, quote close rate — and knowing what numbers to watch and what they mean.
Job cost review and invoice reconciliation
Reviewing job profitability, reconciling invoices against QuickBooks, managing outstanding balances, and catching billing errors before they become disputes.
Managing tech schedules and availability
Adjusting tech availability, managing PTO and sick days in the dispatch board, and ensuring schedule changes don't create gaps the dispatcher doesn't see.
User management and settings ownership
Adding and removing users, managing permissions, updating service catalog pricing, and handling the day-to-day configuration changes that don't need an outside consultant.
After training, your office manager can
Training format
How training is delivered
Every element of the training format is designed to maximize retention and ensure your team can perform independently — not just follow instructions while someone watches.
2-hour role-specific sessions
Each session covers only the tasks relevant to that role. Dispatchers train with dispatchers. Techs train with techs. Nobody sits through content that doesn't apply to their job, which keeps engagement high and retention higher.
Recorded for new hire onboarding
Every session is recorded and delivered to you at the end of the sprint. New hires watch the role-specific video before their first shift. The quality of onboarding doesn't degrade over time as the original team moves on.
Written SOPs per role
Each role gets a written standard operating procedure document covering every common workflow. SOPs live in your shared drive. When your dispatcher is out sick and a temp covers, they're not starting from nothing.
30-day post-launch Slack support
A dedicated Slack channel for 30 days after go-live. Questions answered same business day. Edge cases handled in real time. Your team never gets stuck on a scenario they weren't trained for without a fast path to resolution.
Training that sticks
Why we use live simulations instead of demo data
Most CRM trainers work in demo accounts with perfect, fictional data. We train on your live system with your real jobs. The difference in adoption is significant.
Live dispatch simulations with real jobs
Before go-live, we run a full dispatch simulation using real jobs from your recent history. Your dispatcher sits at the live board. Your techs use their actual phones. We call out scenarios — emergency job comes in, tech goes off-road, customer calls to reschedule — and the team handles them in real time.
When a dispatcher encounters the same scenario on their first real shift, it isn't new. They've seen it before. The muscle memory is there.
SOPs matter more than training videos
Training videos teach people how to use software under ideal conditions. SOPs tell people exactly what to do in specific, messy, real-world situations — when the customer calls back 20 minutes after booking, when a tech marks a job complete but the invoice isn't closed, when a recurring job auto-schedules on a holiday.
We write SOPs for the edge cases, not just the happy path. Those are the ones your team will actually reach for.
Training the "what's in it for me" angle
Tech resistance to CRM apps isn't about the technology — it's about trust and self-interest. We spend time in every field tech session explaining why using the app correctly makes their job easier: no more "the office doesn't have my parts order," no more disputes about whether a job was done, faster close-to-payment cycle.
Techs who understand the personal benefit adopt the app. Techs who are just told to use it don't.
Repetition before independence
No role goes live after a single walkthrough. Every session includes practice repetitions on real scenarios before the session ends. Dispatchers create at least five jobs and run a reschedule workflow. Techs complete a full job end-to-end. CSRs book from a live inbound call script.
Training ends when the team can do the task without prompting — not when the trainer finishes the agenda.
What you get
Everything included in the training sprint
Training is Week 3 of the full sprint — but these deliverables are produced and delivered regardless of whether you engaged us for the full implementation or standalone training.
4 role-specific training sessions (2 hrs each)
Dispatchers, CSRs, field techs, and office manager — each trained separately on their specific workflows.
Session recordings for every role
Full video recordings delivered after each session, organized by role, for new hire onboarding.
Written SOPs per role
One-page SOP documents covering every common workflow and the most frequent edge cases for each role.
Live dispatch simulation
A full end-to-end simulation run before go-live with real jobs, real scenarios, and the full team.
30-day post-launch Slack support
A dedicated channel for questions, edge cases, and troubleshooting for 30 days after go-live.
Rollout playbook
A go-live checklist and day-one guide for the owner and office manager to reference on launch day.
A CRM your team actually uses is worth 10x one they don't.
Book a 30-minute call. We'll look at your current team structure, tell you what training approach makes sense, and explain exactly what Week 3 of the sprint involves — whether you're starting fresh or rescuing an implementation that stalled.
What proper training changes
The numbers behind adoption
These reflect the operational differences between plumbing companies that received role-specific training versus those that received generic onboarding.
Frequently asked questions
Training questions answered
Your team won't trust software they were barely trained on.
Book a 30-minute call. We'll walk through your current team structure and tell you exactly what a training engagement looks like for your specific roles, dispatch volume, and go-live timeline.