Well Contractor Customer Reactivation Checklist

A dormant customer list is not one audience. A pump repair customer, a completed drilling customer, an unresolved complaint, and an old estimate need different decisions.

The safest reactivation process starts with the record, not the message. Verify the relationship, find a real service reason, check the contact path, protect crew capacity, and measure the result through booked work.

What should a well contractor customer reactivation checklist contain?

A useful checklist has five gates: record, reason, permission, capacity, and outcome. A record must pass all five before it becomes an active reactivation opportunity.

Gate	Owner decision	Pass condition	Stop or route condition
Record	Is this a real, identifiable past relationship?	Customer or account, service history, territory, and contact details are understandable.	Unknown source, duplicate, bad data, or no usable contact path.
Reason	Why should this person hear from us now?	A documented follow-up, relevant service, actual offer, or customer-requested next step exists.	Generic “checking in” with no service fit.
Permission	Can we use this channel for this message?	The company can show the channel and opt-out path are appropriate.	Missing SMS consent, opt-out, do-not-call request, or unclear email process.
Capacity	Can we answer, qualify, schedule, and complete the work?	Dispatch, field staff, geography, and service scope can absorb the response.	Backlog, unavailable crew, wrong territory, or unsupported service.
Outcome	How will we know what happened?	Each record has a disposition from delivered through completed job.	Replies live in personal phones, or all activity is counted as a lead.

This is the core operating artifact for the page. It gives an owner a yes-or-no decision before anyone writes a campaign. It also prevents a common failure: a well company sends an attractive offer, then discovers that the office cannot tell who replied, the crew cannot visit the territory, or the customer was already marked do-not-contact.

A customer reactivation campaign is a booked-work process with a message in the middle, not a message blast with a hope attached.

Which customer records belong in the first reactivation list?

Start with completed customers whose service history and current relationship are clear. Do not begin by exporting every contact the company has ever stored.

The first list should be narrow enough that someone in the office can explain why each record is present. A simple starting filter is:

1. The company performed a completed job, or the customer has an identifiable prior relationship with the company.
2. The customer or account is in a territory the company still serves.
3. The record identifies the service line or job type well enough to avoid a generic message.
4. The company has a current email, phone, or customer-requested contact path that can be used lawfully and operationally.
5. There is no do-not-contact, unsubscribe, STOP, complaint, or other suppression flag.
6. The company can explain a legitimate next step that it actually offers.

That filter separates a usable customer file from a historical database. A database contains names. A reactivation list contains decisions.

What fields should the contractor export?

Use one row per customer or account, with a linked job history when possible. The exact CRM names will vary, but the decisions should stay stable.

Field	Why it matters	Example values
Customer or account name	Prevents a message from going to an unidentified record.	Individual, farm, property manager, municipality, general contractor
Primary contact and role	Commercial accounts may have an owner, facilities contact, superintendent, or accounts-payable contact.	Owner, facilities manager, operations contact
Phone and email	Lets the office compare what is current with what was stored.	Current, unknown, bounced, disconnected
Contact source	Shows where the permission or relationship came from.	Completed job, estimate request, referral, website, association
Last completed job date	Separates recent follow-up from genuinely dormant history.	Date, unknown
Last invoice or payment status	Keeps unpaid or disputed work out of a promotional sequence.	Paid, open, disputed, unknown
Service line	Determines the message and routing rule.	Pump repair, pump replacement, drilling, inspection, rehabilitation, testing
System or equipment detail	Makes a message useful without pretending to know more than the record shows.	Submersible pump, pressure tank, well construction record, unknown
Site or service territory	Prevents a response from creating work outside the operating area.	County, state, service zone, commercial site
Job status	Distinguishes completed work, open work, canceled work, and complaint.	Completed, open, canceled, unresolved
Documented next action	Gives the campaign its reason.	Requested revisit, test due, follow-up requested, none
Channel status	Records email, call, SMS, or no-contact status.	Email eligible, SMS consent recorded, call restriction, unknown
Suppression reason	Makes exclusion visible and durable.	Unsubscribed, STOP, do-not-call, complaint, wrong number
Assigned owner	Prevents replies from becoming orphaned.	Office manager, dispatcher, estimator, service manager
Next action and date	Turns a response into a queue item.	Call back, schedule estimate, close record, review later

The Virginia WellCheck form is not a national CRM standard, but it is a useful public example of the information that can matter around a well relationship. It includes customer contact and well-location fields, referral source, customer concerns, well completion and maintenance records, last service date, water-test information, and pump details. Virginia Cooperative Extension and Virginia Water Well Association’s Well Checklist shows why a flat name-and-phone export loses context.

