AI Voice Feature Now Live
A septic company can finish a good job, collect payment, close the work order, and still miss one of the easiest follow-up opportunities it has. Nobody asks the customer for a review because everyone moves on to the next stop.
Septic service review automation fixes the memory problem, but the useful version is not a blast that asks every contact for five stars. It starts after a legitimate completed service, sends a neutral request to an eligible customer, gives that person a direct way to review the business, and changes course when the customer replies, opts out, or leaves a review.
The first question is not what the text should say. It is what event proves the service is actually finished.
Start from completed service, not from the appointment date
A scheduled job is not the same thing as a completed job. The customer may reschedule. The crew may arrive and discover that the work needs another visit. An inspection may still need a report. A repair could remain open after the first trip.
If the review workflow starts from “appointment was on the calendar,” some customers will receive a review request before the business has finished what it promised.
Use the record that really owns completion. For one septic company, that may be a completed status in field-service software. Another may have staff close the job in an operating system after the technician finishes. If LeadDragon or the underlying HighLevel calendar genuinely represents the service event, HighLevel’s Appointment Status trigger can react when that appointment moves to a status such as Showed.
Do not force the trigger into LeadDragon if another system holds the better truth. A completed-service event can come over through an integration, API, webhook, or a staff update when the current software supports it. The important part is that the review request begins because the business knows the service happened, not because a timer guessed that it probably did.
Decide who is eligible before the request sends
“Completed” narrows the list, but it does not mean every completed record should enter the same review request.
The office may need to exclude duplicate contacts, internal test records, customers who already opted out of the channel, jobs with a service issue still open, and contacts who received a recent review request for the same service. The company may also need a rule for commercial accounts where one contact books the work and another person actually dealt with the crew.
That eligibility check should be operational, not sentimental. Do not ask staff to mark customers as “happy” or “unhappy” so the workflow can decide who gets the Google link. Google allows businesses to ask customers for reviews based on genuine experiences, but its current Maps policy prohibits discouraging negative reviews or selectively soliciting positive ones.
A clean rule is easier to defend and easier for staff to follow: the service is complete, the contact is eligible for the channel, the request is not a duplicate, and there is no record problem that makes the message inappropriate.
Send the first request while the service is still recognizable
The review request does not have to fire the second a technician closes the job. It should arrive while the customer still remembers the service clearly and at a time the business can stand behind the request.
For a routine pump-out completed cleanly in the morning, later that day may make sense. A more involved job may deserve a short delay so the office can confirm the work closed correctly. There is no useful rule that says every septic company must send at exactly the same interval.
The message itself can stay simple:
“Thanks for choosing [Company] for your septic service. If you’d like to share your experience, you can leave a Google review here: [review link].”
That language asks for an honest review. It does not ask for five stars, tell the customer what to write, or imply that only praise is welcome.
HighLevel’s Review Request action supports automated requests through workflows, and its Reputation settings let an account choose the review link, message templates, timing, and retry behavior. If Google is the destination, use the direct review path tied to the correct business profile rather than making the customer search for the company and hope they choose the right listing.
SMS and email can do the same job differently
SMS is useful because the customer can see the request quickly and tap the review link from the same phone. Email gives the company more room for branding or service context without cramming everything into one text.
Pick the channel based on the permission and contact information the business actually has. HighLevel’s current LC Phone Messaging Policy requires valid SMS permission, sender identification, and a clear opt-out path for outbound business texting. A prior service relationship does not erase those requirements.
Sending through two channels does not automatically make the workflow better. If the customer receives a text at 3:00 p.m., an email at 3:05, another text the next morning, and another email the day after that, the automation has turned a small request into noise.
A septic company can use one primary channel and a restrained fallback if it has a reason. The sequence should feel like a reminder, not a campaign that keeps pushing until the customer gives in.
A reasonable follow-up sequence has an end
HighLevel’s current review-request settings can control an initial delay, retry interval, and maximum retries. That is useful because the business can define the end before anybody enters the workflow.
One request may be enough for some companies. Another may send a single reminder a few days later if the customer has not clicked the review link. The exact cadence should come from the business’s customer experience and message volume.
Do not mistake “maximum retries” for a target you need to use. The system may allow several attempts. That does not mean a septic customer needs several asks for the same job.
The workflow should also distinguish a link click from a posted review. A click tells you the customer opened the review path. It does not prove they submitted anything. When connected review platforms send a new review into HighLevel’s Reputation area, HighLevel also has a New Review Received trigger that can start a separate post-review action.
Track each event for what it actually means.
Customer replies should interrupt the script
Some customers will reply to the message instead of tapping the review link.
“Thanks, everything was great” is easy. A short human thank-you may be enough.
“Can you send my receipt?” is not a review problem. It is an office request.
“The lid area still looks wrong” or “I thought someone was coming back” needs staff attention. The automation should create a task or alert the right person and stop the automatic review reminders from talking over the customer.
That stop is about customer service, not review filtering. The customer already received the same neutral review opportunity as other eligible customers. Do not make a private satisfaction survey the gatekeeper that decides whether the Google link appears.
If the company first asks, “Were you satisfied?” and only gives happy respondents a public review link while unhappy respondents get sent to a private form, that is sentiment-based review gating. Google’s current Maps policy prohibits selectively soliciting positive reviews and discouraging negative reviews.
Handle the service concern because it is a service concern. Keep the review request neutral.
Do not buy, reward, or script the review
A discount on the next pump-out, a gift card, a raffle entry, or another reward tied to posting a review may sound like an easy way to improve response. Google’s Business Profile guidance says incentives for posting, changing, or removing reviews are prohibited.
The same problem appears when the message pressures the customer toward a particular rating:
“Leave us a five-star review.”
“If we earned five stars, click here.”
“Tell everyone how great your technician was.”
Those messages are trying to shape the rating or contents of the review instead of asking for the customer’s genuine experience. Google’s policy allows merchants to solicit genuine reviews without incentives or attempts to influence the rating or review text.
The request can still be warm. Name the company, thank the customer, and give them a direct link. Just do not turn the review into a transaction.
Stop conditions keep the workflow from becoming embarrassing
A post-service review workflow needs several ways out.
If the customer opts out of SMS, stop using SMS. A new review from a connected platform can close the request when the account can associate it with that customer. When a customer replies with a service concern, pause the automated requests and hand the conversation to staff. An invalid phone number or email should end retries to that broken destination.
A manual stop also matters. Office staff may learn that the listed customer was not the person who dealt with the crew, the contact record is wrong, or the request should not continue for another legitimate reason.
The end state should be obvious when somebody opens the contact later. Nobody should have to read an old conversation thread to figure out whether the review workflow is still active.
Track the outcome, not just the send count
“Review request sent” is useful, but it is only the beginning of the reporting.
A small septic office should be able to distinguish contacts who were requested, customers who replied, people who clicked the review path when that data is available, reviews received through connected platforms, and contacts who opted out or became ineligible.
Those states answer different questions.
Requested tells you the workflow fired.
Responded tells you the message opened a conversation.
Reviewed tells you a public review actually arrived.
Opted out tells you the channel should not continue.
A service concern tells you the customer needs attention before anyone worries about reputation metrics.
Do not collapse those outcomes into one “review campaign” number. A septic company can send hundreds of requests and still have a poor process if complaints sit unanswered or staff cannot tell which jobs generated genuine reviews.
Reputation management starts after the request too
Review automation handles the ask. Reputation management is larger.
A new review may deserve a response from the business. A negative review may expose a service problem that needs an internal follow-up. Several similar comments may point to a recurring customer-experience issue. A positive review can still deserve a simple thank-you.
LeadDragon’s current platform includes reputation-management tools, and the underlying HighLevel system can receive reviews from connected platforms and use review events in workflows. That makes the review request one piece of the process, not the whole reputation program.
Do not let automation turn review management into “send link, count stars, done.” Somebody still owns the public response, the service recovery, and the decision about what the business learns from repeated feedback.
Let the septic operating system keep the service truth
This article is about the customer-facing follow-up after work is complete. It is not a reason to rebuild septic dispatch, routing, invoices, tank history, manifests, or field notes inside LeadDragon.
If the septic company’s field-service system knows when the job truly closes, keep that system as the source for job completion. Pass only the event or status LeadDragon needs to start the communication. If the two systems do not connect cleanly, a staff-controlled completion field can be safer than pretending the CRM knows more than it does.
The boundary matters because review automation depends on one piece of operating truth: the service was legitimately completed. Once that signal arrives, LeadDragon can handle the communication side around it.
A future service can create a new review opportunity
A customer who leaves a review after a pump-out this year may call again years later for another legitimate service. The old workflow should not permanently block that person from ever receiving another review request.
Reset based on a new completed-service event, not merely on time passing.
That means the company may keep a record of the last review request date or the service tied to that request. When a new job finishes later, the business can decide whether another neutral ask is appropriate. The purpose is to avoid duplicate pressure for one job while still recognizing that a future service is a new customer experience.
There is no need to ask after every tiny interaction. The rule should match the kind of service the company wants reviewed and the frequency that feels reasonable for its customers.
Test septic service review automation with real exceptions
Before turning the workflow on for every completed job, run it against a small batch that includes more than ideal cases.
Use a clean completed job. Then test a customer with SMS DND, a duplicate contact, a service concern, a wrong email, a customer who replies instead of reviewing, and a contact who already received a recent request.
The workflow is ready when the office can explain what happens in each case without guessing.
A good test also proves the direct review link opens the correct Google Business Profile, the message identifies the company, opt-outs work, replies reach a person, retries stop when they should, and the reporting does not confuse clicks with reviews.
That is the practical value of septic service review automation. It removes the memory burden without removing judgment from the business.
If your septic company already finishes good work but review requests depend on somebody remembering at the end of a busy day, LeadDragon can handle the CRM, communication, workflow, and reputation side around that process. Watch the 5-minute LeadDragon demo or book a live demo to see how that customer follow-up can fit around the software you already use to run the field work.
