# Well Drilling Review Request Templates for Contractors

Source: https://brictale.com/learn/well-drilling-review-request-templates
Published: 2026-08-19
Language: en
Published by Brictale Pro, the professional archive of Brictale Home Intelligence. https://brictale.com/pro

## Short answer

Use a short, honest review request after the customer has experienced a completed well or pump job, and include a direct Google review link. Choose the timing by service type, send the same public invitation to eligible customers, avoid incentives or review gating, and track requests against qualified calls and booked jobs.

---

## What are the safest well drilling review request templates?

The safest template is short, honest, and sent after a real customer has experienced a completed service. It names the company and service, asks for an honest review, and gives one direct Google link. Use the job-state matrix below to choose timing, send the same public invitation to eligible customers, and never ask for five stars, keywords, incentives, or a positive-only review.

The wording matters. The operating decision matters more.

If an owner sends a polished request before a pump has been tested, before a well project has been handed over, or only to customers expected to leave praise, the template becomes a liability. A plain message sent at the right moment is more useful than a clever message sent at the wrong one.

![Illustration of a well and pump company owner reviewing a completed-job review request workflow](/images/learn/well-drilling-review-request-templates/well-drilling-review-request-templates-well-drilling-review-request-templates-workflow.webp)

![Illustration of a well and pump company owner reviewing a completed-job review request workflow](/images/learn/well-drilling-review-request-templates/well-drilling-review-request-templates-well-drilling-review-request-templates-timing-matrix.webp)

## Why does a well contractor need a service-specific review process?

A review request for a same-day no-water repair is not the same as a request for a new drilled well. The customer experience, completion point, delay between work and confidence, and people involved all change by service line.

For a pump repair, the customer may know within hours whether water pressure has returned. For a new well, the customer may be waiting on testing, records, a final connection, cleanup, or another contractor. For rehabilitation, the result may need to be monitored over time. A generic "thanks for choosing us, leave a review" message ignores those differences.