National Ground Water Association contractor guidance similarly discusses written scope, construction details, yield evaluation, disinfection, and the well construction record. Those records should not be copied into marketing casually, but they can help an owner decide whether a future conversation is technically relevant. NGWA’s contractor toolkit is a useful reference for the kinds of project records a company may already hold.

What should be removed before segmentation?

Remove or route records that cannot support a truthful, welcome conversation.

• Duplicate customer records that could receive two messages.
• Wrong numbers, bounced emails, and contacts with no verified current path.
• Records marked unsubscribed, STOP, do-not-call, or otherwise suppressed.
• Customers with an unresolved service complaint, warranty issue, unpaid dispute, or active escalation.
• Customers outside the current service territory.
• Jobs for a service the company no longer performs or cannot legally perform in that location.
• Records belonging to another company, acquired business, landlord, tenant, or former employee contact when the relationship is unclear.
• Open estimates that never became completed customers. Route them to the well drilling estimate follow-up sequence.

Do not silently delete suppressed records. Keep the suppression reason and date in a field that future campaigns can see. Deleting the row can make the same mistake happen again after the next export.

How should a contractor decide who is dormant?

Use the last completed job, last meaningful customer response, and next known service reason together. A calendar threshold by itself is too blunt for drilling and pump work.

For operating purposes, classify records into four states:

State	What it means	First decision
Active loop	The customer has a current job, open request, promised callback, warranty matter, or dated next step.	Continue the existing service or estimate workflow. Do not put the record in reactivation.
Warm past customer	The last job is known, the relationship is healthy, and a relevant service reason exists.	Prioritize for a specific, low-friction contact.
Dormant but usable	The company has a real past relationship, but no immediate next action is documented.	Contact only if the company can name a truthful reason and has capacity.
Suppressed or uncertain	Contact permission, identity, service fit, complaint status, or territory is unclear.	Hold, verify through an appropriate process, or do not contact.

The word dormant should describe an operating state, not a magical number of months. A customer may be dormant because the last job ended and no next step was recorded. Another customer may have been inactive for years but still be an excellent commercial account if the relationship and service fit are documented. A third may be unusable because the record is wrong.

Which dates are useful?

Capture dates that explain the relationship:

• last completed job;
• last invoice paid;
• last customer-requested follow-up;
• last water test or inspection recorded, if the company performs or documents that work;
• last pump repair or replacement;
• last drilling or rehabilitation project;
• last review or referral request, if relevant;
• next action promised by the company;
• last marketing contact and suppression date.

Do not turn one date into a promise. For example, EPA and CDC public guidance recommends annual testing for several private-well indicators, and EPA also identifies repair or replacement and changes in water quality as reasons to test. That can support a conversation about testing when a contractor actually offers that service, serves the location, and can explain the process. It does not prove that every former customer needs an annual contractor visit. See EPA’s private-well guidance and CDC’s testing guidance.

What does a good dormant record look like?

It is not necessarily the newest record or the highest invoice. It is a record where the next conversation can be precise.

Example:

Completed pump repair, site in current service area, customer contact confirmed during the last job, no complaint or suppression flag, company still offers pump service, and the office has a real follow-up or related service reason.

That record can enter a pump-specific queue. It should not be grouped with an old drilling estimate or a commercial account whose operating contact has changed.

What service reason should justify the contact?

The service reason is the heart of the campaign. Every selected record needs a sentence that answers, “Why this customer, why this service, why now?”

Use reasons the company can prove from its records or public guidance. Good reasons include:

1. A promised follow-up was never scheduled.
2. The customer previously requested a check, test, estimate, or revisit.
3. The company has a real service or inspection it offers and the customer’s prior work makes the conversation relevant.
4. A customer’s prior pump, pressure, or water-system work makes a related service worth discussing, without assuming a defect.
5. A commercial customer has a documented service cycle, asset, site, or contact role that needs review.
6. The company is opening a real service window in the customer’s territory and can say what work it accepts.
7. A previous job left a clear next action in the closeout record.

Weak reasons sound like this:

• “We haven’t heard from you in a while.”
• “Your system is probably due for replacement.”
• “We are reaching out to everyone in the area.”
• “You may have a problem with your well.”
• “Book now before prices go up,” when no actual price or schedule change exists.

The message should not create a technical diagnosis from an old invoice. It should invite a conversation about a real service the contractor provides.

What is the Service-Reason Grid?

The grid is a simple way to pair a record with an action. It is the main segmentation framework for this checklist.

