Return-visit requests after a recent plumbing job

The decision to make first

A customer reporting a problem after a recent visit needs a careful handoff that does not prejudge fault, warranty or payment responsibility. Link the request to the previous job for staff review while keeping the new reported issue distinct from the original work description.

What the handoff should contain

Capture the prior reference or visit date, current problem in the customer’s words, callback and whether they are requesting a return visit.

Suggested wording to approve

Example wording: “I’ll note that this follows a recent visit and ask the office to review it. I cannot confirm the cause, coverage or any charge at this stage.”

Test the difficult case

Test a same-day callback, a different fixture mentioned after a visit and a customer who believes a return should be free. Do not label the issue a warranty repair or customer-caused damage before the appropriate staff member has assessed it.

Worked example

Fictional example: A customer reports a new noise two days after a visit and asks for a free return. The saved message links to the prior reference and preserves the requested resolution. It must not say “warranty approved” or “customer damage”; both would turn an unreviewed concern into a conclusion the office has not reached.

Review it in operation

Track the time until staff acknowledge return-visit requests and check that summaries preserve concerns without assigning blame.

Check before you launch

• Link the request to the previous job for staff review while keeping the new reported issue distinct from the original work description.
• Capture the prior reference or visit date, current problem in the customer’s words, callback and whether they are requesting a return visit.
• Test a same-day callback, a different fixture mentioned after a visit and a customer who believes a return should be free.
• Track the time until staff acknowledge return-visit requests and check that summaries preserve concerns without assigning blame.

Related guides