A repair promise doesn't count as done until the customer says so
Install and repair businesses often promise a fix, an adjustment, or a warranty replacement on a call, then mark it resolved internally once a technician says the work is done, without ever hearing back from the customer that it actually solved the problem. To the business the file looks closed. To the customer, nothing happened and nobody followed up. This page shows one small, working tool that closes that gap: every promised fix gets a visible target date, and a claim cannot move to Resolved in the office view, only the customer's own confirmation can do that.
Everything below is fictional. When this gets built for a real business, it reads from whatever already logs a service call (a CRM, a shared spreadsheet, a phone intake form) and connects the target-date and confirmation prompts to the business's existing email or text system.
Open claims
Check your claim status
Try SMP-1001, SMP-1002, SMP-1003 or SMP-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 work-order or claim number instead of inventing a new one to remember.
The target date is set the moment a fix is promised. A real build can text or email the customer that same target date automatically, instead of it living only in a call note.
The office view genuinely cannot close a claim on its own. Once repair work is marked complete, the claim sits blocked until the customer confirms it from their own status page, mirroring the actual promise made on the call, not just a status label staff can flip.
"Confirmed" 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.