M.Ali
Demo case study · Plumbing

Give a missed enquiry a clearer next step.

This self-initiated prototype explores how a plumber could review a missed-call enquiry, see its key details together, and decide what to do next.

Try the four scenariosBack to overview
The situation

A call comes in during a job.

The business may need to understand what is leaking, how urgent it is, where the customer is, and how to follow up. This sample journey shows how those details could be gathered and surfaced for human review.

Interactive prototype

Explore four sample enquiries.

Choose a scenario to see the details a plumber could review. Every person, business, and enquiry shown here is fictional.

01 / SAMPLE ENQUIRY

Choose a scenario

The selection updates this page preview only.

What is connected?

This web preview makes no n8n, Telegram, or Google Calendar calls. Separately, one local workflow run created a real event in the dedicated demo calendar and sent Telegram business notifications. No customer SMS or WhatsApp is sent.

02 / OWNER REVIEW

Business notification preview

A new enquiry is ready for review.

SIMULATED TELEGRAM-STYLE ALERT

NEW PLUMBING ENQUIRY — DEMO

Next step: Review the details and call to confirm availability and price.

A plumber reviews the enquiry and confirms job scope, price, travel, and attendance. A calendar entry is not a confirmed service appointment.

This is a self-initiated prototype, not client work, production software, or evidence of business results. Missed-call capture and the customer reply are simulated inputs.

Sample journey

From missed call to owner review.

The sample describes a possible customer journey. The missed call and reply in the workflow are simulated inputs.

  1. Simulated missed call and replyFictional lead details enter the local workflow.
  2. Check and organize the enquiryThe workflow validates available details and qualifies the issue, urgency, location, and requested next action.
  3. Flag missing contact informationAn enquiry without a phone number is marked for manual review instead of taking the normal callback path.
  4. Store the lead and alert the businessLead storage and Telegram business notification were exercised in the local plumber workflow copy.
  5. Check a requested calendar slotThe verified run found one requested slot free and created a 30-minute event in the dedicated demo calendar.
  6. Plumber reviews and confirmsThe plumber must confirm job scope, price, travel, and attendance with the customer.
Verification and limits

What was tested, and what remains a demo.

The project verification record dated 1 October 2026 is the source for these statements.

TESTED LOCALLY

One booking path completed

The plumber workflow copy ran through the local test webhook and Ollama. It validated and qualified fictional lead details, stored the lead, checked calendar availability, created one 30-minute event in “Lead Recovery Demo Bookings” for 5 October 2026, 10:00–10:30 Europe/Rome, and sent Telegram business notifications to the workflow’s saved demo chat.

SIMULATED HERE

The interactive four-scenario preview

The buttons change only the page preview. They do not call n8n, Telegram, or Google Calendar. Missed-call capture and the customer reply are simulated. No customer SMS or WhatsApp is sent.

OUTSIDE THIS DEMO

Customer-facing production setup

Real phone capture, customer messaging, authentication, consent, privacy and retention, retries, monitoring, service-area rules, and emergency handling have not been set up or tested for a client.

BOOKING LIMIT

A calendar event is not a confirmed appointment

The test event is real in a dedicated demo calendar and contains fictional details. A plumber reviews every enquiry and confirms job scope, price, travel, and attendance. The demo does not promise an emergency response.

Observed confirmation

One successful run, with matching notifications.

During this review, the local n8n interface showed execution #173 as successful in 8.112 seconds. The matching Telegram booking notice and Google Calendar event were visible in their connected demo accounts.

N8N · 1 OCT 2026

Execution #173 succeeded

The local workflow execution list displayed “Succeeded” for the run started at 22:50:02. The executed workflow map included the lead storage, calendar booking, and Telegram alert path.

GOOGLE CALENDAR · DEMO CALENDAR

[DEMO] Alex Morgan — leak repair

The connected “Lead Recovery Demo Bookings” calendar showed the event on Monday 5 October, 10:00–10:30. Its details identify it as a lead-recovery demo booking with fictional contact information.

TELEGRAM · BUSINESS ALERT

Booking confirmation delivered

The “Lead Recovery Demo” Telegram chat showed the business alert and a separate “DEMO BOOKING CREATED” notice for the same fictional lead and requested start time. These were owner notifications; no message went to the fictional customer.

Captured test evidence

Workflow run, owner alert, and calendar event.

These screenshots show the local workflow execution and its matching fictional test in connected demo accounts. They document business-side notifications and a demo-calendar event, not a customer-confirmed appointment.

Local n8n executions list showing Plumber Lead Recovery Demo execution 173 with Success status and 8.112 second run time.
N8N · LOCAL EXECUTIONExecution #173 completed successfullyThe local n8n execution list shows the plumber demo run as successful in 8.112 seconds. This records a local prototype test, not production use or a client result.
Telegram Lead Recovery Demo chat showing the DEMO BOOKING CREATED notification and the matching Alex Morgan plumbing enquiry.
TELEGRAM · OWNER NOTIFICATIONBooking notice delivered to the businessThe alert and booking notice went to the workflow’s saved demo chat. No message was sent to the fictional customer.
Google Calendar event details for the fictional Alex Morgan leak repair in Lead Recovery Demo Bookings on 5 October 2026, 10 to 10:30 am.
GOOGLE CALENDAR · DEMO EVENTRequested slot added to the demo calendarThe 30-minute event contains fictional details. A plumber still confirms scope, price, travel, and attendance.
Prototype only. Riverside Plumbing, Alex Morgan, the contact details, and the enquiry are fictional. This is self-initiated prototype work, not client work, production software, or evidence of business results. The local workflow copy remains unpublished and uses a test webhook without authentication; it is not suitable for internet exposure or real customer data.
Discuss your process

Where do new enquiries get stuck?

DM “CALLS” on Instagram with your trade and how you currently handle new enquiries.

Message @apps.bymukarram