The Post-Move Follow-Up Sequence That Actually Produces Referrals

Most referral programs fail on timing rather than content. The ask is fine; it just arrives once, at a moment nobody chose deliberately, and then never again. Here is the actual cadence Snoball runs for moving companies — the days, the handoff point, and the decision rules — specific enough that you can rebuild it yourself.

Key Takeaways

• Day 1, day 8, day 21, day 45 — four automated touches after the job, spaced to survive being ignored.
• The goal of the sequence is a reply, not a referral — the referral comes out of the conversation that follows.
• The first reply is the handoff — automation opens, a person takes over and never gives it back.
• Follow-up timing comes from context, not the calendar — “moving in a couple months” means check back in one.
• Default to a check-in every two to three months — no conversation gets abandoned, no one gets nagged.

The four touches

The sequence runs on days 1, 8, 21, and 45 after the job completes. Four touches, front-loaded and then spreading out.

The spacing is doing specific work. Day 1 catches the customer while the experience is still vivid — the crew, the care taken, the relief that it went well. Day 8 catches them after they have unpacked enough to have an opinion, which is a different and often more considered state. Day 21 and day 45 exist because most people ignore the first two, and being ignored twice is not evidence that someone will not refer. It is the normal shape of the thing.

That is the piece worth internalizing. On average it takes three to four touchpoints before a first referral arrives. A program with two touches is not a small version of this — it is a program that structurally cannot reach the average. If you take one thing from this article, extend your sequence to four.

The goal is a reply

Here is the design decision that separates this from a typical drip: the sequence is not trying to produce a referral. It is trying to produce a response.

That changes what the messages should say. Message copy optimized for a referral asks for a referral, four times, in slightly different words. Message copy optimized for a reply asks something answerable — how the move went, whether anything needs following up, whether they would recommend the crew. It leaves an opening rather than making a demand.

Once the customer responds, the automation’s job is finished and it does not resume. A person takes the conversation from there, and from that point on the exchange is unscripted.

This is where the value in the whole system actually lives. Snoball’s clearest example is a conversation that ran ten messages deep, in which the customer had already left a review and recorded a video testimonial, and had mentioned in passing weeks earlier that his son was planning to move. The follow-up asked specifically about the son — and surfaced that the customer himself now needed to move. A repeat job appeared because someone asked a question narrow enough to be worth answering honestly. No sequence generates that message.

The decision rules after the handoff

“A person takes over” is not a plan. The person needs a playbook — a set of if-this-then-that rules that make the response consistent without making it robotic. The core ones:

Positive sentiment, no review yet. Ask for the review or a video testimonial right there. This is the single highest-yield rule in the playbook. Asked inside a warm exchange, review requests convert to five stars at a high rate; asked cold, they mostly do not.

A future date gets mentioned. Someone says their family is moving in a couple of months. Do not pitch. Set a reminder for one month out and ask about that specific person by name.

The contact is a referral partner. A realtor, apartment manager, or storage operator gets offered something useful — a personalized flyer with their name and a QR code they can hand to their own clients. Giving before asking is what separates you from the other vendors competing for their attention.

No specific reason to follow up. Default to a check-in every two to three months, indefinitely. This is how you catch the customer who moved with you years ago and is now back in the market.

They ask you to stop. Remove them immediately, no retention attempt. The whole model depends on people believing a real person is reading, and the fastest way to disprove that is to ignore the one request that is unambiguous.

Layering CRM triggers on top

Beyond the post-job sequence, most CRMs can fire messages on dates you already have: a birthday, the anniversary of the move, a nine-month check-in for a customer who was renting and may be buying soon.

These are cheap to set up and they work, with one condition. The trigger opens the conversation; a person still has to catch the reply. An anniversary message that goes unanswered when the customer writes back is worse than no anniversary message, because you have now demonstrated that the outreach was never really addressed to them.

That condition is the through-line of the entire cadence. Every automated element here exists to start conversations at a scale and consistency no person could sustain by hand. Every valuable outcome comes from what a person does after someone replies. Build the four touches this week — that part is straightforward. Then answer honestly who is reading the responses, because that is the half that determines whether any of it produces anything.

For the numbers behind this cadence, see our referral benchmarks for moving companies and why automations need a driver. On the timing of the ask itself, when to ask for a referral.

Cadence and playbook detail from Snoball CEO Landon Taylor, August 2026.