Service Visit Follow-Up & Workmanship-Warranty Log

The problem this kills

A technician finishes a job, marks it complete, and moves on. Then three weeks later the customer calls back about the same problem. Was that work still under your workmanship warranty? Is this free rework or chargeable new work? Nobody's sure, because the warranty terms live in a quote PDF, the job history lives in a dispatch tool, and the callback just landed as a voicemail.

So warranty obligations slip. Repeat issues don't get connected to the original visit. Satisfaction checks never go out, so you find out a customer is unhappy when they post a review instead of when you could have fixed it. And when a callback does come in, deciding "free or charge?" turns into a judgment call with no record behind it.

This tool closes that gap. Every completed visit gets a warranty clock started on it, a satisfaction check goes out automatically, and any callback that arrives while the work is still under warranty gets flagged and linked back to the original job - so a supervisor decides, on the record, whether it's in-warranty rework or new chargeable work.

What you'll build

A small, private web app for your service team:

• A place to bring in completed jobs (from a CSV or Google Sheet, or pasted in) with work type, completion date, and the warranty terms for that kind of work.
• Automatic calculation of the workmanship-warranty end date for each job, based on the warranty rules you define for each work type.
• An automatic satisfaction check emailed to the customer a few days after the visit, via Resend.
• A callback intake screen: when a customer reports a repeat issue, the tool links it to the original job and tells you instantly whether it's still in-warranty.
• A supervisor approval gate: no follow-up visit is scheduled and no warranty claim is accepted until the supervisor reviews it and approves - the AI drafts the recommendation, a human commits it.
• A clean warranty & follow-up register you can export as CSV in the exact columns your existing system expects.

What's inside the Implementation Plan

The plan is a step-by-step runbook you paste into Claude Code (an AI coding assistant). It builds the whole tool with you, one prompt at a time - you don't write code.

It opens by interviewing you about your business - your work types and their warranty periods, how jobs and callbacks are named and numbered, your typical and peak job volumes, and your exact rule for when a callback is free rework versus chargeable. It reads a short tailored spec back to you and waits for your thumbs-up, so the tool fits your service operation instead of a generic template.

From there it walks through: setting up the database with row-level security, importing your completed jobs, calculating warranty periods from your rules, sending satisfaction checks, building the callback-linking screen, wiring the supervisor approval gate, and exporting the register.

The governance it includes (this is the point)

This isn't a toy. The plan builds in the controls a real service operation needs:

• Login so only your team can open the tool.
• Row-level security so each organization only ever sees its own jobs and callbacks.
• A complete audit trail - who logged a job, who flagged a callback, who approved a follow-up, and exactly when.
• A hard human-in-the-loop approval gate - the AI drafts the "in-warranty rework vs. new chargeable work" call, but a supervisor reviews and approves before any follow-up visit is scheduled or any warranty claim is accepted.
• Duplicate guards keyed on the job ID, so the same completed job can't be logged or processed twice.

Who it's for

Field-service supervisors and coordinators who manage post-visit quality and warranty - in HVAC, plumbing, electrical, appliance repair, facilities, install/repair trades, and similar. If you own the "did we follow up, and is this still under warranty?" question, this is for you. No coding background needed.

You've got this - paste the first prompt and let the agent interview you.