Customer history	Evidence-based reason	Recommended action	Avoid
Completed pump repair	Documented follow-up, service check, or related work the company offers	Short pump-service message with a clear reply path	Claiming the pump is failing because it is old
Pump replacement or pressure-system work	Actual company service scope and a documented system detail	Invite a service conversation or review of the prior work	Offering a service the crew does not provide
Completed drilling project	Record handoff, documentation, testing, rehabilitation, or related work the company actually performs	Use a project-specific follow-up	Treating every drilling customer as a recurring maintenance customer
Well inspection or testing	A relevant testing or inspection service, local need, or customer-requested next step	Explain the service and what happens next	Making a health claim or promising a result
Commercial or agricultural account	Site, asset, contact role, and service scope are current	Route to an account owner for a human conversation	Sending residential language to a multi-site buyer
Emergency or one-time call	A real related service and a current contact path	Low priority unless the company can make the reason specific	Assuming an emergency customer wants a plan
Unresolved complaint or warranty issue	No marketing reason until the issue is addressed	Route to service management	Asking for a review or selling another job
Old estimate	Existing buying loop with different objections and status	Use estimate follow-up	Calling it a past customer reactivation

This grid prevents the most common form of overreach: using a customer’s past technical information as if it were a current diagnosis. The prior record is context. It is not permission to invent a problem.

The best reactivation reason is specific enough to route, but modest enough to be true.

Which channel should a well contractor use?

Choose the channel from the record and the message, not from a generic “SMS converts better” claim. The company must be able to show why the channel is appropriate and how an opt-out will be recorded.

When is email the practical starting point?

Email is often the simplest starting channel when the company has a current address and a compliant sending process. The Federal Trade Commission says commercial email rules apply to all commercial messages, including business-to-business messages and messages to former customers. The FTC’s example is direct: “a message to former customers announcing a new product line” is covered.

The FTC guide requires accurate header information, non-deceptive subject lines, a clear opt-out method, a valid physical postal address, and prompt handling of opt-out requests. It also says the sender remains responsible when another company sends the email on its behalf. Read the FTC’s CAN-SPAM compliance guide before launching a campaign.

For a contractor, that means an email message should include:

• an identifiable company sender;
• a subject that says what the message is about;
• one specific service reason;
• a clear reply or booking path;
• the required postal address and unsubscribe mechanism through the sending system;
• a suppression process the office can see before the next send.

Do not make an old customer “opt in again” by hiding the unsubscribe link or asking them to call the office to be removed. The compliance and trust problem is avoidable.

When can a live phone call make sense?

A live call can be useful when a person has requested a callback, a commercial account expects account communication, or the company has reviewed the applicable telemarketing and do-not-call rules for the specific relationship. It should be a human conversation with a clear reason, not a disguised automated campaign.

The FTC’s telemarketing guidance says businesses need to understand the Telemarketing Sales Rule before planning telemarketing, and the detailed guidance explains how an established business relationship can affect live calls. It also distinguishes that relationship from a customer’s entity-specific do-not-call request. See FTC telemarketing guidance and the FTC’s compliance guide.

An old phone number in a spreadsheet is not enough. Before a call, the office should know:

1. who is calling;
2. which completed job or request is relevant;
3. what service the company can offer;
4. what the caller will do if the person says “not interested”;
5. how a do-not-call request will be recorded;
6. who owns the next step if the customer wants an estimate.

If the company cannot answer those questions, do not turn the phone list into a call campaign.

When can SMS be used?

SMS needs the highest discipline. Do not assume that a phone number collected for scheduling or a technician’s arrival automatically authorizes marketing texts.

The FCC has stated that text messages are calls for purposes of TCPA protections and describes the elements of prior express written consent for telemarketing texts, including a clear authorization and the number to which the messages may be sent. The FCC also says the caller bears the burden of showing that consent was obtained. See FCC DA-15-997.

The FCC’s 2024 revocation order addresses revocation by any reasonable means for covered robocalls and robotexts and limits the sender’s confirmation treatment. In practical terms, a contractor needs a visible opt-out status, a way to recognize STOP and other reasonable requests, and a system that prevents future covered marketing texts after revocation. See FCC-CIRC2402-02.

Use SMS only when the company has reviewed the applicable requirements and can show the contact path. If marketing-text consent is not documented, choose email or a different lawful, reviewed process. This article is an operating checklist, not a substitute for counsel on a specific campaign.

A phone number in the CRM is a contact field, not proof of marketing-text permission.

What about direct mail?

Direct mail can be considered when the customer record is strong but electronic contact permission is unclear. It still needs a truthful service reason, accurate identity, territory fit, and capacity behind the offer. It may cost more staff time and production money, so track it as a separate channel rather than blending it into email or phone results.

