Template, not built for a specific business

A warranty claim doesn't count as handled until the customer can see it move

Businesses that promise a warranty on installed or treated work often log a customer's follow-up call as a note on a job file and nothing else. To the office it looks handled. To the customer, there is no ticket, no target response time, and no way to check whether anyone is actually coming back, so a claim that is quietly stalled looks identical to one that is being worked. And if a crew finds something beyond the original warranty scope once they are back on site, the added charge can get billed before the customer ever agreed to it. This page shows one small, working tool that closes both gaps: every completed job carries a visible warranty window, filing a claim against it opens a status ticket with a stated response-time commitment, and any extra charge beyond the original scope is itemized and held until the customer explicitly acknowledges it, before it is ever billed.

Everything below is fictional. When this gets built for a real business, it reads completed-job and warranty-period data from whatever already tracks it (a CRM, a shared spreadsheet, a scheduling tool) and adds the claim ticket, response-time commitment, and charge-authorization gate on top of that, without replacing the underlying system.

Completed jobs & claims

Check your warranty or claim

Try REF-1001, REF-1002, REF-1003 or REF-1004 from the office view's sample queue.

How this gets built for real

The reference number is whatever the business already gives a customer. A real build reads from an existing job or invoice number instead of inventing a new one to remember.
The warranty window is set the moment a job is marked complete. A real build can text or email that window to the customer automatically, instead of it living only in a filing cabinet.
The response-time commitment is a real clock, not a promise. A claim that sits at "Claim received" past its stated response window shows as overdue in the office view, instead of going quiet.
An itemized charge genuinely cannot be billed without customer acknowledgment. Staff can add a charge beyond the original warranty scope, but it sits held until the customer checks a box and types their name from their own status page.
"Acknowledged" here is a typed name and a timestamp. A real build can add an actual e-signature provider for a stronger record; this demo shows the workflow, not a specific vendor.
See it built for a real business: Bee Safe Bee Removal.