PR-2283 · Live
Closeout Craft
When a technician marks a job complete, the customer is notified without the CSR needing to do a thing. Closeout Craft puts together a plain summary of the visit covering the work completed, any readings and photos taken, and a short note from the technician. The summary then goes to the customer by text or email. A work receipt is included when the shop wants one. The CSR gets a notification confirmation right on the job. When the field service system is connected, Closeout Craft reads the finished job and writes the delivery back on its own. When it is not connected, the technician fills a short closeout form and the summary goes out the same way.
The promise
The customer already knows what happened on the visit before they think to pick up the phone. The CSR's day runs on booking jobs and addressing the calls that need real attention. They no longer field the steady stream of "did the tech come?" and "what did they do?". Every recap is logged on the job, so they can confirm at a glance.
How it works
The path from input to value.
- 01
A job wraps up
When the technician marks the job complete, Closeout Craft picks it up. With the field service system connected it reads the job; without it, the technician submits the details and photos on a short form.
- 02
The recap comes together
It builds a plain-language summary of the work and any readings, gathers the photos and the technician's note, and adds a work receipt if the shop uses one.
- 03
It goes to the customer
The recap is sent by text or email, the way the shop set it up, with no step from the office.
- 04
It is logged on the job
The delivery is recorded back on the job, so the office can see what went out and when.
The day before. The day after.
Same moments. Lived differently.
The first calls of the day include three 'did your tech come yesterday?' checks. For each one the CSR opens the job, reads back what was done, and relays it while the queue stacks up behind them.
8:00 AMThe jobs closed yesterday already went out as recaps. The first calls of the day are bookings, not status checks.
8:00 AMBefore
The first calls of the day include three 'did your tech come yesterday?' checks. For each one the CSR opens the job, reads back what was done, and relays it while the queue stacks up behind them.
After
The jobs closed yesterday already went out as recaps. The first calls of the day are bookings, not status checks.
A customer who was at work during the visit calls to ask what the tech found. The CSR digs through the job notes and a couple of photos to piece the visit back together.
11:30 AMThe customer who was at work got the summary with photos the moment the job closed. No call comes in.
11:30 AMBefore
A customer who was at work during the visit calls to ask what the tech found. The CSR digs through the job notes and a couple of photos to piece the visit back together.
After
The customer who was at work got the summary with photos the moment the job closed. No call comes in.
A member wants a copy of what was done for their records. The CSR builds a quick summary by hand and emails it over.
2:00 PMThe record the member wanted was sent at closeout, receipt included. There is nothing to compile.
2:00 PMBefore
A member wants a copy of what was done for their records. The CSR builds a quick summary by hand and emails it over.
After
The record the member wanted was sent at closeout, receipt included. There is nothing to compile.
What it doesn’t do
The edges we drew on purpose.
A product that tries to do everything ends up doing nothing well. Here’s what we left out, and why we don’t feel bad about it.
- ×Generating the invoice or collecting payment
- ×Handling the customer's reply or questions after the recap goes out
- ×Arrival or ETA notifications before the visit
- ×Writing the technician's work record; the recap summarizes what the tech captured