The point is not to use every channel. The point is to choose a channel the company can control and measure.

How should the contractor write the first message?

The first message should identify the company, name the relevant service history without exposing unnecessary detail, explain the reason for contact, and offer one easy next action.

Use this structure:

We worked with you on [service] in [month or year]. We’re contacting you because [specific, truthful reason]. If you want to discuss [actual service], reply here or call [number]. If this is no longer relevant, tell us and we’ll update your contact preference.

That is a framework, not a claim to copy without checking. Remove any line the record cannot support.

What can a pump-service message look like?

For a past pump or pressure-system customer:

Hi [Name], this is [Company]. We worked on your [pump or pressure-system service] in [month/year]. We’re reviewing service visits in [territory] and have [actual service or follow-up] available for customers who want to discuss [specific scope]. Reply here or call [number] if you’d like us to review what you need. If you no longer want service updates, tell us and we’ll update your preference.

Do not add “your pump is due” unless the company can support that statement for the specific system and service. Do not offer a “free inspection” unless the company has defined what is included, who qualifies, and what happens after the inspection.

What can a drilling-project message look like?

For a completed drilling customer:

Hi [Name], this is [Company]. We completed your well project at [general site reference] in [month/year]. We’re checking our records for customers who may need [actual documentation, testing, rehabilitation, or related service]. If that is relevant to your property or operation, reply here or call [number] and we’ll confirm the right next step.

Use the general site reference only if it is appropriate for the contact and does not expose private information. A commercial account may require a different version addressed to the facilities or operations contact.

What can an inspection or testing message look like?

For a service the company actually performs:

Hi [Name], this is [Company]. We previously handled [service] for you in [month/year]. We’re reaching out because we currently offer [testing or inspection service] in [territory]. If you want to discuss whether it fits your situation, reply here or call [number]. We can explain the scope before scheduling.

This wording keeps the service optional and avoids a health or equipment diagnosis. EPA and CDC guidance can help an owner understand why testing may matter, but the contractor should not turn public guidance into a promise about a particular customer’s water or system.

What should the subject line say?

Keep the subject concrete and accurate:

• Question about your pump service
• Follow-up on your well project
• Testing or inspection question for [territory]
• A service question from [Company]

Avoid fake urgency, fake replies, “Re:” when there was no prior email, and a subject that promises a discount the body does not explain. A reactivation campaign should sound like a company that knows why it is writing.

What should the message not say?

Do not say:

• “We noticed your well is failing.”
• “Your pump is overdue for replacement.”
• “We guarantee better water.”
• “Book now or lose your spot,” unless the schedule constraint is real and the company can honor it.
• “You are one of our best customers,” unless the company has a defensible reason for that classification and the language is useful.
• “Leave us a five-star review and get a discount.”

The customer’s past invoice is not a diagnosis. It is a starting point for a relevant question.

How should replies be routed into booked work?

The reply workflow matters more than the campaign copy. A customer who answers deserves a clear human owner, an immediate disposition, and a next action with a date.

Use this numbered procedure for every active batch:

1. Assign an owner before sending. Name the person who will monitor replies and the backup person for field hours. Do not send a campaign to an unstaffed inbox.
2. Create one campaign identifier. Use a simple internal label such as reactivation-pump-south-2026-08. Attach it to the customer record and every resulting estimate or job.
3. Define the response window. State when replies are monitored and how urgent requests are handled. Do not promise a response time the office cannot meet.
4. Separate reply types. Use at least: wants to schedule, wants information, has a different problem, outside service scope, not now, wrong person, do not contact, complaint, and no response.
5. Ask one qualifying question at a time. Confirm service needed, location or territory, timing, and whether the request is within the company’s scope. Do not interrogate the customer with the entire intake form in the first reply.
6. Create the next action immediately. A requested call gets an owner and date. An estimate request becomes an estimate record. A complaint becomes a service-management task. “Will follow up” is not a disposition.
7. Protect the field schedule. If the customer wants work the company cannot take, say so clearly or route to the correct partner process if one exists. Do not book a job just to make the campaign look successful.
8. Record the source and confidence. The customer may say they remembered the company, saw an email, found a number in their records, or noticed a local message. Record what is known without claiming perfect attribution.
9. Close the loop. Mark booked, canceled, completed, lost, deferred, or no fit. Add the next legitimate follow-up date only when one exists.
10. Review the batch. Compare qualified conversations and booked work by segment, service, territory, and channel. Do not optimize for opens or replies alone.

What should the office say when the customer replies “not now”?

