A customer had a good move. The crew was on time, the estimate was accurate, nothing was damaged. The customer would refer you to their neighbor who’s moving next month. They don’t, because nobody asked, and the moment passes. Six weeks later the neighbor hires your competitor.
Happy customers don’t refer unless asked. Asking is manual — somebody on your team has to remember to send a text, track who responded, track who actually booked, and track whether the referral payout is owed. At 50 jobs a month, nobody does this. The referrals that would have happened don’t.
The Snoball Integration
In August 2026 (Changelog_2608.md !2244), MoveRight shipped a Snoball referral integration that automates the entire loop. Here’s how it runs.
Completed moves auto-post to Snoball
When a move completes, MoveRight automatically posts to Snoball’s Zapier webhook. The payload includes the customer’s contact information, the job’s zip code, and the sales rep name (the estimator is used as the sales rep). Snoball receives the payload and triggers its own outreach flow — SMS and email asking the past customer to refer friends who are moving.
No human at your company touches it. The move completes, the system fires, Snoball asks. The customer who would have referred you if someone had asked gets asked — every time, on every completed move, without exception.
When a Snoball-referred job invoices, a payout fires
The loop closes on the back end. When a job that came in through a Snoball referral invoices, MoveRight sends a payout event to Snoball so Snoball can pay the referrer. The payout fires when the job invoices — not when it books, not when it completes, when it invoices. That’s the moment the revenue is real and the referral is worth paying for.
Per-zone webhook configuration
The Snoball webhook URL is configured per zone via snoball.webhookUrl. There’s no hardcoded default. Each franchise territory can point at its own Snoball account, or the whole network can share one. A 30-location franchise with a single Snoball contract and a single zone config change can turn referral automation on for every location.
Idempotent: No Double-Posts
The integration is idempotent. That word gets thrown around. Here’s what it means in practice.
MoveRight uses a reserve-then-confirm tag pattern. When a move completes, the system reserves a tag on the job — “Snoball Sent” — before posting to the webhook. The event ID is deterministic, derived from the job and the event type, not a random UUID. If two executions fire concurrently (a bug, a retry, a replay), both compute the same event ID. The second one sees the tag is already reserved and exits without posting. The customer gets one referral request, not two.
If the execution is replayed — a queue retry, a manual re-run, a deploy that reprocesses the backlog — the same thing happens. The deterministic event ID matches the already-reserved tag. The post doesn’t fire again. Snoball doesn’t see a duplicate. The referrer doesn’t get paid twice.
This is not a nice-to-have. A referral integration that double-posts under concurrent execution or queue replay is an integration that sends a customer two “refer your friends” texts on the same day. That’s worse than not asking at all.
The YMM-Toledo Pilot
The integration went live first for the YMM-Toledo pilot zone. Toledo was the test bed — a single franchise, a single Snoball account, a single webhook URL configured in the zone. The pilot validated the idempotency model under real job volume before the integration was offered to the broader network.
The pilot surfaced the payload improvements that shipped in the same release cycle. The Snoball Zapier payload now includes the customer’s zip code and the sales rep name (!2244). Earlier versions sent only the customer name and contact info — which meant Snoball couldn’t route the referral to the right franchise territory or attribute it to the right sales agent. The zip code lets Snoball’s routing logic work. The sales rep name lets you track which estimator’s customers refer the most.
Why Referrals Are the Highest-ROI Channel for Movers
Referral leads close at a rate no other channel matches. A customer who was referred by a friend already trusts you before they call. They’re not comparing five quotes on Google. They’re not reading reviews to decide whether you’re legit. They’re calling because someone they trust told them to.
The cost of acquiring that lead is the cost of asking — which, with the Snoball integration, is $0 in labor. The system asks every completed customer, every time, automatically. The payout only fires when the referred job invoices, so you’re paying for referrals that actually generated revenue, not for introductions that didn’t go anywhere.
Compare that to Google Ads (you pay per click whether the lead books or not), lead providers (you pay per lead whether it closes or not), or SEO (you pay an agency whether you rank or not). Referral is the only channel where you pay after the revenue is confirmed.
How to Turn It On
Configure snoball.webhookUrl in your zone settings. Completed moves start posting. Snoball starts asking. When a Snoball-referred job invoices, the payout event fires. That’s it.
If you don’t have a Snoball account, the integration won’t do anything — there’s no hardcoded fallback. You need a Snoball account and a Zapier webhook URL. MoveRight handles the trigger and the payout event. Snoball handles the outreach and the referrer payment.
MoveRight is the moving company CRM that automates the referral loop — trigger on completion, payout on invoice, idempotent under concurrent execution — because the highest-ROI channel for movers is the one nobody asks for.
References:
- August 2026 Changelog — !2244 — Snoball referral integration, idempotent reserve-then-confirm pattern, per-zone webhook config, YMM-Toledo pilot
- Moving Company Reviews: How to Get More 5-Stars and Win More Jobs — the reputation foundation that makes referral outreach convert
- Why MoveRight Is the Easiest Moving Software to Use — how we remove manual steps from every part of the post-move workflow, including referral outreach