Theme
Palette
Saved to this browser. Applied before the page paints, so it never flashes.
Home & trade · SK-PLMB
Built for an emergency-led trade: burst pipes triaged in seconds, planned work nurtured separately, and every one-off customer worked again later.
What is in the kit
Every SubaccountKit snapshot contains the same nine components and nothing else. What changes between kits is what they are configured to say and do — everything below is written for the Plumbing Company Sub-Account Kit, laid out in the order it runs.
Stage 01Lead capture and first contact
The first question is about urgency, not about the caller's name. Burst pipes and no-water calls alert the on-call technician instantly; planned work is qualified and booked into the estimate calendar.
Answers the two questions that decide whether a homeowner enquires at all — can you come today, and roughly what will it cost — then captures the address and access notes.
Emergency and planned service pages written separately, with a call-now path on every emergency page and estimate forms that ask what is leaking before anyone rings back.
Stage 02Ten days of multi-channel follow-up
Rings the estimates that stalled at day five, the missed appointments the same afternoon, and past emergency customers six months on with a planned-work reason to talk.
Stage 03Booking and no-show prevention
Emergency bookings get the earliest window and a live technician-en-route message; planned work gets the full 24-hour, 1-hour and 15-minute ladder. Missed visits are called back inside the hour.
Stage 04Reviews and social proof
Job closed, ask sent, while the homeowner is still relieved. One satisfaction question decides whether they see the Google link or a private form and an internal alert.
Runs the cadence afterwards so a plumbing profile grows steadily rather than spiking after a bad winter: a 72-hour reminder, alternating platforms, monthly reporting.
Stage 05Lifetime client nurture
Six months after a one-off emergency, the AI caller opens a conversation about the planned work the homeowner mentioned at the time — which is in the notes, because the chatbot captured it.
Annual water heater checks, seasonal freeze reminders before the first cold week, and a referral offer sent to the street where a job has just finished.
The same nine ship in every kit in the catalog. Delivered within 1–2 business days of purchase confirmation. 12 hours of dedicated installation support, to be used within 14 days of purchase.
The end-to-end run
From a stranger’s first ring to a client of several years. This is the flow the Plumbing Company Sub-Account Kit wires into a sub-account on day one — the nine components above are what you get, and this is how they run together.
A stranger makes contact
Multi-channel entry with intelligent routing
The call is answered on the first ring, at any hour, in a natural speaking voice.
The same assistant, on every inbox the business owns.
A submission is the start of a sequence, not an entry in a spreadsheet.
They are interested but not ready
A ten-day multi-touch sequence across three channels
Establish who this is and why they should keep reading.
Shorter, closer, easier to act on from a phone.
The touch almost every sequence is missing.
They have booked
Protecting the slot from the moment it is taken
Confirmation lands before they have closed the tab.
Three reminders, three different jobs.
The slot is missed, and the phone rings while the intent is still warm.
The job is done
Turning finished work into public evidence
Two hours after the job, one question decides where it goes.
Reviews are answered, which is half of what a profile is judged on.
The reviews go back onto the site rather than sitting on a platform.
They are a client
Keeping the relationship alive for years, not weeks
Low frequency, long horizon, never silent for a whole year.
Existing clients get answers without waiting for office hours.
Nobody is allowed to quietly disappear.
The two performance figures above — a 70% no-show recovery rate and 5–10 reviews a month — are the system's design targets, supplied by the product team. They are not measured results from named customers, and they are never published as review or rating markup.
The problem it is pointed at
A homeowner with water coming through a ceiling does not leave a voicemail. They call the next plumber, and that call is gone forever.
A burst pipe and a bathroom refit enquiry arrive through the same form and receive the same reply, which is wrong for both.
The emergency gets fixed, the invoice gets paid, and nobody ever contacts that household again despite them owning a boiler, a water heater and a bathroom.
The profile has a few five-star reviews from grateful emergencies and one furious one, because nobody asks the ordinary satisfied customer.
Built for
Not built for
If you are in the second list, say so and we will tell you what would actually help — or that nothing we sell would.
A plumbing company taking 110 calls a week, missing about 30, with an average job worth $640 and a 35% close rate on recovered calls.
~18 hours a week in this illustrative scenario — roughly 78 hours a month. Your figures will differ; the arithmetic is shown so you can substitute them.
When it pays back
Two recovered emergency calls a week at $640 and a 35% close rate pays for the kit inside the first fortnight of this scenario. The eighteen hours returned to the office is the return that keeps arriving.
Run your own numbers
These are not measured customer results and never will be presented as such. They are arithmetic. Change any field and the sentence below changes with it — including the sub-account multiplier, because most people reading this are rolling the Plumbing Company Sub-Account Kit out across more than one client.
Illustrative arithmetic only. It assumes every missed enquiry is answered and that your own close rate holds on recovered contacts — neither is guaranteed, and both depend on your offer and your team. No figure here is a measurement from a real customer, and none of it is published as review or rating markup.
A plumbing company’s call mix is more urgent than almost any other trade. That single fact drives every decision here: the receptionist asks about urgency before it asks anything else, emergencies skip every sequence, and the booking system offers the earliest window instead of a menu of dates.
The other half of the revenue is planned: bathrooms, repipes, water heater replacements. It behaves nothing like an emergency, so it runs on its own estimate track with a slower, quote-shaped follow-up rhythm and a call on day five when it goes quiet.
Most plumbing accounts treat an emergency as a transaction. Somebody had a leak, it got fixed, nobody speaks again. The reactivation component treats that customer as a lead for planned work six months later, with a seasonal reason to make contact rather than a discount.
A homeowner whose emergency was solved that morning is the most willing reviewer a trade will ever have, and the willingness decays by the day. Review harvesting fires at job completion for exactly that reason.
Rolling this across a portfolio of trade clients is bulk sub-account provisioning. If the receptionist needs to handle an unusual on-call rota, that is AI receptionist setup.
Delivery and support
Clear edges make a better engagement than a long list of exclusions. Here is where the included support ends and where a quote begins.
Included with every kit
Quoted separately, or run by a VA
All four are real services we offer — seeintegrations, APIs and custom software. They are scoped and quoted so you know the cost before anyone starts.
Reviews
These are sample entries. SubaccountKit is new, so rather than invent testimonials we are showing clearly-labelled placeholders while the deck waits for real customers. Nothing here is published as review or rating markup either — search engines see no ratings from this site until the words are real.
This is a preview card so the review deck can be styled and tested before real feedback exists. The kit went into a fresh sub-account, the load sheet listed every custom value in order, and the build was finished before lunch.
Placeholder copy standing in for a real review. The point being illustrated here is the follow-up ladder stopping the moment someone books, which is the thing most sequences get wrong.
A preview entry, not a customer quote. It exists so the deck renders with a realistic length of text and the shuffle animation can be judged honestly before launch.
Sample text. Deliberately four stars rather than five, so the star row is tested at more than one value and the layout is proven before real reviews arrive.
Another preview card. Real reviews will replace every entry in this file, and the same change that swaps them in also switches the review structured data on.
The receptionist's opening question identifies urgency. A burst pipe or no-water call alerts the on-call technician immediately, skips the nurture entirely, and books the earliest available window rather than offering a choice of dates.
Yes, on a separate track. Bathroom refits, repipes and water heater replacements go into an estimate flow with its own follow-up rhythm, because a homeowner planning work in three months should not be treated like one standing in six inches of water.
They enter the reactivation track. Most plumbing companies treat an emergency as a single transaction; the database reactivation component brings them back for planned work six months later.
The seven stages from signed client to live account.
Conflict list first, sending held back, links re-pointed.
The per-client step no kit can do for you. Start it on day one.
The exit conditions are the test, not the first message.
Comparing kits in the same group?See every home service contractors kit, with what the nine components are configured to do there and who they are wrong for.
Ready when you are
Delivered within 1–2 business days of purchase confirmation, with 12 hours of dedicated installation support to use within 14 days.
No call required to buy a kit · replies within one business day
Accessibility
Text size
Display
Turning animation off tears down the WebGL grid and the particle field — they stop running, they are not just hidden.