Ask whether they want a dated follow-up or no further contact. A useful reply is:

Understood. Would you like us to follow up in [month or season], or should we leave you off future service updates?

If the customer chooses a date, record the date and the reason. If they ask not to be contacted, record the suppression immediately. Do not put “not now” into a vague notes field that the next campaign will ignore.

What should the office do with an unrelated reply?

Route it as a new service conversation with the same source identifier. A past pump customer may reply about low pressure, no water, water quality, or a new drilling project. The campaign created the opening, but it does not define the customer’s current need.

The dispatcher still needs to confirm whether the company serves the location and performs the requested work. Use the well drilling lead generation system for the broader qualification and booked-job record structure.

What should happen after a completed reactivated job?

Close the job record, record the final invoice or other agreed outcome, and decide whether there is a legitimate next action. If the customer has experienced the completed work, a neutral review invitation may be appropriate. The FTC’s reviews guidance says generalized solicitations for customers to post about their experiences are treated differently from fake or false reviews, but it also prohibits incentives conditioned on a particular sentiment and warns against review suppression. See FTC review and testimonial guidance.

For templates and timing rules, use the existing well drilling review request templates. Do not make the review request the purpose of reactivation. The purpose is a qualified, completed customer interaction.

How should a contractor protect crew capacity?

Capacity is a campaign decision. If the company cannot answer and complete the work, reactivation should be deferred, narrowed, or changed into a waitlist conversation.

Use a three-state capacity check before each batch:

Capacity state	What the owner can safely do	What to avoid
Open	Contact the service segment the crew can qualify and schedule.	Promising an exact response or completion date without checking dispatch.
Constrained	Contact only high-fit customers, group work by territory, and explain real scheduling limits.	A broad campaign that creates scattered site visits and low-margin trips.
Full or unstable	Pause promotional reactivation, handle customer-requested follow-up, and fix the backlog or waitlist process.	Generating more demand that the office cannot acknowledge.

This is especially important for well work because the right job depends on service scope, geography, access, equipment, crew, permits, and schedule. A customer may be valuable but still be a poor campaign target if the company cannot perform the requested work in the current window.

What is a capacity-safe offer?

A capacity-safe offer states the service conversation without pretending that every reply can become a next-day appointment.

Examples:

• “Reply if you want us to review whether this service fits your site.”
• “We are taking requests for [service] in [territory] and will confirm scope before scheduling.”
• “Call the office and we’ll tell you whether this is work we currently accept.”
• “If timing is flexible, tell us the month you are considering and we’ll record it.”

Avoid offers that force the office to promise a number of visits, guaranteed response time, or special pricing that the company has not approved.

When should the contractor segment by geography?

Segment by geography when travel time, crew type, permitting, geology, access, or local service boundaries make the work materially different. A single statewide email can create an expensive mix of jobs that the company cannot serve evenly.

At minimum, include a territory field and a routing owner. For a regional contractor, the first batch may be one county group or service zone. For a commercial drilling company, it may be an account or project type rather than a county.

The goal is not to make a campaign look local. The goal is to make the response deliverable.

What does a useful reactivation scorecard measure?

Measure the journey from eligible record to completed work. Keep campaign activity, demand, sales progress, and revenue in separate columns.

Metric	Formula	What it answers
Eligible records	Records passing the five gates	How large was the real opportunity?
Delivered messages	Messages accepted by the sending channel	How many contacts actually received the message?
Reply rate	Replies / delivered messages	Did people respond to this message and segment?
Qualified conversation rate	Qualified conversations / delivered messages	Did the responses fit the company’s service and territory?
Estimate rate	Estimates / qualified conversations or delivered messages	Did a real sales opportunity form? State the denominator.
Booked-job rate	Booked jobs / qualified conversations or delivered messages	Did the customer commit to work? State the denominator.
Completion rate	Completed jobs / booked jobs	Did booked demand become delivered work?
Realized revenue	Completed, attributable invoice value	What revenue has actually been realized?
Gross-profit contribution	Realized gross profit minus direct campaign and response cost	Did the work make economic sense?
Suppression rate	New suppressions / delivered messages	Did the message or audience create a trust problem?

Choose one denominator per report and display it. “We got 20 replies” says little without the eligible and delivered counts. “The campaign booked five jobs” says little if two jobs were already scheduled or if the source was not recorded.

How should the owner handle attribution?

Use two fields:

• Reported source: what the customer or office record says caused the contact.
• Source confidence: high, medium, or low based on the available evidence.

A customer may receive an email, save the company’s number, search the brand later, and then call. You can record that the campaign was a known touch without claiming it caused the entire decision. If the CRM supports first-touch and assisted-touch views, keep both. If it does not, a simple primary-source field with a confidence note is better than false precision.

