← All postsHow-to

Plumbing dispatch software: emergencies, parts and the second visit

Plumbing dispatch software is judged on how it handles emergency calls and whether the engineer arrives with the right part. What matters in the tool, and the habits that cut return visits.

How-toP

Plumbing dispatch software has one defining requirement: it must cope with work that cannot wait. A leak does not join the back of the queue, so the day is rebuilt several times, and the difference between a profitable plumbing operation and a chaotic one is usually how quickly the next job is reassigned and whether the engineer arrives carrying the part the job needs.

What plumbing dispatch software must handle

  • Fast intake that captures what decides the visit: symptom, property type, water off or on, access arrangements.
  • Reassignment in seconds, including telling the customer whose slot moved.
  • Van stock per engineer, so the dispatcher can send whoever has the fitting rather than whoever is nearest.
  • Emergency call-out rates and after-hours pricing applied automatically.
  • Job history per property, which matters in flats and managed blocks where the same fault recurs.
  • Photos before and after, for insurance work and for disputes about damage.
  • Gas and unvented certifications where the work requires them, checked at assignment.

The second visit is where the margin goes

A return visit costs travel, a slot that could have served a new customer, and the customer's patience. Most repeat visits trace back to three causes: the symptom was recorded too vaguely to predict the part, van stock was unknown, or nobody asked whether the property had unusual fittings. Fixing the intake questions is cheaper than any software feature, and it is the change that most improves first-time fix rate in a small plumbing business.

Ask on intake whether the water can be isolated and where the stopcock is. It sounds trivial and it changes both the length of the visit and what the engineer needs to bring.

Running it without buying software yet

  1. Standardise five intake questions and use them on every call, including out of hours.
  2. Keep one shared job list with status, so any dispatcher can pick up the day.
  3. Record van stock weekly — approximate is fine, unknown is not.
  4. Log the cause of every return visit for a month and fix the top one.
  5. Keep property history by address, not by customer name, because tenants change and pipework does not.

Ettex Records fits that stage: jobs with status and priority, properties with history and fittings, engineers with certifications and van stock. The same fields transfer to a dedicated tool later, and the wider dispatch mechanics — intake, skills matching, travel time — are described in the general service dispatch software guide.

Frequently asked

How should emergency plumbing calls be prioritised?

By harm and spread: uncontained water or no water in an occupied property outranks a dripping tap. Agree the tiers in advance so the dispatcher is applying a rule rather than judging under pressure.

Does dispatch software reduce return visits?

Indirectly. It helps by showing van stock and property history; the bigger gain comes from better intake questions, which cost nothing.

What should be recorded after a plumbing job?

Work done, parts used, photos before and after, meter or pressure readings where relevant, and any follow-up needed — captured on site rather than written up later.

MI
Written by Maria I.

Part of the Ettex team — writing about product, engineering and the future of work.

More posts
Get the best of the Ettex blogProduct news, guides and tips — straight to your inbox, no spam.