Exactly two messages. Never a third.
The second goes out 7 days later. Then it stops, answer or no answer.
The second goes out 7 days later. Then it stops, answer or no answer.
A septic tank gets pumped every 3 to 5 years. That’s the clock. It started the day you finished the job, and it’s running on every customer you have ever served.
When it runs out, he doesn’t call you. He calls whoever comes up first when he searches. Not because he was unhappy. Because three years went by and your number isn’t in his phone anymore.
Below is the exact list of rules the rebook system follows to get to him first. There’s nothing clever in it. Most of it is a list of things the system will not do.
Every day it counts the days since each customer’s last finished job, and checks that number against how often that customer needs service.
You pick the cap: 3, 5, or 10 a day. We recommend 5. You should never get back more calls than you can run in one day.
Per person, not per service. A customer with three services on file is still one human being with one phone.
Somebody who said no three times is telling you something. The system listens and stops writing to him.
The system checks all five before every send, on every customer, every day.
It fails toward silence. A message built on a guess costs you more than a message you never sent.
No Sundays. Nobody wants a text from his septic company on a Sunday morning.
It looks like this: “60 customers are overdue. 5 a day for 12 days. Start?” You answer once. You don’t open it again.
When somebody answers yes, the booking step takes over, and that step asks you before it puts anything on your calendar.
Because that’s what it is. His tank is due. There’s no discount in the message and nothing to sign up for.
Most of what gets sold as automation is a blast. One list, one message, everybody at the same time. It works for about a week, and then your customers stop reading anything that comes from you.
This is the opposite. It watches one clock per customer, and it holds back far more often than it sends. The numbers above are ceilings, not settings. You can’t raise them, and neither can we.
The whole thing runs on one piece of information: the date of the last finished job, customer by customer. In most shops that lives in a spreadsheet, an old system, a paper folder, or the owner’s phone.
We load it by hand when we set you up. It takes about two hours. You send what you have, in whatever shape it’s in, and you’re done with that part forever.
If a customer’s date can’t be confirmed, that customer sits out. He doesn’t get a guess.
This is a rule sheet, not a case study or a client result.
It shows the mechanism and its limits. Vercon has no confirmed septic client outcome to publish.
It counts the days since that customer’s last finished job and compares it to how often that customer needs service. Every customer has his own clock. There’s no single list and no single send date.
That’s normal. A spreadsheet, an old system, a paper folder, or your phone contacts all work. You send what you have and we load it by hand when we set you up. It takes about two hours on our side.
Each person gets two messages at most, no more than one “you’re due” every six months, inside business hours, and never on a Sunday. Three no answers in a row and he comes out of the system for good.
As many as you say. The cap is 3, 5, or 10 a day, and we recommend 5. It works the oldest customers first, so the ones who have been gone the longest hear from you first.
The reply goes to the booking step, which handles the back and forth about the day and the time. Nothing lands on your calendar until you approve it.
No. We build it, we load your history, and we run it. On day one you answer one question to start it. After that it runs without you.
Vercon has no confirmed septic client case or outcome to publish. This page demonstrates the operating rules, not a customer result.
Book a call. We’ll go through your customer list, count how many are already past due, and show you what the first 12 days would look like. If it isn’t a fit, you’ll know on the call.