Track the campaign identifier through the estimate and job records. Do not rely on memory at month-end. The well drilling lead generation guide covers the wider source-to-booked-job discipline; this page narrows it to reactivated customers.

What would count as a useful result?

A useful result is not necessarily the largest number of replies. It is a repeatable pattern that an owner can act on.

Examples of useful findings:

• Pump-service customers reply when the message names the prior service and gives one clear next step.
• Commercial accounts need a human account-owner call rather than a residential email.
• A territory produces replies but no booked work because the service is outside current crew scope.
• Old estimates generate interest but belong in a different sequence.
• A message creates many suppression requests, so the audience or reason needs to change.
• The campaign produces booked jobs but the jobs are low margin after travel and response labor.

These are operating findings, not universal industry benchmarks. The next action should be based on the company’s own records.

A reply is evidence of interest, not evidence of a booked job.

How should a contractor run the checklist on Monday morning?

Use the following one-day setup if the company already has a usable CRM export. If the data is not usable, spend the day fixing the record process instead of sending.

The 90-minute list review

Minutes 0-15: define the batch. Choose one service line, one territory or account group, and one capacity state. Write the service reason in one sentence.

Minutes 15-30: export the fields. Pull the customer, contact, service, date, status, territory, channel, suppression, owner, and next-action fields. Preserve the raw export so the working list can be audited.

Minutes 30-45: suppress and route. Remove duplicates from the active batch. Route complaints, open estimates, active jobs, bad contact data, and out-of-scope work to their proper queues. Preserve the reason for each exclusion.

Minutes 45-60: score the reason. Give each remaining record one of three labels:

• specific: the service reason and next action are clear;
• possible: the relationship is real but the reason needs human review;
• none: no legitimate reason found.

Only the specific group should be considered for the first send. Possible records need review. None stays out.

Minutes 60-75: check the channel. Confirm the email sending requirements, phone-call restrictions, SMS consent status, suppression process, and the ability to monitor replies. If the channel is uncertain, pause that record.

Minutes 75-90: confirm capacity and ownership. Name the person watching responses, the backup, the service scope, the territory rules, and the next-action statuses. Set up the campaign identifier before any message goes out.

The first batch decision

Send only when all of these statements are true:

• We can say why this customer is receiving the message.
• We can explain the service without diagnosing a problem.
• We can show the contact path and suppression rule.
• We can answer the replies during the defined window.
• We can qualify the work and route it to the correct person.
• We can record estimates, booked jobs, completions, and suppression.
• The company can perform the work it is inviting.

If any statement is false, the campaign is not ready. That is a useful result. It tells the owner which operating constraint must be fixed before spending more effort on outreach.

The weekly review

At the end of the batch, review the list by service, territory, reason, channel, and outcome. Keep the questions narrow:

1. Which records passed the five gates but still lacked enough context?
2. Which reason produced qualified conversations rather than generic replies?
3. Which service requests did the company reject, defer, or route elsewhere?
4. Which replies were lost because the office did not assign an owner?
5. Which contacts opted out or complained?
6. Which jobs were booked, completed, canceled, or still open?
7. What field should be added to the next closeout record so this process gets easier?

Do not change every part of the system at once. Fix the earliest broken gate. If the company cannot tell whether a record is a completed customer, repair the job-status field. If the reason is weak, improve closeout notes. If replies are lost, fix ownership and response routing. If jobs cannot be delivered, fix capacity before expanding the audience.

What common mistakes make reactivation fail?

The same mistakes appear in many dormant-list projects. They are not copy problems. They are decision and operating problems.

Blasting the entire database

The company sends one message to every old customer because the export is easy. The result is a mixed audience with mixed expectations, mixed service fit, and mixed contact status.

Fix it by starting with one service line and one reason. Segment before writing.

Using a calendar as the only trigger

“No job in 24 months” is not a reason to contact someone. It is a filter that may help find records for review. The actual reason must come from service history, a customer request, a legitimate current service, or a real operating window.

Fix it by adding a service-reason field and refusing to activate records labeled none.

Treating an old estimate as a former customer

An estimate that never closed is an unfinished sales loop. The customer may have an objection about scope, timing, price, access, financing, or another contractor. A past customer message can sound careless or confusing.

Fix it by sending the record to an estimate follow-up workflow with its own status and next action.

Assuming a phone number means text permission

A phone number can be useful for scheduling, billing, or a prior inbound call. That does not answer whether the company can send automated or telemarketing text messages now. The FCC’s consent and revocation rules require a more careful review.