The National Ground Water Association's public handout on hiring a water well contractor lists reputation beside licensing, certification, well logs, equipment, insurance, code familiarity, written contracts, and other selection questions. [NGWA's guidance](https://www.ngwa.org/docs/default-source/default-document-library/groundwater/How-to-Hire-a-Water-Well-Contractor.pdf) is written for the person hiring a contractor, but it gives an owner a useful standard for what public proof should support: a real, accurately described service experience.

Reviews are not a substitute for those things. They are one part of the proof around them.

Google says local results are mainly based on relevance, distance, and prominence. It also says more reviews and positive ratings can help local ranking, while warning that there is no way to request or pay for a better position. [Google's local-ranking guidance](https://support.google.com/business/answer/7091?hl=en) supports a restrained conclusion: reviews can contribute to local visibility, but a request template cannot guarantee a Maps position or a booked job.

**A review request is a customer-experience handoff, not a ranking trick.**

That distinction keeps the process useful to an operator. The owner can ask whether the work was completed properly, whether the customer understood the next step, and whether the resulting public proof reflects the services the company can actually perform. The owner should not promise that a certain sentence will rank the profile, produce a fixed number of calls, or create a five-star average.

## What should count as a review-ready job?

A job is review-ready when the customer has had a genuine experience of the service and the company has reached the agreed operational handoff point. The request should not be used to cover a known unresolved issue, an unverified outcome, or a disputed transaction.

Use this four-part gate before sending any template:

1. **Real experience:** the person received or directly experienced the company's service. Do not ask a prospect, neighbor, family member, employee, or referral source who did not receive the work.
2. **Operational completion:** the company has reached its defined completion point for that service. This may be a function check, commissioning, final test, documentation handoff, or agreed project closeout.
3. **Accurate contact path:** the company is permitted to use the selected channel for this customer and can honor replies, corrections, and opt-outs.
4. **No manipulation:** the request does not offer an incentive, demand a rating, request specific wording, or filter the public invitation based on predicted sentiment.

Google's guidance is direct: “Reviews and other user contributions to Google Maps must reflect a genuine experience.” [Google's review guidance](https://support.google.com/business/answer/3474122?hl=en) gives the public standard. The contractor workflow below turns it into an internal check.

| Gate | Pass condition | Hold the request when |
|---|---|---|
| Customer | The recipient used or experienced the service | The contact is a quote-only lead, vendor, employee, family member, or person who was not the customer |
| Work | The agreed completion point has been reached | A callback, failed test, missing part, permit item, warranty issue, or promised return visit is still open |
| Account | The company can identify the job and recipient | The record is duplicated, the customer is unknown, or the contact details are wrong |
| Channel | The selected channel fits the relationship and company process | The company cannot handle replies, opt-outs, or a complaint that comes back through the message |
| Request | The copy asks for an honest experience through one public link | The copy asks for five stars, a keyword, a named employee, a positive sentiment, or a review in exchange for value |

This gate is a recommendation, not a legal test. State laws, contracts, platform rules, and message regulations can add requirements. The company's counsel or compliance lead should review any automated SMS program.

**The completion trigger is more important than the wording.**

## When should you ask after each well or pump service?

Choose the request moment from the customer's ability to judge the work, not from the moment an invoice is marked paid. The best moment is usually after the customer has experienced the result and the office can answer a follow-up question.

| Service type | Suggested operational trigger | First channel | What the owner should confirm |
|---|---|---|---|
| Emergency pump repair or no-water call | After the system has been tested and the customer confirms the immediate problem is addressed | SMS or technician handoff | The pump runs, the customer knows what was done, and no promised callback is open |
| Pump replacement or pressure-system work | After commissioning and a reasonable function check | SMS followed by email when the job is larger | The customer has received the basic care or warranty information and the system is operating as agreed |
| New residential well drilling | After the agreed completion and handoff, including required testing, records, cleanup, or next-step explanation | Email, then optional SMS | The company has not asked the customer to review an incomplete stage of a multi-stage project |
| Commercial or agricultural well project | After the agreed project milestone or final handoff, based on the contract | Email from the project owner | The recipient has authority to describe the experience and the project is not still in a dispute or commissioning phase |
| Well rehabilitation | After the agreed rehabilitation work and monitoring or test point | Email or SMS, depending on the customer relationship | The message does not imply a guaranteed yield, water quality, or outcome beyond what was actually delivered |
| Well inspection, testing, or documentation | After the report or deliverable is received | Email | The customer can review the service provided without being asked to endorse an unrelated result |
| Recurring maintenance or service visit | After each completed visit if the customer relationship supports it, or after a meaningful milestone | SMS | The company is not sending repetitive requests that create fatigue |
| Job with an unresolved complaint | Do not send the normal request yet; continue service recovery and document the next decision | Direct office contact | The public request is not being withheld permanently to hide a complaint, and the company is prepared for honest feedback |

These triggers are practical recommendations. A company can set different timing for a warranty-heavy job, a commercial account, or a customer who prefers email. The key is to define the trigger before the request is automated.

### How should emergency pump repair timing work?

Start with function, not relief. A customer who called because the house had no water may be grateful when the pump starts, but the office still needs to know whether the pressure switch, tank, control box, electrical supply, or another part of the system remains under observation.

An appropriate trigger might be:

- the technician has completed the work order;
- the system has been tested according to the company's normal procedure;
- the customer has been told what changed and what to watch for;
- there is no open promise to return that would materially change the customer's account of the service.

If the customer reports a problem in reply to the review request, treat it as a service message. Do not answer with a second request or tell the customer to keep the issue off Google. Assign an owner, respond, and record the result.

### How should pump replacement timing work?

Pump replacement often deserves a short delay after commissioning because the customer needs to use the system. The company may have to explain pressure behavior, controls, noise, water flow, or the warranty path. The first request can be sent after the agreed function check. For a larger replacement, an email with the work summary can make the review link easier to recognize than an isolated text.

Do not write a template that promises the replacement will last a certain number of years or that asks the customer to endorse a pump brand unless the customer independently chooses to discuss it. The request should describe the service completed, not manufacture a technical testimonial.

### How should new well drilling timing work?

New well drilling is a project, not a single doorstep event. The request should usually wait until the company's defined handoff point. That may include well construction, development, yield evaluation, disinfection, records, site cleanup, and a clear explanation of what remains for the owner or other trades. The exact obligations vary by contract and jurisdiction.

The customer can still be asked to review the company after a completed milestone if the message clearly says what stage was completed and does not imply that the entire project is finished when it is not. For most small companies, one request after the final agreed handoff is easier to manage and less likely to confuse the customer.

### How should rehabilitation, testing, and inspection timing work?

Ask when the deliverable is in the customer's hands and the service has reached its stated scope. If the company performed a test or inspection, ask about the clarity, communication, timeliness, and professionalism of that service. Do not ask the customer to confirm an outcome the contractor did not promise or control.

This is where internal service tags help. A review about a well inspection should not be presented as proof of pump replacement expertise. A review about emergency repair should not be used to imply that the company drills new wells. Public proof is strongest when the service fit is clear.

![Illustration of review request timing by well and pump service type](/images/learn/well-drilling-review-request-templates/well-drilling-review-request-templates-well-drilling-review-request-templates-timing-matrix.webp)

![Illustration of review request timing by well and pump service type](/images/learn/well-drilling-review-request-templates/well-drilling-review-request-templates-well-drilling-review-request-templates-sms.webp)

## How do you create a direct review link before sending anything?

Create and test one direct Google review link, then store it where the office and field team can reach it without searching. Google provides a Business Profile workflow for creating a review link or QR code. [Google's review-link instructions](https://support.google.com/business/answer/16816815?hl=en) are the source of truth for the current clicks.

Use this setup procedure:

1. Sign in to the Google account that manages the correct Business Profile.
2. Open the profile's review-request or customer-review control.
3. Generate the review link or QR code supplied by Google.
4. Open the link from a phone that is not the office computer. Confirm that it opens the intended business profile and review action.
5. Send a test to the owner or office lead. Check the visible company name, profile, location context, and the mobile experience.
6. Store the link in the CRM, work-order system, office template library, and the approved technician handoff card.
7. Record the date of the last test and assign an owner to retest it after a profile move, rename, duplicate cleanup, or major account change.

Use one primary review destination in a message unless the customer relationship calls for another platform. Multiple links create a choice problem and make attribution harder. If the company needs reviews on more than one platform, use a documented channel strategy rather than putting a row of destinations in every SMS.

The link is a friction reducer, not proof that the company has earned a review. It should take the customer to the correct place. The work and the request still need to be honest.

## Which SMS templates fit well and pump work?

Use SMS when the customer already expects the company to communicate by text and the company has a process for replies and opt-outs. Keep the first message compact. Identify the company, reference the completed service, ask for an honest review, and include one link.

The brackets are merge fields. Replace every field before sending. Never let a system send the words `[service]`, `[name]`, or `[link]` to a customer.

### Template 1: completed pump repair

```text
Hi [first name], this is [company]. Thanks for trusting us with your pump repair today. If you’re willing, would you share an honest review of your experience? [Google review link]
```

Why it works: it says what happened, avoids a star request, and gives one action. It does not claim that the repair solved more than the technician verified.

### Template 2: pump replacement or pressure-system work

```text
Hi [first name], [company] here. We appreciate the opportunity to complete your pump replacement today. When you’ve had a chance to use the system, would you share an honest review of your experience? [Google review link]
```

Why it works: the phrase "when you’ve had a chance" fits work that needs customer use before judgment. If the company has a defined commissioning period, use that period internally and send only after the agreed trigger.

### Template 3: completed well drilling handoff

```text
Hi [first name], this is [company]. Thank you for choosing us for your well project. Now that we’ve reached the agreed handoff, would you share an honest review of your experience? [Google review link]
```

Why it works: it avoids saying "your new well is perfect" or implying that an unfinished project is complete. The office should only use it after the handoff condition is true.

### Template 4: inspection, testing, or documentation

```text
Hi [first name], [company] here. We’ve delivered the [inspection/testing/report] for your well. If you’re willing, we’d appreciate an honest review of your experience with our service: [Google review link]
```

Why it works: it asks about the service the company actually performed. It does not ask the customer to endorse a test result or a condition the contractor did not control.

### Template 5: short technician handoff by text

```text
Thanks again for having [company] out today, [first name]. If you’d like to share an honest review of the visit, here’s the direct link: [Google review link]. Reply here if you need the office to follow up on anything.
```

Why it works: it keeps the public request and the service reply path in the same message without saying that a complaint must stay private. The company must monitor the reply channel.

### Template 6: larger project with a summary email coming

```text
Hi [first name], we’ve sent your [project] completion summary by email. If you’re willing, you can share an honest review of your experience with [company] here: [Google review link]
```

Why it works: the customer has a useful project record to refer to. Do not send it until the email is actually sent and the project status is accurate.

### Template 7: one reminder

```text
Hi [first name], a quick follow-up from [company] in case the review link was easy to miss. If you’d like to share an honest review of your [service], here’s the link again: [Google review link]. No reply is needed if now isn’t a good time.
```

### What should an SMS system do with opt-outs?

Treat a request to stop as a stop. The FCC's order identifies common reply-text terms including STOP, QUIT, END, REVOKE, OPT OUT, CANCEL, and UNSUBSCRIBE as reasonable means to revoke consent in the covered context. [FCC-24-24A1](https://docs.fcc.gov/public/attachments/FCC-24-24A1.pdf) is a primary source for that specific discussion.

This does not make every review text program legally compliant. Message content, consent, automation, state law, sender technology, and the customer relationship all matter. Use a system that can record the opt-out and prevent another review request from firing. Have the company's counsel or compliance lead approve the program.

![Illustration of a well pump technician sending a compliant review request by text](/images/learn/well-drilling-review-request-templates/well-drilling-review-request-templates-well-drilling-review-request-templates-sms.webp)

![Illustration of a well pump technician sending a compliant review request by text](/images/learn/well-drilling-review-request-templates/well-drilling-review-request-templates-well-drilling-review-request-templates-email.webp)

## Which email templates fit drilling and larger pump projects?

Email gives the office more room to explain the completed service, attach a useful summary, and make the request feel connected to a real project. It is often better suited to new well drilling, commercial work, agricultural work, rehabilitation, and installations where the customer needs a record.

Keep the request near the top. Do not bury the link beneath a long sales message. Do not turn a completion email into an advertisement for unrelated services.

### Template 8: professional post-service email

```text
Subject: A quick favor after your [service]

Hi [first name],

Thank you for choosing [company] for your [service] on [date]. We appreciate the opportunity to work with you.

If you’re willing, would you share an honest review of your experience with our team? Here is the direct Google link:

[Google review link]

If you need the office to follow up on anything from the job, reply here and we’ll route it to the right person.

Thank you,
[sender name]
[company]
```

This is the default email. It does not tell the customer what to say. It also makes an office reply possible without making a private complaint a condition of public feedback.

### Template 9: new well project handoff

```text
Subject: Your [well project] handoff

Hi [first name],

Your [well project] has reached the agreed handoff point. We’ve included the relevant [report, record, test information, care notes, or next-step information] below or in the attached project summary.

If you’re willing, we’d appreciate an honest review of your experience with [company]. You can use this direct Google link:

[Google review link]

If something about the handoff needs attention, reply to this email so [office contact] can review it.

Thank you,
[sender name]
```

Only include the bracketed records that actually exist. Do not use "final" if the contract still has an open stage. A customer should not have to correct the company's project status in a public review.

### Template 10: commercial or agricultural account

```text
Subject: [Project] completion and feedback

Hi [first name],

Thank you for working with [company] on the [project]. We’ve completed the agreed [milestone or handoff] and sent the project information to [recipient or team].

If you’re the right person to comment on the service, we’d appreciate an honest review of your experience. Here is the direct link:

[Google review link]

If another person on your team handled the day-to-day work, please forward the request to that person rather than asking someone who did not experience the service to review it.

Thank you,
[sender name]
```

The line about the right reviewer is important for commercial work. A procurement contact, property manager, project engineer, or facility lead may have different knowledge from the person who worked with the crew. Use a generalized, accurate process instead of asking an executive to write a review about an experience they did not have.

### Template 11: report or inspection delivery

```text
Subject: Your [inspection or test] report

Hi [first name],

Attached is the [inspection or test] report from [company]. Thank you for giving us the opportunity to provide this service.

If you’re willing, would you share an honest review of your experience with our communication, process, and service? [Google review link]

If you have a question about the report, reply here so we can send it to the appropriate person.

Best,
[sender name]
```

This wording keeps the public review about the service experience. It does not ask the customer to verify a technical conclusion or to repeat language supplied by the contractor.

### Template 12: one email reminder

```text
Subject: Following up on your [service] review link

Hi [first name],

I’m following up once in case the link from [company] was easy to miss. If you’re willing, you can share an honest review of your [service] experience here:

[Google review link]

No problem if you don’t have time. If the office needs to follow up on the work, reply to this email.

Thank you,
[sender name]
```

Send one reminder by default. A larger commercial relationship may use a different cadence, but the owner should document why. More touches do not automatically create better feedback. They can create annoyance, especially after an emergency call.

![Illustration of a well drilling office manager sending a project completion email and review link](/images/learn/well-drilling-review-request-templates/well-drilling-review-request-templates-well-drilling-review-request-templates-email.webp)

![Illustration of a well drilling office manager sending a project completion email and review link](/images/learn/well-drilling-review-request-templates/well-drilling-review-request-templates-well-drilling-review-request-templates-decision-tree.webp)

## What can a technician say in person?

The in-person script should take less than half a minute and should not pressure the customer while the technician is standing in the home, at the well site, or beside the equipment. Give the customer the option to use the link later.

### Template 13: technician handoff

```text
We’ve finished the work we agreed to complete today. The office will send you a link where you can share an honest review of your experience if you choose. If you need us to follow up on anything from the job, tell me now or reply to the office message.
```

This script is deliberately plain. It does not say "give us five stars," ask the customer to mention the technician, or put a phone in front of the customer until they comply. Google's Maps policy says merchants should not pressure people to leave ratings or reviews on the spot or ask for specific content. [Google's prohibited-content guidance](https://support.google.com/contributionpolicy/answer/7400114?hl=en) supports keeping the handoff optional and content-neutral.

### Template 14: QR card or leave-behind

```text
Thank you for choosing [company].

If you’d like to share an honest review of your experience, scan the QR code or use the link below.

[QR code]
[short review link]

Questions about the work? Call [office number] or reply to the follow-up message from our office.
```

The card should identify the company clearly and contain a QR code that has been tested. It should not say "leave a five-star review," offer a discount, or include a prompt such as "mention our fast pump repair in [town]." The customer owns the words.

### What should a field team know before using a template?

Give technicians a one-page instruction with four rules:

- Offer the request only after the defined handoff point.
- Use the approved company link and do not substitute a personal link.
- Invite an honest review without naming a rating or required content.
- Record a service issue through the normal office path and never debate a customer into leaving a review.

The field team should not become a review quota team. A quota changes the interaction. It can also push employees to ask for a particular number of reviews or particular words, which is the opposite of an honest request.

## How should you follow up without pressure?

Use a small sequence with clear stop conditions. A practical default is one initial request and one reminder through the same channel or a channel the customer already expects. The goal is to make the link easy to find, not to wear the customer down.

### The two-touch sequence

**Touch 1, after the service trigger:** send the relevant SMS or email template. Record the job ID, service type, completion trigger, channel, link version, and sender.

**Touch 2, after a reasonable interval:** send one short reminder. The interval should match the service. An emergency repair may need a short wait after the function check. A larger project may justify a longer wait after the handoff email. The company should choose a window and keep it consistent enough to compare.

**Stop:** stop after a posted review, an explicit decline, an opt-out, a direct request to stop, or a new issue that needs service recovery. Do not reset the sequence because the customer did not answer.

### What if the customer replies with a complaint?

Reply as an office, not as a review algorithm. A useful response is:

```text
Thanks for letting us know, [first name]. I’m sorry this part of the experience was not resolved. I’ve sent this to [office owner or service manager] and we’ll contact you by [time or business-day expectation] to review what happened.
```

Do not follow this message with "please update your review when we fix it." Resolve the issue first. If the customer later chooses to update a review, that decision must be theirs. The FTC's guidance says not to ask only customers who are expected to leave positive reviews, and Google prohibits selectively soliciting positive reviews. [FTC's review-solicitation guidance](https://www.ftc.gov/business-guidance/resources/soliciting-paying-online-reviews-guide-marketers) and [Google's Maps policy](https://support.google.com/contributionpolicy/answer/7400114?hl=en) should be read together here.

The right lesson from a complaint is often operational. Was the customer unclear about the work? Did the technician promise a callback that no one owned? Did the invoice describe a different completion point? A review request can surface those gaps, but it cannot repair them.

![Illustration of a contractor review request decision tree with service recovery and opt-out paths](/images/learn/well-drilling-review-request-templates/well-drilling-review-request-templates-well-drilling-review-request-templates-decision-tree.webp)

![Illustration of a contractor review request decision tree with service recovery and opt-out paths](/images/learn/well-drilling-review-request-templates/well-drilling-review-request-templates-well-drilling-review-request-templates-compliance.webp)

## Which review-request practices should a contractor reject?

Reject any tactic that changes who is allowed to speak, what they are asked to say, or whether the company rewards a desired sentiment. A template library is not safe just because the words sound friendly.

| Practice | Why it is a problem | Use instead |
|---|---|---|
| "Leave us a five-star review" | It requests a rating and influences sentiment | Ask for an honest review |
| Ask only customers marked happy in a survey | It can suppress less favorable experiences | Send the same public invitation to eligible customers |
| Offer a discount for a review | Google prohibits incentives for review activity, and FTC rules add disclosure and sentiment concerns | Offer no review-conditioned value |
| Ask the customer to include "pump repair" and the town | Google says merchants should not request specific content | Describe the completed service internally, but let the customer choose words |
| Ask the customer to name a technician | It is specific content and can create employee pressure | Let the customer mention people if they choose |
| Put the QR code in front of a customer until they post | It can become pressure, especially at a private home or job site | Provide the link and let the customer decide later |
| Send a review request before a failed test or open callback is resolved | The customer has not experienced the promised outcome | Wait for the defined completion point and keep service recovery open |
| Buy reviews or ask staff, family, or vendors to review | The experience or independence is not genuine | Ask real customers who experienced the service |
| Use an AI tool to write a review for a customer | It misrepresents the customer's own experience | Give customers space to write their own review |
| Put several platforms in one SMS | It increases choice friction and complicates measurement | Choose one destination for the message |
| Copy a customer review into an ad without permission or context | A public review used in advertising can become a testimonial with different disclosure and context issues | Get permission and preserve attribution and meaning |

Google describes incentives as including payment, discounts, free goods or services, and other benefits that influence a review. [Google's incentivized-review policy](https://support.google.com/contributionpolicy/answer/16597558?hl=en) is clear enough for an owner decision: do not build a Google review program around rewards.

The FTC's consumer-review rule also matters. It says that an incentive cannot be conditioned on a particular sentiment, and the FTC warns that selectively asking customers believed to be happy can create problems under the FTC Act. [The FTC's Q&A](https://www.ftc.gov/business-guidance/resources/consumer-reviews-testimonials-rule-questions-answers) is the right source to review with counsel when a campaign uses incentives, testimonials, or automated filtering.

**The safest review program is easy to explain to the customer and to a regulator.**

![Illustration of compliant and noncompliant review request practices for a well contractor](/images/learn/well-drilling-review-request-templates/well-drilling-review-request-templates-well-drilling-review-request-templates-compliance.webp)

![Illustration of compliant and noncompliant review request practices for a well contractor](/images/learn/well-drilling-review-request-templates/well-drilling-review-request-templates-well-drilling-review-request-templates-scorecard.webp)

## How can you personalize a request without scripting the review?

Personalize the message with facts about the job record, not instructions for the customer's public wording. The office needs enough context to avoid sending a pump-repair request to a drilling customer, but the customer should control the review.

Use internal fields such as:

| Internal field | Example value | What it changes |
|---|---|---|
| Customer name | First name only when appropriate | Greeting |
| Service type | Pump repair, pump replacement, well drilling, inspection | Template selection |
| Completion trigger | Function check, commissioning, report delivered, project handoff | Send eligibility |
| Job location | Internal town or territory tag | Reporting, not customer copy unless accurate and useful |
| Technician or project owner | Internal record | Routing and accountability |
| Public link | Current tested Google link | Destination |
| Open issue | None, callback, warranty, billing, permit | Hold or service-recovery path |
| Channel permission | SMS, email, in-person card | Channel selection |

Avoid inserting details that could expose a customer's private address, water problem, property condition, or project information. A public review is public. The customer may choose to mention a place or technical detail, but the company should not push them to reveal it.

Use a small set of templates with merge fields rather than generating a new message for every job. Variation should come from the actual service and completion stage. It should not come from changing the request into increasingly persuasive language.

### Which details belong in the customer message?

Include the company name, service category, sender identity when useful, the honest-review invitation, one link, and an office reply path. Add a project date only if it helps the customer recognize the job and does not expose sensitive information.

Leave out a promised rating, a keyword, an instruction to mention an employee, a claim that the company needs reviews to survive, and a request to compare the company with a competitor. Those additions turn a simple request into pressure.

### Should the message say "if you were happy"?

Be careful. People use the phrase casually, but it can make the public invitation sound like it is intended only for positive feedback. A cleaner default is "If you’re willing, would you share an honest review of your experience?" That wording gives the customer control and does not ask them to classify themselves before seeing the link.

The FTC says the review rule does not contain a specific prohibition on asking only customers believed to be happy, but that practice could violate the FTC Act. The safest operating choice is a generalized invitation to eligible customers, not a satisfaction filter.

## How should an owner measure whether requests are helping the business?

Measure the process from eligible completed jobs to public feedback and commercial outcomes. Review count is an output, not the whole business result. A company can collect reviews and still miss qualified calls, send messages to the wrong territory, or fail to answer the phone.

Start with one row per eligible job or customer record.

| Field | Example | Why it matters |
|---|---|---|
| Job ID | Internal work-order number | Prevents duplicate requests |
| Service line | Pump repair, drilling, inspection | Shows which work creates feedback |
| Territory | Internal town or route | Connects public proof to the served market |
| Completion date | Date from work order | Supports timing review |
| Eligible date | Date the defined trigger was met | Separates operational completion from payment |
| Channel | SMS, email, technician, card | Compares process use |
| Request sent | Yes/no and date | Shows execution |
| Reminder sent | Yes/no and date | Controls frequency |
| Public review | Yes/no and date if visible | Measures response, not sentiment manipulation |
| Issue reply | Yes/no | Shows service-recovery demand |
| Qualified call later | Yes/no and source when known | Connects public proof to inquiry quality |
| Estimate booked | Yes/no | Separates inquiry from a real sales event |
| Job booked | Yes/no | Connects marketing activity to operations |
| Lost reason | Outside territory, no capacity, price, wrong service, no answer | Identifies the next bottleneck |

The last five fields are where an owner avoids vanity reporting. A review may help a future customer trust the company, but the review itself does not prove that a later call came from it. Use call tracking, the CRM source field, the customer's own answer, and a consistent attribution rule.

This is related to the broader measurement problem covered in [how to measure Google Maps leads for well contractors](/learn/how-to-measure-google-maps-leads-well-contractors). That page handles the territory and lead-measurement system. This article supplies the review-request fields that can feed it.

### What should the weekly owner review ask?

Use a short review every week or every two weeks while the process is being installed:

1. How many eligible jobs reached the completion trigger?
2. How many requests were sent within the company's chosen window?
3. How many failed because of missing contact information, an untested link, or an automation error?
4. Which service lines received requests and which did not?
5. How many customers replied with an unresolved issue?
6. Did any message create an opt-out or complaint?
7. Which reviews, if any, reflect the service types the company wants to be known for?
8. Were qualified calls, estimates, and booked jobs recorded separately?
9. What operational change would reduce complaints before another request is sent?

Do not set a target such as "collect 100 reviews this month" without checking capacity and service quality. A sudden campaign sent to old or poorly documented jobs can create more customer friction than useful proof. Start with current, clearly completed work.

### What can a simple request dashboard show?

For a small company, four rates are enough to start, as long as the numerator and denominator are written down:

- **Send rate:** requests sent divided by eligible completed jobs.
- **Public response rate:** visible reviews attributed to the process divided by requests sent, with the limits of attribution documented.
- **Issue rate:** service issue replies divided by requests sent.
- **Booked-job rate:** booked jobs from identified qualified conversations divided by qualified conversations.

These are internal operating calculations, not industry benchmarks. Do not compare them to an unverified vendor claim or treat them as a promise. Use them to find broken handoffs. If send rate is low, the office process is broken. If issue rate rises after a service change, inspect operations. If requests are high but qualified calls do not move, review the wider profile, website, response speed, and service fit.

**Review count is a signal; booked work is the business outcome.**

![Illustration of a well contractor review request and booked-job scorecard](/images/learn/well-drilling-review-request-templates/well-drilling-review-request-templates-well-drilling-review-request-templates-scorecard.webp)

![Illustration of a well contractor review request and booked-job scorecard](/images/learn/well-drilling-review-request-templates/well-drilling-review-request-templates-well-drilling-review-request-templates-monday-setup.webp)

## How do reviews fit into Google Maps and the website?

Reviews support a larger local visibility and conversion system. They do not replace accurate Business Profile information, relevant service pages, clear territory language, a working phone path, answered calls, or a capable sales process.

Google's local-ranking guidance names relevance, distance, and prominence as the main categories it uses for local results. It also says complete and accurate business information helps Google understand a business, and that reviews and positive ratings can contribute to prominence. [Google's guidance](https://support.google.com/business/answer/7091?hl=en) does not publish a universal review count or promise a position.

That has three implications for a well or pump operator:

1. Ask for honest feedback about the real service mix. This can make the public profile more informative to a future customer, but it does not change the company's actual distance or service capability.
2. Keep the website and profile aligned. If the company asks for pump-repair work but the website only explains new drilling, the review request cannot fix the relevance gap.
3. Track the call after the review process. A profile action or review count is not the same thing as a qualified, answered, profitable call.

The [well drilling website conversion checklist](/learn/well-drilling-website-conversion-checklist) covers the connected proof and contact path. Use the review process to supply truthful customer evidence, then make sure the pages and phone workflow can handle the demand.

### Should you copy reviews onto the company website?

Only with a clear process for permission, attribution, accuracy, and context. A review shown in an advertisement or on a company website can function as a testimonial rather than merely a platform-hosted review. The FTC distinguishes consumer reviews from testimonials and applies different considerations when a business uses the material in its own marketing. [The FTC's review rule Q&A](https://www.ftc.gov/business-guidance/resources/consumer-reviews-testimonials-rule-questions-answers) explains that distinction.

Do not edit a customer's words into a technical claim. Do not move a pump-repair review onto a drilling page where it implies a different service. Do not publish a customer's address, private water problem, or project photograph without permission.

### Should an agency manage the review request process?

An agency or software tool can help with links, scheduling, reporting, and templates. The contractor still owns the truth of the job record, the completion trigger, the customer relationship, the opt-out, and the service recovery. A vendor that asks for positive-only feedback, hides negative feedback, invents job detail, or cannot show the request log is creating risk.

Brictale can use a free territory audit to examine how public proof, service coverage, profile visibility, and qualified calls fit together. The audit should lead to a better owner decision, not a guaranteed review count or ranking promise.

## When should a contractor not start a review-request campaign?

Do not make review collection the first project when the company has a more immediate bottleneck. A request system cannot compensate for a phone that rings into an unanswered voicemail, a service area the company cannot profitably cover, unresolved warranty work, or a profile with incorrect business information.

Pause or narrow the campaign when:

- the company cannot define when a job is complete;
- the office has no person responsible for replies and opt-outs;
- the direct review link has not been tested on a phone;
- work-order records do not identify the customer and service accurately;
- the company is considering discounts or other review-conditioned rewards;
- the field team is being paid or pressured by review count;
- the business has a queue of unresolved customer issues;
- the company has no way to distinguish a qualified call from a wrong-number or homeowner research call;
- the current crew is at capacity and more demand would harm response time;
- the requested review would expose private project or property information.

The right alternative may be an intake cleanup, call-answering fix, service-page repair, profile correction, or a customer-resolution sprint. The [how to get more pump repair leads](/learn/how-to-get-more-pump-repair-leads) guide covers the wider lead system. Review requests should support that system, not distract the owner from the bottleneck nearest the money.

**More reviews are not a growth strategy when the company cannot answer the calls they may help create.**

### What are the most common template mistakes?

**Mistake 1: Sending immediately after payment.** Payment is an accounting event. It may happen before testing, commissioning, documentation, or a promised return visit.

**Mistake 2: Asking for a five-star review.** It tells the customer that the company wants a rating outcome, not an honest account.

**Mistake 3: Asking for keywords.** The message starts shaping the evidence instead of allowing the customer to describe the experience.

**Mistake 4: Filtering by a private satisfaction score.** The company may be tempted to send public links only to people who clicked a positive button. That creates a biased process and can violate platform or consumer-protection expectations.

**Mistake 5: Adding every review destination.** The customer sees a menu rather than a simple action, and the owner loses a clean record of which destination the request intended.

**Mistake 6: Overwriting the customer's words.** A contractor may turn "the office called me back" into "the company solved my low-yield well." That is not personalization. It is a new claim.

**Mistake 7: Letting an automation run without a stop path.** The system continues after a customer opts out, posts a review, or reports a failure. That converts a helpful follow-up into an annoyance.

**Mistake 8: Reporting review count as booked revenue.** The owner cannot decide what to fix if the process stops at a public number.

## What should a well contractor implement on Monday morning?

Install the smallest version that can be run honestly. Do not begin with a complex reputation platform or a large campaign. Begin with a tested link, a completion rule, four templates, one owner, and a log.

### A five-day setup

**Day 1: define completion.** Write the review-ready trigger for pump repair, pump replacement, drilling, and inspection. Include the conditions that put a job on hold.

**Day 2: create the link.** Generate the Google review link or QR code, test it on a phone, and put the date and owner beside it.

**Day 3: approve the copy.** Select one SMS, one email, one technician handoff, and one reminder. Remove all rating requests, incentives, keywords, and positive-only language.

**Day 4: assign the workflow.** Decide who marks the completion trigger, who sends the request, who handles replies, who processes opt-outs, and who records the outcome.

**Day 5: start with current eligible jobs.** Use a small set of clearly completed jobs. Review every sent message and reply before expanding. If a customer reports a service problem, fix the path before sending more requests.

### What should the owner keep in the template library?

Keep one approved version of each item:

- current direct review link and QR code;
- job-state eligibility table;
- pump-repair SMS;
- pump-replacement SMS;
- drilling handoff email;
- inspection or report email;
- technician handoff script;
- one reminder;
- service-recovery reply;
- stop and opt-out rules;
- request log fields;
- person responsible for monthly review.

Put a version date on the library. When the Google link, company name, office number, CRM, or policy changes, test the templates again. A short library that stays accurate beats a folder of 40 variants that nobody trusts.

![Illustration of a well drilling company implementing a review request system on Monday morning](/images/learn/well-drilling-review-request-templates/well-drilling-review-request-templates-well-drilling-review-request-templates-monday-setup.webp)

![Illustration of a well drilling company implementing a review request system on Monday morning](/images/learn/well-drilling-review-request-templates/well-drilling-review-request-templates-well-drilling-review-request-templates-monday-setup.webp)

## What is the final decision for an owner choosing a template?

Choose the message that is accurate for the completed service and easiest for the customer to use. Do not choose the message that sounds most persuasive.

If the job is not truly complete, wait. If the customer did not experience the service, do not ask. If the message requests a rating, rewrite it. If the company cannot handle a reply, fix the office path. If the public proof does not match the services the company wants, improve the service record and website rather than scripting the customer.

The practical standard is simple: one honest request, one direct link, one optional reminder, and a log that follows the path to qualified calls and booked jobs. That is enough to start. Brictale's free territory audit can show where review proof fits within the larger visibility and lead system, but the next operational step belongs to the contractor who owns the customer experience.