A septic system needs pumping every ~2 to 5 years, and the interval is arithmetic — tank gallons divided by the people living over it. So every property you have ever serviced already has a next due date. You just can't see it, which is why the phone has to ring before you get the work.
Most software helps you chase new leads. We build the register: last pump date, the interval measured at your own tank, next pump due — on every property, rewritten at every visit. Then it calls the ones inside 90 days, clustered by township, and fills the route day for you.
1,000 gal · 4 occupants · conventional gravity · riser present
Homeowners move. Tanks don't — a concrete tank outlives several owners and the county's record is keyed to the ground, not to a name. So the register lives on the property, and three fields carry the whole business.
Stamped at completion, on the property, with the gallons removed and the sludge depth the technician measured at the tank. It is also the document a homeowner will come back asking you for years later, at a closing.
Measured at this tank, not inherited from a category default. Tank size and occupants set the starting number; what the technician finds at each visit corrects it. A tank near the one-third solids threshold early shortens; a thin one lengthens.
Written forward the moment the job closes. A completed pump-out that leaves this field empty has quietly removed a property from your book — so the board treats it as a defect, not an omission.
A water heater's install date fires once, at replacement, and then it's over. A pumping clock fires forever, and every firing writes the next one. That makes the septic customer database — not the septic lead flow — the asset, and it is the one thing a marketing-shaped CRM cannot represent: a recurrence whose period is tuned by a field observation.
Routine pumping is not sold to a customer's preferred time slot. You batch everyone in an area who is due and sell the day. The question your system has to answer is “who in this township is due inside 90 days” — and that is a join between a date and a map, not a calendar lookup. Here is that day filling.
Illustrative example. Those seven stage names are the Routine Pumping & Service board your account actually opens with — not a diagram made for this page. Stage 6 is the one nothing else ships: the visit that just finished writes the next due date before the card closes.
A vacuum truck has to offload at a permitted receiving site before it can take another stop, so the disposal leg caps the day independently of drive time. The board watches gallons hauled against the capacity you set and warns the dispatcher before the route over-commits. It alerts; it does not pretend to be a router.
A locked gate, a dog, ground that won't hold an 18,000-lb truck, or a lid nobody can find is a lost stop plus the drive — and the fix is a records-and-access call, not a rebooking text. They are handled as two different things, because they are.
Buried lids add roughly ~$50–$150 in digging to every visit. Fitting a riser lowers what the customer pays next time and raises your margin per stop at the same moment. Properties without one carry the flag, and the offer goes out with the confirmation.
Effluent that can't leave the tank keeps the tank full. So a property whose pumping interval keeps shortening is telling you its drainfield is failing — and the high-ticket work in this trade almost never arrives as a lead. It arrives as a finding.
Illustrative example. The direction is the trade's own plain rule — a tank that starts needing more pumping than normal points at the drainfield. How much shortening, over how many cycles, is a threshold your account starts with and then calibrates against your own history; it is not an industry standard and it isn't presented to you as one.
You already collect every number this uses. All it needs is that the service history be stored per property and the intervals subtracted — which is exactly what a three-ring binder and a route sheet cannot do.
Once a biomat has formed, a drainfield rarely can be truly repaired, so the honest recommendation is replacement and the system won't offer work it can't deliver. The flag books the soil evaluation and opens the project board.
Steel tanks carry a ~15–20 year life and rusted lids are a collapse risk, not a repair. Concrete past ~30 years in acidic soil is an inspection offer. A cesspool is a replacement conversation that public funding programs frequently cover. Each one is a field on the property, not a memory.
Septic isn't a demand trade with recurrence bolted on. It's the inverse: a recurrence business with demand service bolted on, and two deadline lanes whose dates belong to somebody else entirely.
In most trades an emergency and a big project need different crews and different sales motions. Here the pump-out is the emergency response — what changes is the clock and the arrival window. So the emergency lane gets its own board and its own reserved capacity, and everything else rides the route.
It's “city sewer or septic?” — a different diagnosis and a different truck — and then “stop using water right now,” which has to be said on the call, before dispatch, because every flush makes the backup worse. The intake asks both, and records that the instruction was given.
What the technician writes down — sludge depth against the one-third rule, and whether the liquid sits above or below the outlet — decides whether this was a ~$400 stop or the front end of a five-figure project. Said aloud at the truck and never written is the most common leak in the trade.
A closing date belongs to a lender and a title company. A permit, a maintenance contract and a filing window belong to a county health department. A CRM that models only leads has nowhere to put either one — so it puts them in somebody's head, and that's where they get missed.
Not a blank CRM you have to design. These are the boards your account opens with — the indigo marker is a gate somebody outside your company controls, the gold one is where the money lands.
An alarm light on an aerobic panel is usually an aerator, a tripped breaker or an empty chlorinator — a service visit, not a hazmat event — so it doesn't burn an emergency slot by default. But it starts a filing clock, so it can't be treated as routine either. It gets same-day contact, a scheduled service visit, and the filing timer — and it escalates to the emergency board only when there is sewage present.
Two of the stages above belong to a health department, not to you. The customer-facing follow-up goes quiet in those states and the tasks point at the county instead — a chirpy nurture text firing while an inspector is scheduled reads as incompetence.
Merge them and a soil test gets booked into frozen ground, or a dig date gets set before the permit exists. These are the calendars your account opens with, by name.
Not an availability calendar. The day is assembled from who is due in a township and then offered — and the offload leg is reserved inside it.
Reserved capacity for backups, surfacing sewage and alarm calls, so one bad Saturday doesn't detonate the route. After-hours pricing is stated before the truck rolls.
The only calendar here with a weather window: frozen ground blocks test pits, and seasonal high water table is only observable in certain months in many places. Outside your window it holds the booking and tells you, rather than offering a slot.
Generated from the maintenance contract's own schedule — and it starts a reporting clock on you, not on the customer. These are the densest, most predictable stops on the board.
The date isn't offered, it's calculated: the closing date minus your report turnaround and a buffer. It often consumes an inspector and a pump truck, because several states' transfer inspections require the tank be pumped.
A block on your own calendar for a visit you don't control, so the crew and the excavator aren't booked over the top of an open trench waiting on the county.
Every one of these ships switched on and named for septic. None of them is a template you have to find, wire up and remember to turn on — and several of them exist mainly to know when not to send.
An emergency call, an alarm light, a web or Google Business Profile lead, a title company ordering an inspection, and “when was my tank last pumped” are five different conversations. Each gets its own intake, and the web one captures system type, bedrooms and occupants so the register starts populated instead of back-filled.
The unanswered rural phone is where jobs die before a pipeline ever exists. The text goes out in seconds and opens with sewer-or-septic and the urgency question — not “how can we help?” Outside your hours it says so and holds the thread until morning.
Every property's next due date produces its own outbound, clustered by township before it fires so it lands as a route offer. Past due, the message changes entirely — and the overdue list is a different list, worked differently.
The confirmation carries what the driver needs: the lid offsets from two fixed landmarks, whether there's a riser, the gate code, the dog, the soft spot in the drive. Surfaced at dispatch, not discovered on arrival.
Completion recomputes the interval, compares it to the one before, and raises the drainfield flag when it moves the wrong way. That flag books a soil evaluation and opens the project board. It is the highest-value automation in this trade and it runs on data you already have.
The closing date is captured as the first field, because everything else is computed from it. Follow-up counts down — two weeks, one week, three days, one day — and escalates to the agent, not just the homeowner, because the agent is the one who ordered it.
Where an external clock exists it replaces the generic sequence: a closing, a repair window on a conditional result, a county correction notice, a funding application window. Where none exists, the day-five task lands on the technician who looked in the tank — because the homeowner's real question is “how bad is it,” and only he can answer it.
Design approval and permit issuance are separate events with separate tasks, and the excavation block only releases on the second one. Then the backfill hold, the as-built filing, and the final approval chase — each with a different party owing the next move.
Maintenance contracts and operating permits are flagged at 90, 60 and 30 days before they lapse. Where a county requires a service provider's report before it will renew a homeowner's permit, your document is the prerequisite — so renewal season is an inbound you can get in front of. Requirements vary by county.
The one clean seasonal play in this trade, and it runs against the due register rather than the whole database: pull work out of the spring crunch into fall's slack capacity, dry ground and low water table.
It never goes out on an unresolved backup, a failed or conditional transaction inspection, a job driven by a county enforcement notice, or an open filing. The customer who just learned their house has a five-figure problem is not a review moment. A clean pump-out and a passed inspection are — the passed one most of all, because you just unblocked a sale.
An agent who sent you twelve files last year and two this year is a churned account, and nothing keyed to contacts will ever show you that. Repeat orderers get a quarterly “here's what we did for your closings” touch and a standing records-lookup offer instead of a homeowner drip.
Two of these are records a regulator can ask you for, and the third is the piece of paper a homeowner will come back for years later, at a closing. They are rails, not marketing — they nurture nothing and they ship switched on.
A pump-out receipt has mandated content in many places — date of service, the conditions noted on the tank, risers and effluent filter, and the quantity removed. It generates as a durable file attached to the property, retrievable years later, with your company and license details on it. In Massachusetts, documented annual pumping extends a transfer inspection's validity from two years to three; that is one state's rule, and requirements vary by county.
Every load needs a record of where it was pumped, how it was handled and where it went. The board won't close a leg without the manifest number, the receiving site and the gallons hauled, and it keeps them per load for the retention period your jurisdiction sets. It records; it does not file on your behalf.
After an aerobic service visit the report goes to the county on a clock — fourteen days in Texas, on their own schedule in Florida counties, and other states vary. Completion opens the task with its due date, escalates before it lands, and won't close until the filing is recorded. Missing it is a licensing exposure, not a missed touch. Your window is set to your own jurisdiction at setup.
Inspection frequency, transfer obligations, penalty exposure, permit status — none of it goes out as a statement of law. Every one of those sentences is your own configured jurisdiction language, confirmed with you at setup, or the system doesn't send it. This is a deliberate design choice and it costs nothing operationally.
There is no plan to invent here and no benefit sheet to write. The recurring revenue already exists in the ground: a due date on every property, and on aerobic systems a maintenance contract that a county is keeping score of. The job is to stop losing them.
The clock regenerates on the visit that just ended. No sequence to enroll anyone in, no plan to sell — the annuity is the register, and it only breaks when a job closes without writing the next date.
Aerobic maintenance contracts run a two-year initial term with shorter renewals in the jurisdictions we measured, and they are filed with the permitting authority. The renewal sequence is anchored on the expiry date on the property record.
Where a county tracks permits and a lapsed contract exposes the homeowner, the renewal message writes itself and it is true. It is also the reason the wording is yours, keyed to your jurisdiction and confirmed at setup, rather than ours.
A declined drainfield quote goes back to the register armed. It comes back when the interval shortens again, when the property goes on the market, or when a funding window opens — a buyer's inspector is going to find it anyway.
The routine lane has no proposal and never has one — it closes on the phone or it doesn't happen. Which means the whole business is how many stops the truck makes, and how few of your properties fall off the clock between them.
The pumping interval range across published guidance, computed per property from tank gallons and occupants. One thousand gallons under four people works out near ~2.5 years on one county's chart; the same tank under one person, ~12.
Average residential pump-out in published trade data, in a ~$291–$564 band. At five to eight stops a day, an hour of avoidable driving is a whole ticket.
Per truck per day lost to poor route sequencing in one published example — about one extra stop per truck per week. Illustrative arithmetic, not a projection.
More likely to qualify a lead when the first contact happens inside the first hour, across ~1.25 million leads studied by Harvard Business Review.
Figures are published industry research or illustrative examples, shown to indicate where the opportunity sits — they are not a projection of your results. Pumping intervals and ticket prices are national ranges and vary widely by region, tank size and household. The route-sequencing figure comes from a single published example and its arithmetic is illustrative. The response-time study is cross-industry and directionally relevant to home services rather than native to it.
Configuration is ours, not yours. Here's the sequence — and the one point where we need something only you can give us.
All four boards, and the fields this trade actually needs — system type, tank size and material, tank location notes and whether a riser is present, bedrooms and occupants, last pump date, pump interval, next pump due and the prior interval, last sludge depth, drainfield condition, maintenance contract status and expiry, operating permit expiry, health department jurisdiction, permit number, whether the as-built is on file, and per job the gallons hauled, the disposal site and the manifest number.
An emergency form that opens with sewer-or-septic and the stop-using-water acknowledgement rather than name and email, a routine service request, an inspection order form built for agents and title officers, a records-lookup request, the chat widget and your Google Business Profile — all wired to the boards, with missed-call text-back on and every source tagged so you can see which ones produce.
Text-message registration and your sending domain both require a real human with your business details — regulation, not paperwork we invented. We prepare the submissions; you approve and sign, and that sets your go-live date. Alongside it, the numbers your texts will quote: your license number, your health department jurisdiction and its filing window, your standard pump price, your after-hours rate, and the truck capacity the route cap watches.
Your Square account and dual-priced invoicing go live: text-to-pay from the truck when the receipt issues, the project deposit invoice computed at your deposit percentage of the quoted amount, e-signed proposals on the install lane, and the maintenance contract set up as recurring billing.
Your existing customers are loaded with their last pump dates, intervals computed, next due dates written forward. Then the 90 and 30-day register calls, the overdue list, the interval-shortening detector, contract and permit renewals, the asset-age reactivations, and the fall pre-book campaign — all scheduled, then running whether or not anyone remembers them.
Follow-up that ends in “I'll mail an invoice” is half a system — and on a route day the invoice happens in the driveway. Your account runs on Square for processing, with dual-priced invoicing on top: the cash price is the price, and a customer paying by card sees the card price beside it and chooses.
Receipt Issued generates the regulated document and fires the invoice into the same thread the confirmation ran in, with a pay link. The driver is at the next stop before the customer has finished reading it.
A sold system fires a deposit invoice at your deposit percentage of the quoted amount — before a permit fee is paid or a tank is ordered. A deposit schedule on the card overrides the default when a job needs staged draws.
The aerobic maintenance contract runs as recurring billing rather than an invoice somebody has to remember to send, and a declined card is chased the day it fails — because a lapsed contract is a compliance problem for your customer, not just a missed payment for you.
Route-day tickets, emergency calls, inspection fees, install deposits and contract billing add up to steady card volume at ~3% in processing. Dual pricing hands that cost back. Your title companies and property managers paying by check notice nothing — they already pay the cash price.
Everything above is included in both — all four boards, the register, the compliance rails, the payment rails. The difference is how much marketing and reporting surface you want on top.
Then the only number that matters is whether it puts stops on the truck. It runs against properties you have already serviced and whose due dates you already own — the cheapest work in the trade, and the work that quietly disappears when nobody writes the next date down. If it recovers one stop a month it has covered itself; we're not going to promise you a number beyond that.
Some don't, and the system honors that permanently the first time they say so. But the route offer isn't marketing — it's “we're in your area Tuesday, you're due, want the stop,” which is the same call your office already makes by hand and rarely gets all the way through. It goes out on the channel each customer answered on, and the ones who prefer a phone call become a call task with the script in front of you.
Don't. Route sequencing, truck assignment and the disposal side stay where they are. What moves is the layer above them: the property register and its due dates, the outbound that fills the day before anyone sequences it, the inspection and install lanes, the compliance documents, and the money. This board tells your router who is due; it doesn't try to drive the truck.
Agreed, and it's built that way on purpose. Nothing here asserts what your state or county requires of a homeowner. Every sentence of that kind is your own wording, keyed to your jurisdiction and confirmed with you before it can send — and the filing windows and renewal timings are parameters you set, not national rules we invented. Where we cite a rule anywhere, we name the state it came from.
No, and the stage names above are the first test — those are the boards your account actually opens with. The second test is what you can't buy elsewhere: we went looking for a septic snapshot that ships a due register with a per-property interval, a shortening detector, a disposal manifest gate and a backward-scheduled inspection lane. What is publicly sold is the same niche paragraph with the trade noun swapped, right down to a shared misspelling. That gap is why this build exists.
Board now and the register works your fall — dry ground, low water table, and the spring crunch a little smaller than last year's.
Automate With Us provides software and configuration services. Figures shown are published industry research or illustrative examples — they are not projections, guarantees, or representations of the results you should expect. Individual results depend on your market, pricing, capacity and execution. Processing costs vary by card mix and volume; the ~3% figure is illustrative and your effective rate will differ. Payment processing is provided through Square and is subject to Square's approval and terms. Text-message and email sending are subject to carrier and regulatory registration. Septic inspection, permit, maintenance-contract and reporting requirements are set by state and county and vary by jurisdiction; rules referenced here are attributed to the places they were measured, are shown as examples rather than legal advice, and your account is configured to speak your own jurisdiction's requirements as you confirm them. Terms · Privacy