Fix it by storing channel status and consent evidence. Do not infer permission from the field being non-empty.

Reusing technical details as a diagnosis

An old pump model, pressure setting, well depth, or water test can help the team understand history. It cannot by itself prove that the customer now has a defect or needs replacement.

Fix it by using language such as “we previously worked on” and “if you want to discuss,” not “your system needs.”

Offering a discount before knowing the economics

A blanket discount can pull in low-fit work, reduce margin on jobs the customer would have booked anyway, and create a price expectation the company cannot sustain. It can also distract from the real service reason.

Fix it by defining the service scope, travel rules, staff time, materials, and margin before offering an incentive. A reactivation checklist does not require a discount.

Sending customers to an unattended inbox

The campaign generates replies, but the dispatcher sees them days later. A customer who wanted an estimate receives no next action, and the owner later calls the campaign a failure.

Fix it by assigning an owner and backup before the first send. Use statuses that force a next action.

Counting replies as revenue

Replies are signals. They are not estimates, booked jobs, completed work, or realized revenue.

Fix it by separating every stage in the scorecard and carrying the campaign identifier into the job record.

Asking for a review before the new work is experienced

A review request before the reactivated job is complete is premature. Asking for a positive review or tying a reward to sentiment creates a different problem.

Fix it by using a neutral review request only after completion and following the FTC review guidance and the platform’s current rules.

Contacting an unresolved complaint with an offer

The customer may need a service manager, correction, warranty response, or refund review. A promotion can make the company look as if it is trying to sell past the problem.

Fix it by routing the record to resolution. Marketing comes later, if the relationship is repaired and contact remains appropriate.

When should a well contractor not reactivate a customer?

Skip or defer the record when the company cannot make the contact useful, welcome, and deliverable.

Do not reactivate when:

• the customer’s identity or current contact path is uncertain;
• a suppression, unsubscribe, STOP, or do-not-call instruction exists;
• the company cannot show the channel is appropriate for the intended marketing message;
• the customer has an unresolved complaint, warranty issue, or payment dispute;
• the company no longer performs the relevant service;
• the site is outside the current service area or the company cannot support the work there;
• the message would require a technical or health claim the company cannot substantiate;
• the crew is already full and the office cannot set honest timing expectations;
• the record is an old estimate that belongs to a different process;
• the only reason is “we have an old list.”

Not contacting a record is a valid outcome. It protects the relationship and keeps the scorecard honest.

What if the contractor wants the customer back but the data is incomplete?

Repair the record process first. Use the next completed job to collect the fields the company will need later: service performed, system or equipment detail when relevant, territory, contact preference, unresolved status, owner, and next action. Confirm that the information is accurate and that the customer understands the company’s communication process.

Do not solve a data-quality problem by sending more messages. An old, wrong list is not an underused asset. It is an unverified risk.

What if the customer sold the property?

Mark the prior contact as moved or no longer responsible if the information is confirmed. Do not assume the new owner has consented to the old communication path. If the company has a legitimate new relationship, create it as a new record with its own source and contact status.

What if the customer is commercial or agricultural?

Use an account-level record with contacts, site, equipment or well information, service scope, and decision role. A single individual may no longer be the right contact. Route the first conversation to an account owner who can understand site count, access, procurement, billing, and scheduling.

The message should not expose private operational details to an outdated contact. Verify the person and role before sharing sensitive information.

What if the customer asks for work the company cannot do?

Say so. Record the request as out of scope, and if the company maintains a reviewed referral process, route it according to that process. Do not book a job to protect a campaign metric. A qualified no-fit record is more useful than a bad booking.

How does reactivation fit with new customer acquisition?

Reactivation should support acquisition, not replace it. It works with known relationships and can reveal service language, territory demand, and weak closeout fields. New prospects still need a reliable visibility and intake system.

The two motions should remain visible in reporting:

Motion	Starting point	Primary question	Main risk
New demand	Search, Maps, referrals, paid campaigns, bids, or other public sources	Can the right company find and qualify us?	Paying for inquiries that do not fit.
Customer reactivation	Completed customer or known account record	Can we create a relevant next conversation?	Contacting the wrong person or creating work we cannot deliver.
Estimate follow-up	Existing quote or proposal	Can we resolve the buying decision?	Treating an unfinished sale as repeat business.

Track the motions separately, then compare them by qualified conversations, booked jobs, completion, margin, and staff time. A reactivated customer can be commercially valuable, but the owner still needs to know whether the process is profitable and repeatable.

For the wider acquisition system, see well drilling lead generation. For a defined recurring offer after completed work, see how to sell well pump maintenance plans. Those pages support this checklist without owning its customer-list reactivation intent.

