Sort plumbing emergency calls and page the on-call plumber

IntermediateA design, not yet run for a business

For:Plumbing

Post this as a projectFree to post. We call you within 2 working days to scope it with you.

The job

Plumbing emergencies do not wait for office hours. A burst pipe, sewage coming up a floor drain or a house with no water all land on the same phone line as "my faucet drips". Evenings and weekends, the on-call plumber is woken for small jobs, or a real flood waits until morning. The owner's question: "which calls tonight could not wait, and did the right person go?"

Trigger and outcome

Trigger: a call, web request or answering-service message arrives outside office hours. Outcome: each request is sorted into "page now", "first thing tomorrow" or "book normally", with a reason; the on-call plumber gets one clear page for the urgent ones; everything is in the job system by morning.

Tools

  • Jev sorts each request against the owner's written rules: active leak, no water, sewage backup, no hot water with a vulnerable person in the house.
  • Hermes keeps the rules, the on-call rota and each customer's history, so a returning customer's old notes come with the page.
  • OpenClaw creates the request in the job system (Jobber, ServiceTitan or Housecall Pro) and sends the page.
  • n8n collects messages from the answering service, web form and voicemail transcripts in one place.

Steps

Plumbing call sorting: a request arrives after hours, a fixed safety script runs first, the agent sorts it with a reason, the on-call plumber confirms the page, and urgent jobs are booked

Safety first, then sorting; the plumber decides whether to roll.

  1. Safety lines first. Any message mentioning a gas smell gets the owner's fixed reply: leave on foot, do not use switches or phones inside, call 911 and the gas company from outside. The agent never sorts these as a booking. The owner writes and approves this text once.
  2. Collect. n8n gathers every after-hours request into one list. The CSR checks, during the first weeks, that the count matches the phone log.
  3. Sort. Jev labels each request and writes a one-line reason ("water coming through ceiling, main not shut"). The on-call plumber can overrule any label.
  4. Page. For "page now", OpenClaw sends the plumber one message with address, problem, customer history and callback number. The plumber calls the customer; the agent does not promise a time.
  5. Book. Urgent jobs and next-morning jobs go into the job system. The CSR reviews the overnight list at opening.

Human checks

  • The safety script is fixed text, written and approved by the owner; the agent cannot reword it.
  • The plumber decides whether to go out tonight. The agent never quotes a call-out price or arrival time.
  • Any reply to a customer is a holding message the owner approved in advance ("we have your request; the on-call plumber will call you").
  • The owner reviews the sorting reasons weekly and changes rules that put the wrong call on top.

Data needed

The owner's urgency rules, the on-call rota and a few weeks of past after-hours messages. For practice, write twenty invented messages for a plumbing company, including one gas smell, two floods and several dripping taps.

Variations

  • Shut-off coaching: add the owner's approved text on finding the main water shut-off.
  • Commercial accounts: restaurants with a blocked grease line go to the top during service hours.
  • Two on-call plumbers: split pages by area.

Where to find more

Further reading, not the source of this design:

Sources

Further reading

More workflow libraries elsewhere

Further reading, not part of our programme: other people's takes on the same jobs.

  • n8n workflow templates ↗

    Community-built automation flows, filterable by sales, marketing, support, document work and AI.

    Read a template for the order of its steps and the apps it touches, then design the approval points yourself.

  • Make templates ↗

    Ready-made scenarios grouped by business area, including invoicing, inventory, HR and email marketing.

    Useful for seeing which systems a small business already connects, before you pick what your agent reads.

  • Zapier templates ↗

    Short trigger-and-action recipes for lead management, support tickets, forms and campaigns.

    Most recipes are one trigger and one action; notice where an agent would add a judgement step and a human check.

  • Claude Cookbooks ↗

    Code notebooks for classification, summarising, extracting data from forms and PDFs, and tool use.

    Open it when a step needs code, such as pulling fields out of a receipt; the ideas carry over to other models.

  • Building effective agents cookbook ↗

    Minimal examples of chaining, routing, parallel calls, orchestrator and workers, and evaluator loops.

    Read it to name the shape of your workflow before you build it; the patterns matter more than the code.

  • Hermes Agent Skills Hub ↗

    Searching skills other people have written for Hermes Agent, from built-in to community sources.

    Read a community skill before you install it, and never give one access to an owner's accounts without review.

  • ClawHub ↗

    The public registry of OpenClaw skills and plugins, including email, calendar, sheets and chat connectors.

    Check who published a skill and what it can touch; treat it as a starting point you read, not a black box.

  • Agent Skills ↗

    The open format for packaging a workflow as a SKILL.md folder that many agents can load.

    Use it when you want to hand a workflow over as a skill file the owner's agent can reuse.