How a Mobile Repair Business Reactivated 2,000 Dormant Customers in 30 Days

This case study describes a 30-day reactivation exercise built around a mobile-repair customer database of 2,000 dormant records. It is a worked example of the method and the decisions, not a guarantee that another repair business will recover the same number of customers or revenue.

The important lesson is not the headline number. It is the discipline required before a message goes out: understand what each record means, choose a relevant repair or upgrade reason, separate channels and record objections.

The starting problem

The business had a familiar leak: customers who had previously paid for a repair were difficult to see once the original job was closed. The database contained names, contact routes and service history, but “dormant” mixed together several different situations:

• a customer whose device might fail again;
• someone who had bought a replacement elsewhere;
• a one-off visitor with no ongoing need;
• a record with an unclear permission or contact preference;
• a customer who had already asked not to be contacted.

Treating all 2,000 as one audience would have made the campaign easier to schedule and harder to defend.

Step 1: make the audience explainable

The first working table used fields the business could verify:

The ICO's electronic-mail guidance says marketing emails, texts and other stored electronic messages to individuals need consent or the limited own-customer soft opt-in. A phone number in a repair database is not a universal licence to send a campaign.

Step 2: choose a reason to return

The campaign did not begin with “we have a promotion”. It grouped customers around a reason the business could explain:

1. a likely maintenance or repair question;
2. a complementary service related to the original job;
3. a seasonal or practical device problem;
4. a simple invitation to ask whether help was needed.

If a segment could not support a relevant reason, it stayed out of the first cohort. That is a feature, not a failure.

Step 3: sequence contact without creating pressure

The 30-day plan used a deliberate order:

• Preparation: reconcile permission, deduplicate records and remove objections.
• First message: email or the recorded preferred channel, with one clear question.
• Follow-up: only for eligible non-responders and only when it added information.
• Conversation route: give the customer a way to reply to a person rather than forcing a booking form.
• Suppression: record a purchase, objection, complaint or invalid address immediately.

SMS or WhatsApp were not automatic “next touches”. They were separate channel decisions with their own permission and operational owner.

What the case study measures

The useful result table is wider than revenue:

The published case headline uses 2,000 records and 30 days. It should not be read as independent research, a typical benchmark or a promise. A repair business considering the method should substitute its own database, permissions, capacity and margin.

What changed operationally

The lasting improvement was visibility. The business could now see which records were:

• eligible for a defined message;
• waiting for a human answer;
• suppressed permanently or temporarily;
• linked to a service history;
• ready for a later, different reason to return.

That is more durable than one campaign. A reactivation programme should leave the database clearer than it found it.

What another repair business should copy

1. Start with one service category and a named owner.
2. Write the eligibility rule before writing the message.
3. Make the customer reason specific and honest.
4. Give every reply a human route and a response target.
5. Stop after an objection, complaint or completed job.
6. Measure completed work and margin, not only clicks.
7. Keep the case-study result separate from your forecast.

For the legal and channel detail, read email, SMS or WhatsApp reactivation. For the broader strategic choice, read database reactivation vs cold outreach.

FAQ

Can a smaller repair database use the same approach?

Yes, if the segment is explainable and the team can handle replies. Smaller volume does not remove the need for permission and suppression checks.

Is a dormant repair customer automatically eligible?

No. Recheck the original notice, consent or soft-opt-in conditions, product similarity and objections before contacting the person.

Do I need email, SMS and WhatsApp together?

No. Choose the channel the customer is eligible to receive and the team can support. Add another only for a clear reason.

What if the case result does not repeat?

That is normal. Use the case as a method, then measure your own eligible audience, response quality, completed work, margin and complaints.

If the database is full of “maybe” records and you need a safe first segment, Get unstuck.