What should the contractor change in its closeout process?

The best reactivation list is built at job closeout. If the company wants better repeat demand next season or next year, it should leave the next operator a clear record after every completed job.

Add these closeout prompts:

1. What service was completed?
2. What system, equipment, well, or site detail matters for future service?
3. Was the work completed, deferred, disputed, or referred?
4. Was a follow-up promised? If yes, who owns it and on what date?
5. Is there a legitimate related service the company may discuss later?
6. Is the customer in the current territory and service scope?
7. What contact path is appropriate for service communication and what marketing preference is recorded?
8. Is there a review request or referral request that belongs after completion?
9. What should suppress future marketing contact?
10. What source identifier should remain attached to any future booking?

These fields improve more than reactivation. They improve dispatch, estimate follow-up, warranty handling, review timing, and source measurement.

What should the customer receive at closeout?

Give the customer the documents and explanation the company has promised, such as an invoice, relevant report, record, test result, warranty information, or next-step note. NGWA’s contractor guidance emphasizes written scope and records around well construction, including details such as yield evaluation and the well record. The exact documents depend on the work and applicable requirements, but a clear handoff gives the future office a better starting point.

Do not ask the customer to remember technical details that the company should retain. Do not store sensitive information in an unstructured note if a field can carry the decision.

How should the company handle the next-action date?

Use a date only when a real reason exists. Examples include:

• customer requested a callback in a particular month;
• a promised document or test result is pending;
• the customer accepted a plan or service interval the company can deliver;
• an estimate has a stated validity or revisit date;
• a commercial account requested an annual review conversation.

Do not use “follow up later” as a date. It guarantees that the next export will be full of false opportunities.

How can an owner tell whether the process is improving?

Look for better decisions before looking for more messages. A healthy process makes the list smaller, clearer, and easier to route.

Useful signs include:

• more records have a documented service reason;
• fewer messages go to wrong numbers or outdated contacts;
• suppressed records stay suppressed across exports;
• replies reach an assigned owner;
• estimates and booked jobs retain the campaign identifier;
• the company can explain why a customer was contacted;
• the company can decline out-of-scope work without losing the record;
• closeout records contain a next action when one is genuinely needed;
• the owner can compare reactivation by service, territory, and channel without inventing attribution.

Bad signs include:

• rising sends with no reliable disposition;
• more complaints or opt-outs after a generic campaign;
• field staff receiving work the office could not qualify;
• a campaign report that uses “leads” for every reply;
• a growing list of customers marked “follow up later” without dates;
• repeat contacts receiving different instructions because suppression is stored in separate systems;
• the owner cannot identify who was responsible for replies.

The goal is not a permanently active list. The goal is a list that tells the truth about the business relationship and gives the office a next decision.

What is the final customer reactivation checklist?

Before the first send:

• Choose one service line, territory, or account group.
• Define the capacity state: open, constrained, or full.
• Export completed customers and the fields needed for routing.
• Separate active jobs, open estimates, complaints, disputes, and canceled work.
• Remove duplicates and flag bad contact details.
• Preserve unsubscribe, STOP, do-not-call, complaint, and other suppression records.
• Give every active record a service reason.
• Mark records with no defensible reason as out.
• Confirm the current service area and scope.
• Review the selected email, call, SMS, or mail process for the intended message.
• Assign a reply owner and backup.
• Define reply, qualification, estimate, booked, completed, deferred, lost, and suppression statuses.
• Create a campaign identifier before the message goes out.
• Prepare one short message branch for each selected service segment.

After the send:

• Monitor replies during the stated response window.
• Route complaints and do-not-contact requests immediately.
• Qualify service, territory, timing, and fit without diagnosing from old records.
• Give every meaningful reply a dated next action.
• Keep old estimates in their own sequence.
• Record source and confidence at the estimate or job level.
• Separate delivered messages, replies, qualified conversations, estimates, booked jobs, completions, and realized revenue.
• Ask for an honest review only after completed work and under current platform and legal rules.
• Review results by service reason, territory, channel, and capacity state.
• Improve the earliest broken gate before expanding the audience.

If the company cannot pass the record, reason, permission, capacity, and outcome gates, the right next step is repair, not reactivation.

A well contractor customer reactivation system should make the office more selective, not noisier. Start with a small, explainable group of completed customers, give each one a truthful service reason, route every response, and judge the work by qualified booked jobs and completed outcomes. Brictale’s free territory audit can help identify where repeat demand, public visibility, service pages, call handling, and tracking are breaking apart in the same territory.