Part 1 covered lead routing, AI zone mismatches, negative discounts, photo sync failures, and revenue reports that lose booked revenue on rescheduled jobs. If you missed it, start there.

Part 2 is where most CRMs really fall apart: dispatch and reporting.

#6 — Drag-and-Drop Reschedules That Don’t Tell the Customer

A dispatcher drags a job from Thursday to Friday on the calendar. The job moves. The crew gets reassigned. The system updates internally. The customer? They have no idea until Thursday night when nobody shows up.

This is one of the most common dispatch complaints in the industry. The CRM handles the operational side — crew reassignment, calendar update, truck reallocation — but it doesn’t trigger an automated text or email to the customer confirming the new time.

The fix is straightforward: every reschedule triggers an automated customer notification. Not optional. Not a checkbox. Automatic. If you move a job, the customer finds out immediately. No exceptions.

#7 — Crew Payroll Calculations That Miss Tip Splits and Stair Pay

The foreman gets a different payroll number than the office. Not because of malice — because the CRM calculates crew pay differently than the payroll system. Common gaps:

Tip splits — Customer tips $100. The foreman reports it. The CRM doesn’t automatically allocate it across the crew. Or it does, but the allocation doesn’t match what the crew actually received.
Stair pay / flight surcharges — These are supposed to be added per the estimate, but the crew app reports hours without surcharges, and the office doesn’t catch the discrepancy until payroll processing.
Overtime calculations — A 12-hour move on a Saturday has a different rate structure than a 6-hour move on a Wednesday. If the CRM doesn’t track actual clock-in/clock-out times per crew member, the payroll calculation is a guess.

The result: the foreman’s pay stub says one thing, the office says another, and someone spends two hours on Friday reconciling a spreadsheet that should have been automatic.

#8 — Reports That Double-Count Revenue When a Job Has Multiple Workorders

A 3-day long-distance move has three workorders: load day, drive day, unload day. Your monthly revenue report lists this job three times — once for each workorder. The total looks like $4,500 instead of $1,500.

This is the reporting version of the N+1 query we wrote about in our dispatch performance post. It happens when the report groups by workorder instead of by job. It’s invisible until the owner asks why booked revenue is 40% higher than bank deposits, and the accountant spends a week tracking it down.

The fix: reports should aggregate at the job level by default, with a secondary view at the workorder level for operational detail. Revenue belongs to the job. Workorders are operational units, not financial ones.

#9 — Calendar Views That Lie About Availability When Crews Are on Long-Distance Jobs

A crew is assigned to a 3-day long-distance move: Monday, Tuesday, Wednesday. On the dispatch calendar, that crew shows as “busy” on Monday and Tuesday — but Wednesday is “available” because the workorder ends Tuesday night.

Except the crew isn’t back until Wednesday evening. They’re driving back from Chicago. They can’t take a local move on Wednesday morning.

The dispatcher sees an available crew on Wednesday and books a job. Now they have to unbook it or fly a different crew in. Either way, it’s a mess.

The fix: workorders need start and end dates (including travel time), not just service dates. The calendar should block the crew for the full span of the workorder, including return travel. If the system can’t calculate travel time automatically, it should at least let the dispatcher specify “crew unavailable until X date.”

#10 — KPIs Without a Denominator

“Booked $150,000 this month.” Great. Out of how much lead value?

A KPI without a denominator is a vanity metric. Booked revenue of $150K means one thing if you had $200K in lead value (a 75% close rate) and something completely different if you had $600K in lead value (a 25% close rate). The first is a well-run sales floor. The second is a conversion problem disguised as a revenue success.

The denominator matters:

Connection rate = connected leads ÷ total inbound leads
Close rate = booked revenue ÷ total lead value
Average ticket = booked revenue ÷ number of booked jobs
Revenue per lead = booked revenue ÷ total number of leads

If your CRM gives you the numerator without the denominator, you’re measuring output without measuring efficiency. And you can’t optimize what you can’t measure properly.

The 6-Question Vendor Test (Revisited)

Take Part 1 and Part 2 together. That’s 10 questions, but these 6 are the ones that separate a functional CRM from a reporting disaster:

Does your dispatch board auto-notify the customer when a job is rescheduled?
Does your payroll calculation include tip splits and stair surcharges?
Do your revenue reports aggregate by job, not by workorder?
Does your calendar block crew availability for the full workorder span, including travel time?
Do your KPIs include denominators — connection rate, close rate, revenue per lead?
When a job is rescheduled across months, does your booked-revenue report track both booking date and service date?

Take Part 1 + Part 2 to your current vendor. Ten questions, ten answers. We’ll send you the PDF.

Get the 10-question checklist

References:

Capterra/Software Advice — SmartMoving reviews — https://www.softwareadvice.com/fleet-management/smartmoving-profile/
Movers Development — Best Moving CRM 2026 — https://moversdev.com/best-crm-software-for-movers/

Five More Things Your Moving CRM Is Silently Getting Wrong (Part 2: Dispatch and Reporting)