Workflow Template

High-pressure jetting service record Workflow

Captures a high-pressure jetting service record from the field, sets service status based on the jetting result, and triggers the appropriate customer communication and follow-up (feedback request for cleared jobs, or an office quoting task for jobs needing further work).

Drainage and jetting operations serving multiple customers and sites need a consistent, visible way to capture what happened in the field and act on it without delay. This workflow captures the jetting service record submitted by the drainer, sets the service status based on whether the line was cleared, partly cleared, or not cleared, and coordinates the resulting customer communication and office follow-up. Drainers, customers, and office staff each interact with a defined stage of the record, from initial logging through to feedback or quoting.

Business Outcomes

Helps standardise how jetting job details and results are captured from the field
Supports faster, more consistent customer communication after each job
Makes it easier to track which jobs need further work and follow up on quoting
Reduces manual handoffs between field and office teams for quote preparation
Provides a visible status and timeline for every jetting job from start to resolution

Workflow Steps

Steps

1
Create jetting service recordcreate record
Creates the jetting service record from the submitted service form.
2
Set status to Servicedupdate record
Sets the service status to Serviced immediately after the job is logged.
3
Route on jetting result
Branches the workflow depending on whether the line was cleared, partly cleared, or not cleared.
result: "Cleared"→Set status to Completed
result: "Partly cleared"→Set status to Further Work Needed
result: "Not cleared"→Set status to Further Work Needed
Default→Set status to Further Work Needed
4
Set status to Completedupdate record
Updates the record's service status to Completed for a fully cleared line.
5
Email customer work summarysend email
Emails the customer a summary of the jetting work carried out.
6
Wait 2 days before requesting feedback
Pauses for two days after the service email before asking the customer for feedback.
7
Request customer feedbackrequest external input
Sends the customer a short feedback form with a 1-5 rating and comments.
8
Set status to Further Work Neededupdate record
Updates the record's service status to Further Work Needed when the line was partly or not cleared.
9
Email customer on further work neededsend email
Emails the customer what was found during jetting and what further work is required.
10
Create office task to prepare quotecreate task
Creates a task for the office to prepare a quote for a CCTV inspection or repair, due in 2 days, without waiting for completion.

Fields

Drainer's Name*
Customer Name*
Customer Email*
Customer Mobile*
Site Address*
Job Reference*
+9 more fields

Forms

High-Pressure Jetting Service Record

14 fields

Data Views

Jetting Service Records

customer_name, site_address, lines_jetted, blockage_type +2 more

Dashboard Widgets

Services by Service Status

Recommended integrations

Setup the following integrations to extend workflow capability.

Send email in the workflow
AWS SES

high-pressure jetting service recorddrain cleaning and cctvtradetrades

Similar Workflows

drain defect root intrusion assessment drain maintenance program inspection cctv drain inspection report

Similar Categories

trades home services maintenance

FAQs

What does this workflow record for each jetting job?

Each job becomes a record with a reference number, a service status, and a timeline of what happened. The request form captures details such as drainer's name, customer contact information, site address, job reference, lines jetted, access points, nozzle type, jetting pressure, blockage type, CCTV check status, photos, and the result. Feedback ratings and comments submitted by the customer are also saved to the record, while notes entered on the office quoting task are kept with that task.

Who is involved at each stage of this workflow?

A drainer submits the initial service form from the field, which creates the record and sets its status to Serviced. Depending on the jetting result, the workflow either emails the customer a work summary and later requests feedback, or emails the customer about further work needed and assigns a task to an office team member to prepare a quote. Office and field users interacting with the workflow are workspace admins or members, with the quoting task assigned to a specific team member.

How does the workflow decide what happens after a job is logged?

After the record is created and marked Serviced, the workflow routes based on the Result field entered on the service form: Cleared, Partly cleared, or Not cleared. A fully cleared line moves the status to Completed and triggers a customer summary email followed by a feedback request two days later. A partly or not cleared line sets the status to Further Work Needed, sends the customer an email describing findings, and creates an office task to prepare a quote.

What happens when a line is only partly or not cleared?

The record's service status updates to Further Work Needed, and the customer receives an email outlining what was found during jetting and what further work is required. At the same time, an office task is created to prepare a quote for a CCTV inspection or repair, due in two days. This task is not one the workflow waits for, so the quote type and preparation notes entered on it stay with the task rather than on the record.

How is customer feedback collected and where does it appear?

For fully cleared jobs, the workflow waits two days after sending the work summary email before sending the customer a short feedback form asking for an overall satisfaction rating and any comments. Because the workflow waits for this form, the customer's responses are saved directly on the record. This gives office staff a record-level view of satisfaction alongside the job details.

How do we change this workflow to fit our own process?

A workflow can be adjusted by describing the desired change in plain English or by editing its steps directly in the workflow editor. This makes it possible to adjust the wait time before the feedback request, change the office task due date, or add fields to the initial service form. Earlier versions of the workflow are kept, so changes can be reviewed against the prior setup.

Can customers access this workflow without creating an account?

Yes, customers take part through forms emailed to them, such as the work summary notification, further work email, and feedback request, without needing to create an account. Field staff submit job details through the public request form. This keeps customer interaction simple while still capturing structured data on the record.

How quickly can this workflow be put into use across a workspace?

As a ready-to-use template, the workflow can be published by a workspace in minutes and run as a live process immediately, without an installation or development project. Office and field teams can begin submitting service forms and receiving tasks right away. Adjustments can be made afterwards as the team's process evolves.

What visibility does office staff have into job status across the business?

Table views and dashboards display jetting records by their current status, such as Serviced, Completed, or Further Work Needed, making it easier to see which jobs need attention. Workspace activity is logged, giving a record of actions taken across jobs. Each business should confirm how this level of tracking fits its own record-keeping obligations.

Ready to use this workflow?

Create a free account and customise this workflow for your business.