Illustrative case study. BlueLine Plumbing is a fictional example built from common trades deployment patterns. Metrics shown are representative, not verified customer results.

The Company

BlueLine Plumbing is a fictional five-truck plumbing firm based in Auckland, New Zealand. They cover the central suburbs and parts of the North Shore — standard residential and light commercial work, with after-hours emergency call-outs as a meaningful revenue line.

Like most Kiwi trades businesses, their office closes at 5pm. On-call plumbers rotate nights and weekends. Before voice AI, the business line forwarded to a mobile that often rang out while the on-call tech was under a house or driving between jobs.

The Challenge

BlueLine’s owner, Sarah Chen (fictional), tracked missed calls for two weeks and found a pattern:

• Emergency callers didn’t leave voicemails. They rang the next plumber on Google.
• On-call staff returned voicemails 30–60 minutes later — too late for true emergencies.
• Routine overnight enquiries (dripping taps, quote requests) were ignored until morning, and half had already booked elsewhere.
• Office admin spent Monday mornings returning calls that could have been booked automatically.

“We weren’t losing jobs because we couldn’t do the work,” Sarah says in this illustrative scenario. “We were losing them because nobody picked up.”

The team considered a human answering service but balked at per-minute pricing during storm weeks — and operators couldn’t reliably tell a burst main from a slow drip without taking a message anyway.

Why Help Genie

BlueLine needed:

• Voice-first coverage on their existing NZ business number after hours
• Triage logic they controlled — their definition of emergency, not a call centre script
• Flat pricing predictable for a small firm (Professional at $169 NZD per genie/month — see the ROI calculator)
• No developers — Sarah’s office manager could set it up

Help Genie’s trades preset and the voice AI for trades complete guide matched the workflow. They also linked the genie from their Trades hub demo path for website enquiries.

Implementation

BlueLine stood up one genie in an afternoon:

1. Knowledge base — service area postcodes, callout ranges in NZD, emergency definitions (active leak, no hot water in winter, sewage backup), on-call rotation numbers
2. Triage paths — emergency dispatch vs next-day booking
3. Branding — “BlueLine Plumbing” greeting, calm voice, logo on website widget
4. Deploy — forwarded business line to genie after 5pm and all weekend; widget on contact page
5. Test calls — burst pipe scenario, dripping tap, out-of-area caller

The office manager ran three test calls before enabling forward. On-call plumber Mike received a text with address and fault summary on the emergency test within seconds.

The Results (Illustrative)

After 90 days in this illustrative scenario, BlueLine reports:

Metric	Before	After (illustrative)
After-hours calls answered	~35%	100%
Emergency dispatch	Voicemail callback ~45 min	Immediate triage + alert
Routine overnight jobs captured	0–1/week	4–6/week

Sarah reviews transcripts Monday mornings — about ten minutes — and adds FAQ entries when callers ask something new. One knowledge base update (“do you service gas hot water cylinders?”) eliminated five repeat calls the following week.

Mike (on-call plumber): “I used to get voicemails I couldn’t understand — no address, just ‘urgent leak.’ Now I get a text with suburb, fault, and whether they’ve shut the mains. I show up knowing what I’m walking into.”

What They’d Tell You

Start with after hours only. BlueLine didn’t change daytime operations for two months — zero risk while they learned.

Write your emergency definition in plain English. The genie follows it literally.

Use the ROI calculator before you debate cost. One recovered emergency call-out often covers the month.

What’s Next

In this illustrative roadmap, BlueLine plans overflow routing during Monday rush and a second genie trained on drainage-specific FAQs. Explore similar setups on discover.