Why Aurora plumbing requests show up missing half the job

It is a Tuesday in Aurora, and by 8:15 the shop has six new requests. Two came through the website form: one says "water heater not working" with a phone number, and the other says "leak" and nothing else. Two are voicemails, one from a man who reads his address too fast to catch. One is a text with a blurry photo of a sink cabinet. The sixth is a note that says "call back" with no name.

Whoever runs the office, or you from the truck between stops, now calls each of them back to ask what the form should have asked. Gas or electric? How old is the heater? Is the water off? Which sink, and are the other drains slow too? Is there a dog? Some of them do not pick up.

Why a vague request costs more than the callback

Every question you skip at intake still gets asked, just later, and usually from the truck.

Phone tag comes first. Each thin request needs a round of calls before it can be scheduled, and the woman who typed "leak" spends that time at home with a bucket. A shop that asked her the right questions on first contact is already sending someone.

Then there is the truck. "Water heater not working" can mean a gas tank that will not light, an electric tank with a burned out element, or a tankless unit showing an error code. Each needs different parts. Guess wrong and the visit turns into a diagnosis, a supply house run, and a return trip, which the customer notices even if you do not charge for it.

A main line backing up into the basement and a slow bathroom sink both arrive as "drain clogged." One needs the cable machine and a long block of the day, the other is a quick stop, and a day planned on guesses rarely survives until lunch.

Nobody tracks the requests that never become jobs. The man with the rushed address and the "call back" with no name are still sitting in voicemail. Nobody decided to drop them. They never got a second touch because they were not on any list.

What intake looks like when the questions come first

Every request comes in through one path and gets the questions its job type needs before it reaches your list.

• Website forms, texts, voicemails, and missed calls land in one queue, stamped with the time and the source.
• The first question is the job type: water heater, leak, drain, sewer, or something else.
• Each job type gets a short question set that you write. A water heater request asks gas or electric, tank or tankless, and roughly how old, plus a photo of the label. A leak asks where, whether water is still running, and whether they found the main shutoff. A drain asks which fixture and whether other drains are slow.
• Address and access get confirmed in writing, gate code and dog included, and an address from a voicemail gets read back by text.
• Missing answers get one follow-up text. If there is still no reply, the request stays on the list marked incomplete.
• Active water, sewage coming up, or no water at all skips the line and goes to whoever has the phones that day.
• The finished request drops into whatever you already schedule and dispatch from, with a summary the tech can read in the driveway, and the customer gets a text saying it is in.

Gas smells never get a questionnaire. If a customer mentions one, the system sends them what Nicor Gas tells customers to do: leave the area right away, avoid anything that could make a spark, including light switches and phones, and call Nicor Gas at 888.642.6748 and 911 once they are somewhere safe. Then it alerts you. You approve that wording first.

The closest thing I have built is intake for a freight forwarder. Quote, import, export, and general inquiries each have their own form, and all of them land in one tracked place, so the shipping details arrive with the request. For a Chicago area pool service company, I built lead capture that tracks each request from first contact to a job. Plumbing has the same gap with different questions.

What stays with a person

The diagnosis stays with the plumber. A photo of a label tells you what to bring. I would not let an intake flow tell a homeowner what is wrong or what it will cost.

So does priority. The system flags what sounds urgent using rules you set, but whether a leak jumps ahead of a scheduled water heater swap is a call for whoever is running the day.

Some customers should reach a person quickly, like the homeowner who does not want to text a photo or the one still upset about the last visit. The intake flags them for a call from your office.

The questions come from you and your techs, because you know which details change what goes on the truck. I build the flow around your list, and the list gets better every time a tech learns something on site that intake should have asked about.

When this is not worth building

If you run one truck and ask the questions yourself when you answer the phone, your intake already lives in your head and works.

If most of your work arrives as detailed work orders from builders or property managers, handle the few gaps by hand.

If neither describes you, builds start at $500 one time, then a flat monthly from $99 after an included run-in period, cancellable whenever it stops earning its keep. More on the plumbing page and on what I build for businesses in Aurora.

Where to start

Start with a free 20 minute process audit. We pull one week of service requests, count the callbacks and return trips, and see whether fixing intake pays for itself. Start here.