Turn a driveway voice memo into a customer recap

You finish a job. The customer is not in the driveway, or they are, and both of you will forget half of it by tomorrow. A one-minute voice memo, turned into a short recap, gives you a record you can send and a record you can read on the next visit.

The bot writes the draft. You send it. Those are different jobs. The first text a caller ever gets is covered in the missed-call text-back. This page starts after the work is done.

The memo you record

Stand where you can name what you see. Sixty seconds is enough. Cover only these, in this order:

1. Customer first name, and a job label you will recognize later. An address or your own job number is enough.
2. What you did.
3. What you did not do, especially if they asked and you declined or deferred.
4. What you want them to watch, in plain language.
5. What happens next, including “nothing” if nothing happens next.

Speak the gaps out loud. “I did not open the wall.” “I did not give a price for the other room.” If you do not say it, the draft must not add it. The memo is the only source.

The instruction you give the tool

Paste this above the transcript, every time:

Use only the memo. If a section was not in the memo, write "Not stated" under that heading.
Do not add parts, prices, time promises, causes, or code language.
Do not upgrade "I tightened the fitting" into "I repaired the system."
Do not suggest extra work.

Then ask for this shape and nothing more creative:

Subject: Today's visit — [job label]

[First name], here is a short record of today's visit.

Did:
- …

Did not:
- …

Please watch:
- …

Next:
- …

This note is a record of the visit. It is not a warranty and it is not an invoice.

“Not stated” is a successful line. It means the tool stayed inside the memo.

Your edit is the product

Read the draft against the memo once. Out loud is better if the driveway is quiet enough. You are looking for inventions.

• Delete any sentence that was not in the memo.
• Remove vague upgrades the tool added, such as “thoroughly,” “fully,” or “permanently.”
• If a price belongs in the conversation, it goes on your invoice, which you write. It does not go in a sentence the tool composed.
• If you are unsure, cut the sentence. A short true recap beats a complete-sounding one.

Then you send it, from you, in the channel that customer already uses with you. The bot does not get its own relationship with them.

File it where the next visit starts

Save the memo and the sent recap in the same place as the job. A folder of texts to yourself counts if that is the system you already open. On the next visit, read the “Did not” lines before you unload. The point of the draft is that those lines exist when you are in a hurry, not that the prose sounds polished.

A dry run before a real customer

Record a memo about a job you already finished and already explained in person. Run the draft. Compare it to what you know you did. Count the inventions. If the count is above zero, tighten the instruction, especially the “Not stated” rule, and run it again.

Do not send the first draft of a new workflow to a customer on the day you invent the workflow.

What this setup is for

It describes the visit you already did. It is not a quote bot, not an invoice bot, and not a way to sound larger than the shop. If the tool offers to identify extra work or to “sound more premium,” turn that off. The after-hours sheet is the same idea applied to questions: one source, no inventions, a person still owns the send.