Workflow Template
Blocked drain service request Workflow
Manages a plumbing business's blocked drain service requests end-to-end: intake and acknowledgement, urgency-based booking with a visit date and assigned plumber, plumber field work capturing cause/method/outcome, and outcome-based customer communication (completed with a feedback survey, further work quoting, or unable to complete).
When a blocked drain call comes in, urgent jobs get buried in the same inbox as routine ones, and the office ends up chasing plumbers for what they found on-site while customers wait to hear back. This workflow captures the request, splits urgent bookings (1 day) from standard ones (3 days), and gives the plumber a single task to record the cause, method and outcome that then drives what the customer is told next. The result is a team that books faster, keeps a full record of every job, and sends the right follow-up — completion summary, further-work quote, or unable-to-complete notice — without manual chasing.
Business Outcomes
- Faster response to urgent blockages through automatic 1-day vs 3-day booking deadlines
- Fewer missed follow-ups thanks to automatic completion, further-work, and unable-to-complete emails
- More consistent field records with cause, method, work done and photos captured on every job
- Improved visibility into satisfaction with a feedback request sent automatically 2 days after completion
- Less manual admin for the office when scheduling, quoting and status updates are handled by the workflow
Workflow Steps
Steps
- 1Create service request recordcreate record
Creates the drain service request record from the submitted form.
- 2Set status to New Requestupdate record
Marks the record as a new request.
- 3Email acknowledgementsend email
Sends the customer an acknowledgement email with their reference number.
- 4Route on urgency
Routes the booking task with a different due date depending on urgency.
urgency: "Urgent"→Office: book urgent visiturgency: "Standard"→Office: book standard visitDefault→Office: book standard visit - 5Office: book urgent visitcreate task
Asks the office to book an urgent visit within 1 day, recording the visit date and assigned plumber.
- 6Office: book standard visitcreate task
Asks the office to book a standard visit within 3 days, recording the visit date and assigned plumber.
- 7Save booking details and set status to Bookedupdate record
Persists the visit date and assigned plumber to the record and updates status to Booked.
- 8Email customer the visit datesend email
Notifies the customer of the confirmed visit date.
- 9Plumber: perform job and record findingscreate task
Gives the assigned plumber a task with no due date to record the cause, clearing method, work done, photos and outcome.
- 10Save job detailsupdate record
Persists the cause, clearing method, work done, photos and outcome to the record.
- 11Route on job outcome
Routes to completed, further-work, or unable-to-complete handling based on the plumber's recorded outcome.
job_outcome: "Cleared"→Set status to Completedjob_outcome: "Further work needed"→Set status to Further Work Requiredjob_outcome: "Unable to complete"→Set status to Unable to CompleteDefault→Set status to Unable to Complete - 12Set status to Completedupdate record
Updates the record status to Completed.
- 13Email completion summarysend email
Sends the customer a summary of the work done.
- 14Wait 2 days before feedback request
Pauses for two days before requesting customer feedback.
- 15Request customer feedbackrequest external input
Sends the customer a feedback form asking for a 1-5 rating and comments.
- 16Set status to Further Work Requiredupdate record
Updates the record status to Further Work Required.
- 17Email findings and further work neededsend email
Sends the customer the plumber's findings and the work still needed.
- 18Office: prepare quote for further workcreate task
Gives the office a task due in 2 days to prepare a quote for the further work, without waiting for it.
- 19Set status to Unable to Completeupdate record
Updates the record status to Unable to Complete.
- 20Email findings for unable to completesend email
Sends the customer the plumber's findings when the job could not be completed.
Fields
- Full Name*
- Email Address*
- Mobile Number*
- Site Address*
- Where is the blockage?*
- How long has this been happening?
- +15 more fields
Forms
Blocked Drain Service Request
11 fields
Data Views
Drain Service Requests
customer_name, site_address, blockage_type, urgency +3 more
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send email in the workflow
AWS SES
Similar Categories
FAQs
What happens if a customer marks their request as Urgent but the office can't book within 1 day?
The workflow assigns the office a booking task with a 1-day due date when urgency is set to Urgent, but the task stays open until the office records a Scheduled Visit Date and Assigned Plumber. The record's status stays at New Request until that step is completed, so nothing moves forward silently. The due date is a target shown on the task, not a hard system block, so the office can complete it whenever the visit is actually confirmed.
Can this handle urgency values other than Urgent or Standard?
Yes, the routing step includes an 'otherwise' branch for any other urgency value submitted on the form. This means the workflow can be extended to route unusual or blank urgency entries to a specific booking task if needed. The workflow editor lets a workspace add or adjust these branches without redevelopment.
What if the plumber's outcome doesn't match Cleared, Further work needed, or Unable to complete?
The job outcome routing step also has an 'otherwise' branch to catch any other value recorded on the plumber's task. This keeps the record moving through a defined path instead of stalling, and the outcome value itself is still saved to the record. A workspace can edit this branch in the workflow editor to send a different email or task if their plumbers use additional outcome labels.
Who is responsible for each step in this workflow?
The office handles both booking tasks (urgent and standard visits) and the further-work quote task, while the assigned plumber completes the field task recording cause, method, work done, photos and outcome. All of these are assigned to workspace members, and the customer takes part only through the request form and emailed forms, without needing an account. Every task and status change is added to the record's timeline.
Does the office need to wait for the quote before the customer hears about further work?
No, the customer is emailed the plumber's findings and the further-work notice as soon as the outcome is routed, before the quote task is even due. The office quote task is due 2 days later and doesn't hold up that customer email, since the workflow doesn't wait for it. The quote notes are saved to that task and shown in the record's task list.
What happens to the feedback survey if the customer doesn't respond?
The feedback form is sent by email 2 days after the completion summary, and since the workflow doesn't wait for it, the record's status remains Completed regardless of whether the customer replies. If a response is submitted, the rating and comments are saved as answers on the record. This keeps the completed job visible in table views and dashboards without depending on customer action.
Can we customise the booking deadlines or the email content?
Yes, due dates for the booking and quote tasks, and the wording of any email, can be changed by describing the change in plain English or editing the step directly in the workflow editor. Earlier versions of the workflow are kept, so changes can be reviewed or reverted. This makes it straightforward to adjust urgency thresholds or messaging as the business's process evolves.
What information does the plumber actually record on-site, and where does it go?
The plumber's task captures the Cause of Blockage, Clearing Method Used, Work Done, Job Photos and Outcome, and because the workflow waits for this task, all five fields are saved directly to the service request record. This data then drives which outcome branch the record takes next. It also stays visible in the record's timeline for reference on future jobs at the same site.
How does the record show where a job currently stands?
Each service request has a status — New Request, Booked, Completed, Further Work Required, or Unable to Complete — that updates automatically as the workflow progresses. Table views and dashboards group records by this status, and the full timeline of tasks, emails and status changes is kept on the record. Businesses using this data for their own compliance or record-keeping needs should confirm it meets their specific obligations.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
