Customer No-Show Field Note: Minimum Facts Before an AI Follow-up
A missed appointment is easy for a model to turn into a verdict. The technician texts "nobody home," and the office asks for a follow-up. The draft says the customer breached the window, a trip fee now applies, and the crew can return Thursday morning if the customer confirms. It may also say the company never heard from anyone, even when a text is already sitting on the job. None of those sentences require a careless writer. They require a gap. The office asked for a follow-up, and the note never said which facts were real. The difference between a careful no-show message and a confident fiction is the field note written before the model drafts.
This guide is that note: the facts to collect, or mark UNKNOWN, before any AI drafts a customer follow-up after a crew arrived and did not find the customer, or after the customer missed the appointment the office had on the board. It is not a phone call the office failed to answer. If the problem is an unanswered ring, use the missed-call handling guide instead of describing a phone event as a visit. It is not the appointment reminder guide, which is about messages sent before a visit to confirm a window that is still live. It is not a weather stop. If the crew could not work because of conditions at the site, use the weather delay field note, and do not tuck a no-show into a weather paragraph to soften it. It is not an after-hours emergency callback. The callback note is about what dispatch needs before sending someone out. This page starts after a scheduled visit has already been attempted.
Why the note has to exist before the follow-up
No-show language creates money and schedule risk when it is casual. "We'll charge the trip" feels like policy in the truck and becomes a fee the owner has not approved. "You missed us, so Thursday is the next opening" feels helpful and becomes a new arrival promise. "We never heard from you" feels like a clean story and may contradict a message the customer already sent. A model is good at smoothing those impulses into a paragraph. It is not on the porch, and it is not in the owner's pricing conversation.
Read the job pointer and the window already given to the customer before anyone prompts a model. Classify the follow-up in office language: internal note only, customer follow-up that the attempt happened and no new window exists, or customer follow-up that includes a window the approver has already set. If the owner has not chosen, the honest draft is an internal summary, not a customer email.
Treat the AI as a writer working from the field note, not as a dispatcher, a contract reader, or a person who decided a fee. It can arrange sentences the office already decided. It cannot decide that eight minutes on site "usually" becomes a trip charge, that a late text cancels the visit, or that the customer will accept a Saturday. Those decisions stay with named people.
A follow-up also sits next to private details the model does not need. Gate codes, alarm words, card numbers, and portal logins are not what makes the note clear. The NIST small-business privacy page, retrieved 2026-11-15, says a small business owner may want to protect customers' privacy and points to the NIST Privacy Framework's Learning Center as a place to start. The page was updated on the NIST site on 2 September 2025. The NIST cybersecurity basics page, also retrieved 2026-11-15 and updated on the NIST site on 6 November 2026, says cybersecurity is a continuous process and lists everyday steps that include knowing which assets matter, training people, and keeping sensitive accounts behind strong authentication and unique passphrases. A customer follow-up draft is one of those everyday assets. The prompt should carry the job label, the window, and what was observed, not the secrets that protect the property or the business.
The minimum facts to collect first
Before prompt time, fill each field or write UNKNOWN and the name of the person who can resolve it:
- Job or appointment pointer — job, work-order, or appointment ID, and the customer or property label the office already uses. A street nickname is not a pointer. Do not add a new phone number or email that is not already on the job file.
- Follow-up purpose — internal note only; customer follow-up that the attempt happened and no new date exists; customer follow-up with an approved new window; or not yet decided. A second purpose, such as a change in scope or a fee decision, is a different note unless the approver has already written that position on this one.
- Scheduled window — the arrival or work window already told to the customer, and where that promise lives: confirmation text, proposal, or dispatch board. If none was made, write NONE. Do not reconstruct a window from memory so the email has something to point at.
- Who went — the person who attempted the visit, whether they were on site, and the times they recorded for arrival and departure. A remembered comment from someone who was not there is not an observation.
- What was observed — what they saw or did, in their words: knocked, no answer, lights off, a note on the door, a locked gate, or a person who was not the customer. Do not upgrade that into "refused access," "abandoned the appointment," or a contract breach the observer did not state.
- Time on site, as arithmetic from the times they wrote — departure minus arrival, in minutes, but only when both times are on the note and departure is not earlier than arrival. If either time is missing, the duration is UNKNOWN. Do not invent a wait policy. If the confirmation states a wait, quote that sentence and who is willing to repeat it. Otherwise a "required wait" is UNKNOWN and stays out of the draft.
- Where the attempt sat inside the window — minutes from the window start to arrival, and minutes from departure to the window end, when the window and the times are all known. If the crew left while the window was still open, the draft must not say the window had expired. If the crew arrived after the window ended, say that only if the times show it.
- Customer message already received — quote the message that is already on the job file, with its time, or write NONE. Do not summarize a late text into "they cancelled" unless the words say cancel. Do not write "we never heard from you" when a message exists. If the office has not checked the thread, the message field is UNKNOWN and the draft waits.
- Who has read that message — the technician before the attempt, the technician after leaving, the office only, or UNKNOWN. A message the crew had not seen is still a message the follow-up has to live with.
- Work that could have proceeded — one line in the technician's words, or UNKNOWN. Do not claim the job was ready, the part was on the truck, or the visit would have finished if the customer had been home, unless the person who was there said so.
- New window — only a date and window the approver has set. Otherwise UNKNOWN. "Next available," "tomorrow," and "Thursday" are not windows.
- Price and contract position — no money language on this send; a fee or waiver the approver has written in a sentence the draft may repeat; or UNKNOWN. Do not invent a trip charge, a waived fee, or a statement that the visit was free. Elapsed minutes are not a price. This note is not legal, tax, or contract advice.
- Office position — the send/no-send choice: internal note, customer follow-up without a new date, or customer follow-up with the approved window. If position is blank, do not prompt a customer message.
- Do-not-promise list — the sentences that must not appear: a specific return day, a fee, a breach or blame line, a claim that nobody made contact, a "required wait" the file does not contain, or the original window restated as if the crew were still coming.
- Approval owner — who must approve customer language, any date the customer will hear, and any money sentence.
- Channel and timing — how the follow-up will be sent, to which contact already on file, and when a reply is reasonably expected. Do not harvest a new address from an old thread "for context."
- Photo pointer — if a door, gate, or note photo exists, point to it by job and time. Do not paste it into the prompt. What a photo is allowed to support belongs on the jobsite photo field note.
- PII and secret check — confirm the prompt excludes payment card data, government IDs, gate or alarm codes, full account numbers, and portal or mailbox passwords.
Office position is the field that keeps a missed visit from becoming a new appointment or an invoice. If the owner has not decided whether this send is an internal note or a customer follow-up, the model will decide by sounding firm. Firm, in this setting, usually means a fee or a date. Write the position before the prompt exists.
Observer words beat atmosphere. "Knocked twice, no answer, left at 13:20" can be checked against the person who was there. "Customer no-show in breach of the service agreement" cannot. The second sentence imports a contract and a conclusion the note never earned.
An illustrative example
The clock is the part a model will round into a story, so the note keeps the subtraction visible. The window is three hours, which is 180 minutes. Morgan arrived 12 minutes after the window opened. `13:12` is not an equation the sheet needs a formula for: the 12 is 13:12 minus 13:00. Time on site is `8` minutes because departure minus arrival is 8, and 13:20 is after 13:12. From departure to the end of the window is 2 hours and 40 minutes, which is 160 minutes. The check is `12 + 8 + 160 = 180`. Twelve minutes after the window opened, plus eight minutes on site, plus the 160 minutes still left, exhaust the 180-minute window and do not run past it. The crew left while the customer's window was still open. A draft that says the appointment window had already expired contradicts the times.
The message clock is a second subtraction. From 12:40 to 13:00 is 20 minutes, and from 13:00 to 13:12 is 12 minutes, so the text existed `20 + 12 = 32` minutes before Morgan knocked. It also existed before the window started. The words are "running late, please start if you can." They do not say cancel, and they do not name a new arrival time. Morgan did not see them until after 13:20. The follow-up can say, in substance, that the office has the 12:40 message, that the technician did not see it before leaving, and that the crew did not start the work. It cannot say the customer never wrote, and it cannot say the crew began the repair because the text said "please start." Starting was not observed.
A draft that stays inside this note can say: we were scheduled for Tuesday 2026-11-17 between 13:00 and 16:00 on job 7740; our technician arrived at 13:12, knocked, got no answer, and left at 13:20; we have your 12:40 message that you were running late and asked us to start if we could; we did not start the work; we do not have a new arrival window yet; the office will send one after it is set. It cannot say the crew will be back Thursday, that a trip fee applies, that the customer breached an agreement, that a required wait was completed, or that nobody made contact.
Once Elise keeps the "no new date" and "no money language" positions, and Morgan confirms the door sentence is complete, the field note is stable enough to prompt. If Elise later sets a window, that is an edit to the new-window field and a second approval, not a silent improvement by the model. If Elise later writes a fee sentence, that sentence has to land on the price field before it can land in the email. The eight minutes do not generate it.
Two records that are not ready to prompt
The first bad record changes only the departure time. Arrival stays 13:12 and someone writes departure as 13:05. Departure is earlier than arrival by 7 minutes. Duration is not −7, and it is not "about ten minutes" to keep the story moving. The times contradict each other. The note is not ready. Fix the clock with the person who was there, or mark both times UNKNOWN and do not let the model pick a duration that makes the paragraph sound precise.
The second bad record is a different message, not a different visit. Suppose the job file instead held a 11:00 text that said "please cancel today." That sentence is a cancellation already received, 2 hours before the 13:00 window start. A no-show follow-up that ignores it and scolds a missed knock is the wrong document. The purpose field changes: the office is answering a cancel, or it is confirming that the crew stood down, and only the approver can say which. The original example's "running late" text is not that cancel. Quoting the words is what keeps the two jobs apart. Paraphrase is where they collapse.
A third trap does not even need a new fact. Leave the message field UNKNOWN because nobody checked the thread, and then draft anyway. The model will often fill the silence with "we did not receive a message." UNKNOWN is not NONE. NONE means someone looked and the file has no customer message. UNKNOWN means the draft waits.
A short sequence before anyone prompts the model
- Name the job and the follow-up purpose — one sentence: "Job 7740, customer follow-up, attempt recorded, no new date." If purpose is not yet decided, stop.
- Read the window and the two times — scheduled start and end, arrival, departure. If departure is before arrival, stop. If a time is missing, duration is UNKNOWN.
- Do the subtractions in the note — minutes after the window opened, minutes on site, minutes left in the window. The draft does not get a fresher clock than these.
- Quote any customer message already on file — words and time, or NONE after a real check. Record who had read it before the crew left.
- Check the lookalikes — an unanswered phone call is the missed-call guide. A reminder for a window that has not happened yet is the appointment-reminder guide. Weather, a missing part, or an after-hours callback is a different note. Do not rename those causes as a no-show.
- Set price position and the do-not-promise list — no money language, a written position, or UNKNOWN. Blank means the model will invent a fee or a courtesy waiver.
- Prompt with the field note only — no dispatch-board screenshots, no photo files, no full proposal if it contains payment data, no extra threads "for tone."
- Review by role — the person who went checks the observed words and the times; the approver checks dates and money; the sender checks the address and that secrets stayed out.
- Save the packet — field note, window pointer, message quote, draft, edits, and the sent message, stored with the job file.
The sequence is short because most bad no-show emails are position failures, not writing failures. A firm paragraph drafted from an unresolved fee or an unresolved next window will still name a charge or a day. Fix the note, then draft.
Prompt rules that keep the model inside the note
When the note is complete enough to draft, give the model rules as strict as the facts:
- Use only the field note. If a fact is UNKNOWN, say the office is checking it or that no new window is set. Do not fill the gap from a typical missed appointment.
- Do not invent return dates, trip fees, waived fees, required wait times, breach language, or a claim that the work could have been finished.
- Do not say the company never heard from the customer if a message is quoted, and do not say the customer cancelled unless the quoted words cancel.
- Do not say the window had expired, or that the crew were still inside it, unless the note's own subtraction says so.
- If price position is "no money language," do not add a P.S. about cost, goodwill, or a trip charge.
- If office position is internal note only, draft an internal summary, not a customer email.
- Do not assign fault beyond what the observer and the message field actually say.
- Do not describe parts as backordered, weather as the cause, or the visit as a warranty finding unless this note's purpose says that and the matching field note is the one being used.
- Keep one purpose, one named office contact, and one reply path. After the draft, list every sentence that depends on a date, a duration, or a money claim a human must match to the note.
That last list is the review. The approver should be able to point at each date, each duration, and each money sentence and find it on the field note. Sentences with no field behind them come out before the message is sent.
Common failure patterns
The first failure is the invented return. The model sees a missed afternoon and offers Thursday, "tomorrow morning," or "the next opening." Unless the new-window field contains that day and the approver's name, the sentence goes. A hopeful dispatcher is not an approved window.
The second failure is the invented fee. A trip charge, a waived trip, or a promise that the attempt was free may be the right business decision later. It is not a sentence the model may add because the email felt unfinished. If the price field says no money language, the draft has no dollar signs and no fee words at all. Minutes on site are a duration. They are not a rate.
The third failure is the missing message. "We never heard from you" is false in the example, where the 12:40 text was on the file 32 minutes before the knock. It is also false whenever the message field is UNKNOWN, because the office has not looked. NONE is the only value that supports a no-contact sentence, and even then the approver has to want that sentence. The do-not-promise list in the example bans it outright.
The fourth failure is the required wait. Offices reach for "we waited the standard fifteen minutes" because it sounds more official than "left at 13:20." Official is not the goal. The confirmation in the example states no wait. Eight minutes is what the two clock times support. A fifteen-minute policy that is not on the note is an invention, even if some other job's script uses fifteen.
The fifth failure is saying the window expired. The subtraction `12 + 8 + 160 = 180` is there so a reviewer can see the crew left with 160 minutes still on the window. An email that scolds a missed day, when the knock happened 12 minutes after the window opened and the crew left inside that same window, rewrites the appointment the customer was given.
The sixth failure is treating "please start if you can" as permission that was used. The observed line says Morgan did not enter. The work-that-could-have-proceeded field is UNKNOWN. A draft that thanks the customer for letting the crew begin is a different visit from the one on the note.
The seventh failure is prompt oversharing. Pasting a dispatch board, a door photo, or the customer thread can drag other jobs, gate codes, and card notes into a chat log. Point to a photo if one exists. Follow the photo field note before any description of what the picture shows. Leave passwords and payment data out. The cybersecurity basics page treats training and care around sensitive accounts as ordinary business hygiene, not as a special project. The person who pastes the prompt is part of that hygiene.
The eighth failure is using a no-show note to close a different job. A missed knock is not a passed inspection, a finished warranty diagnosis, a weather delay, or a material backorder. If the part was the real reason the crew could not work, use the material delay field note. If the sky was the reason, use the weather note. If the visit was a warranty call and the finding matters, use the warranty service visit field note. This note only carries the missed attempt. Mixing them produces an email that sounds complete and answers the wrong question.
Finally, keep the record. Save the field note, the pointer to the original confirmation, the quoted message, the do-not-promise list, the draft, the approver's edits, and the sent message. The next person who gets a reply asking "so when are you coming, and are you charging me" should not have to reconstruct the porch from a text thread and a memory of an empty driveway.
How this note connects to related field guides
Use this sheet when the immediate task is a customer or internal follow-up after a scheduled visit was attempted and the customer was not available, or after the office is answering a message about that attempt. Use the missed-call guide when the immediate task is a phone call nobody picked up. A job can have both problems. It should not have one paragraph that pretends a ring and a porch are the same event. Messages that go out before the visit, asking the customer to confirm a window, belong to the appointment reminder guide. Do not reuse a reminder template for an attempt that has already happened. The reminder assumes the window is still ahead. This note exists because the attempt is behind.
Board moves and the question of which jobs shift are the dispatch workflow guide. This page does not tell the office how to rebuild the day. It tells the writer which facts are allowed into one customer's follow-up. An after-hours emergency that has not been dispatched yet stays on the callback note. Do not borrow callback urgency to make a missed 13:00 window sound like a different kind of job.
Pictures of the door, the gate, or a note stay on the jobsite photo field note until someone decides what the image is allowed to prove. A follow-up that describes "the attached photo shows no one home" is a documentation claim. Make that claim on the photo note, or do not make it. Weather, materials, and warranty findings stay on their own notes, linked by job pointer. Do not merge their conclusions into the no-show draft to save a second email unless the approver explicitly made that the purpose.
The habit across these notes is the same. Collect the minimum facts, mark UNKNOWN, name the approver, then draft. A no-show text feels smaller than a change order. It still sets a date or a fee, or it refuses to, and the customer will treat that sentence as the plan.
A copyable one-page template
Keep the filled sheet with the job file beside the confirmation that named the original window. A one-line post-send note is enough when the follow-up was clean: who approved it, and that no new date and no fee were included. When it was not clean, the note should say which field was still UNKNOWN, not which technician "sounded unsure."
If the office writes no-show follow-ups often enough to be tired of the sheet, the cure is a standing do-not-promise list — no unnamed return day, no fee language, no required-wait theater, no "we never heard from you" unless the file says NONE — pasted once into the job folder. The template above still needs the observer's words, the two clock times, the quoted message, and the approver's position for this visit. The standing list only stops the same inventions from coming back.
Assumptions and limits
All examples are hypothetical. Contract language about missed appointments, trip fees, cancellation notice, and consumer messages varies by agreement and by jurisdiction. This page does not interpret a contract, does not give legal or tax advice, and does not offer industry-average costs, wait times, or durations. No dollar amount appears because a sample price would only look like guidance. The office's own price position, including a decision to say nothing about price, has to be written by the approver. The eight minutes, twelve minutes, and one hundred sixty minutes in the example are subtractions from stated clock times. They are not a recommended wait and not a billing increment.
NIST pages cited below were requested on 2026-11-15 and loaded. The privacy page, updated on the NIST site 2 September 2025, says a small business owner may want to protect customers' privacy and points to Privacy Framework resources as a starting place. The cybersecurity basics page, updated on the NIST site 6 November 2026, describes cybersecurity as a continuous process and lists starter steps such as inventorying important assets, training employees, and protecting sensitive accounts. They are starting points for privacy and everyday security hygiene. They are not a quote of the full frameworks, not a certification, and not a rule that forbids or endorses any particular AI product. Identification of a NIST page is not a claim that NIST reviewed this article.
No visit was observed and no customer message was sent for this article. The worked example uses invented people, an invented company, and a synthetic job so the fields can be read without a real file. If a later company policy is stricter than this note, the policy wins for that office.
Sources and method
- NIST: Small Business Cybersecurity Corner — Privacy — retrieved 2026-11-15
- NIST: Small Business Cybersecurity Corner — Cybersecurity Basics — retrieved 2026-11-15
AI-assisted writing with automated source, calculation and editorial checks. No hands-on testing or professional certification is claimed. Check the stated assumptions before applying this guide.