A name and a time on your calendar isn't an appointment. Not yet. On our floor, an appointment counts when it passes four boxes: we're talking to the homeowner, everyone who makes the decision will be at the table, the product's right, and we read the time back and they said yes. Then QA, a second person on the floor, calls the homeowner back and asks all four again. Miss one, and it doesn't go on the calendar.
That's the check behind our best month so far: our outbound floor sold about $800,000 in September 2026, and every appointment it set had to pass these four boxes first. I'm not going to tell you the check did that by itself. A floor is a lot of things. But it's the part you can copy this week, for free.
So here's all of it: the four boxes and what counts for each one, the lines your setters say at the end of the call, the QA callback script, the rule for what happens when a box misses, a log to keep it honest, and a first test you can run before you change anything. There's also a prompt that has Claude or ChatGPT walk you through it, and one that reads your log for you.
Start here: paste this into ChatGPT or Claude
Not technical? Start here. Copy this prompt into ChatGPT or Claude (the free versions work) and it walks you through the whole guide, one step at a time, in plain English. It asks before it assumes anything and checks with you before anything that costs money, reaches a real customer or deletes something. The rest of the page is the same guide, written out, if you'd rather do it yourself.
Hi! Please be my patient guide for this step-by-step guide from Receipts Group: "The 4-box check every appointment passes before it counts"
The guide is here: https://receiptsgroup.com/guides/four-box-appointment-check (open it if you can; if you can't, everything you need is below).
About me: I run a small business and I'm not technical. Use plain words and short sentences.
My goal: every appointment my setters book passes four checks before it goes on the calendar. 1, we're talking to the homeowner. 2, everyone who makes the decision will be at the table. 3, the product's right, so we send the right rep. 4, we read the time back and they said yes. Then someone else (QA) calls the homeowner back and asks all four again. Miss one, and it doesn't go on the calendar.
How to help me:
1. One step at a time. For each step, tell me in a sentence what it's for and exactly what to do (what to write, who to ask, what to say). Then stop and wait until I say "done" or tell you what I see.
2. Ask before you assume anything about my business, my trade, my team, my calendar or my numbers. One question at a time.
3. If you use a technical or sales word, explain it in plain English the first time (for example: setter, QA, decision maker, sit, CRM).
4. Stop and check with me before anything that costs money (signing up for a tool or a paid plan), anything that reaches a real customer (the first real QA callback, any text or call to a homeowner), and anything that deletes something (removing appointments from my calendar, clearing a sheet).
5. Use only what I tell you or show you. Never make up numbers, names or results. If something's missing, ask me.
6. If I paste anything, remind me first to take out homeowners' names, phone numbers and addresses.
7. You're not my lawyer. If I want to autodial, use a recorded voice or send automated texts for these callbacks, tell me to have my lawyer check the consent rules first.
The steps, from the guide:
Step 1. Write the four boxes for my trade.
Ask me what I sell and help me fill in: what counts as the homeowner (the person who owns the house, not a tenant or a relative who answered), who usually decides in my customers' homes, the list of products and which rep sells each one, and how we read the time back.
Step 2. Give my setters the four boxes for the end of every call.
Fill in the setter script below with my products and company name. Show it to me and wait for my yes. The setter books nothing on the calendar: it goes on a QA list as PENDING.
Step 3. Pick who does QA.
Someone other than the setter who booked it: an office manager, another setter, or me. Ask me who, and when in the day they'll make the callbacks.
Step 4. Give QA the callback script.
Fill in the QA script below. Help me decide two rules and write them down: how many times QA tries a homeowner who doesn't answer, and by when, before the appointment comes off the list.
Step 5. Set the rule: miss one, it doesn't go on the calendar.
Any box missed goes back to the setter with the box named. The setter fixes it (for example, a new time when both decision makers can be there), and QA calls again. Help me write this rule in one paragraph I can send my team.
Step 6. Start the log.
Help me make the QA log below as a sheet (Google Sheets or Excel) or as fields in my CRM, whichever I already use. Ask me which.
Step 7. First test, before I change anything.
Before the new rule starts, QA calls the homeowners on my next 10 appointments (or the ones already on the calendar for the next few days) and asks the four boxes. Wait for my yes before anyone calls a real homeowner. We fill in the log and count how many pass all four.
Step 8. Every week, read the log.
Count which box misses most, overall and by setter, and coach that one. Box 2 (everyone who decides) is the one that gets skipped most on our floor.
The setter script (fill in the brackets with me):
---
THE FOUR BOXES: the end of every booking call
1. THE HOMEOWNER
"And you own the home, right?"
Yes: box ticked.
A tenant, a relative, "I'd have to ask": get the
homeowner's name and best number. Book nothing yet.
2. EVERYONE WHO DECIDES
"Is anyone else part of a decision like this? A
spouse, a partner, a parent?"
Yes: "Great, let's pick a time you can both be
there. What works for both of you?"
Write down every decision maker's first name.
3. THE RIGHT PRODUCT
"Just so I send the right person: you're looking
at [windows / doors / a roof / ...], for [which
part of the house]?"
Book the rep who sells that.
4. THE TIME, READ BACK
"Okay, I have you down for [day], [date], at
[time], at [street]. You and [name] will both be
there. Does that work?"
Wait for a clear yes. "I think so" is not a yes.
Then: "Someone from our team will call you back
in a bit to confirm everything. Is this the best
number?"
Nothing goes on the calendar yet. It goes on the
QA list as PENDING.
---
The QA callback script (fill in the brackets with me):
---
QA CALLBACK: before it goes on the calendar
(done by someone other than the setter who booked it)
"Hi, is this [first name]? This is [your name] with
[company]. You just set up a time with [setter's
first name] for us to come out about your [product].
I'm confirming a few details so we send the right
person. Got a minute?"
1. "And you own the home on [street]?"
2. "Who else is part of the decision? Will [names]
be there?"
3. "And this is about [product], right?"
4. "We have you down for [day], [date], at [time].
Still good?"
All four yes: APPROVED. Now it goes on the calendar.
"Perfect, you're all set. We'll see you [day] at
[time]."
Any no, or a maybe: BACK TO SETTER, with the box
that missed. Nothing goes on the calendar.
No answer: NOT CONFIRMED. Nothing goes on the
calendar. Try again at the time you set as your
rule.
---
The QA log:
---
QA LOG: one row per appointment
(appointment numbers only: no homeowner names,
phone numbers or addresses)
Appt # | Booked (date, time) | Setter | QA by
Box 1 homeowner Y / N
Box 2 everyone who decides Y / N
Box 3 right product Y / N
Box 4 time confirmed Y / N
Result: APPROVED / BACK TO SETTER / NOT CONFIRMED
Box that missed: ____
Fixed and approved later? Y / N
What happened: SAT / CANCELLED / NO ONE HOME
---
Watch out for these:
- The setter doing their own QA. It has to be someone else, or it's just the same call twice.
- "My husband will probably be there." Probably isn't yes. Book a time they can both make.
- Booking the window rep for a door job, or the other way around. Box 3 is there for that.
- "I think so" on the time. Read it back again and wait for a clear yes.
- Putting it on the calendar "just for now" while QA is pending. That's how a name and a time turns into an appointment by accident.
- Fewer appointments on the board. That's expected, and that's the point.
- A clean appointment can still cancel. The check catches the ones that were missing something, not every cancellation.
- Pasting customer details into an AI. Take out names, numbers and addresses first.
When we're done, give me a short recap: my four boxes, who does QA and when, my no-answer rule, and what the first test showed.
Start by asking me a few quick questions about my business, one at a time. Then begin with step 1.The four boxes
- You're talking to the homeowner. Not the tenant, not the nephew who picked up the phone. The person who owns the house.
- Everyone who makes the decision will be at the table. The spouse, the partner, the parent, whoever decides. This is the one that gets skipped, like, constantly.
- The product's right. They want windows, you send a window rep.
- You said the time back, and they said yes. The day, the date, the time, out loud, and a clear yes.
Then QA calls the homeowner back and asks all four again. Miss one, and it doesn't go on the calendar, period, end of story.
- 1The booking callYour setter, with the four boxes at the end→ a PENDING appointment, not on the calendar yet
- 2The QA callbackSomeone other than the setter, with the QA script→ four yes answers, or the box that missed
- 3ApprovedQA puts it on the calendar→ an appointment your rep can drive to
- 4Back to the setterThe setter fixes the box that missed→ a new call, then QA again
- 5The logA sheet or your CRM, one row per appointment→ which box misses most, every week
Anything that misses a box goes back to the setter, gets fixed, and comes back through QA. It only reaches the calendar through step 3.
| Box | Counts | Doesn't count |
|---|---|---|
| 1. The homeowner | The person who owns the house says yes, they own it | A tenant, a relative who answered, "I'd have to ask" |
| 2. Everyone who decides | Every decision maker named, and a time they can all make | "My wife will probably be there", "I'll fill him in" |
| 3. The right product | What they want, in their words, and a rep who sells it | "They want a quote" with no product named |
| 4. The time, read back | Day, date and time read back, and a clear yes | "I think so", "sometime Tuesday", "call me that morning" |
Words you'll see
- Setter: the person on the phone who books the appointment.
- QA: quality assurance. Here it's a second person on the floor who calls the homeowner back and asks the four boxes again.
- Decision maker: anyone who has a say in buying. Usually a spouse or partner, sometimes a parent or a co-owner of the house.
- Sit: an appointment where the rep actually sits down with the homeowners.
- CRM: the software where you keep your customers and appointments.
Set it up, step by step
Write the four boxes for your trade
Ten minutes with a notepad. Write down every product you sell and which rep sells it (box 3). Then who usually decides in your customers' homes (box 2). Boxes 1 and 4 are the same in every trade.
Give your setters the four boxes for the end of every call
Fill in the brackets and hand it to every setter. The big change: the setter books nothing on the calendar. It goes on a QA list as pending. Use whatever you already have for that: a tab in your sheet, a pipeline stage in your CRM, a column on a whiteboard.
THE FOUR BOXES: the end of every booking call 1. THE HOMEOWNER "And you own the home, right?" Yes: box ticked. A tenant, a relative, "I'd have to ask": get the homeowner's name and best number. Book nothing yet. 2. EVERYONE WHO DECIDES "Is anyone else part of a decision like this? A spouse, a partner, a parent?" Yes: "Great, let's pick a time you can both be there. What works for both of you?" Write down every decision maker's first name. 3. THE RIGHT PRODUCT "Just so I send the right person: you're looking at [windows / doors / a roof / ...], for [which part of the house]?" Book the rep who sells that. 4. THE TIME, READ BACK "Okay, I have you down for [day], [date], at [time], at [street]. You and [name] will both be there. Does that work?" Wait for a clear yes. "I think so" is not a yes. Then: "Someone from our team will call you back in a bit to confirm everything. Is this the best number?" Nothing goes on the calendar yet. It goes on the QA list as PENDING.Pick who does QA
Someone other than the setter who booked it. An office manager, another setter, or you. If the setter checks their own appointment, it's just the same call twice. Pick when in the day the callbacks happen, too, so pending appointments don't sit there.
Give QA the callback script
Short and friendly: it's a confirmation, not an interrogation. Then write two rules down: how many times QA tries a homeowner who doesn't answer, and by when, before the appointment comes off the list. Your trade and your schedule decide those, not me.
QA CALLBACK: before it goes on the calendar (done by someone other than the setter who booked it) "Hi, is this [first name]? This is [your name] with [company]. You just set up a time with [setter's first name] for us to come out about your [product]. I'm confirming a few details so we send the right person. Got a minute?" 1. "And you own the home on [street]?" 2. "Who else is part of the decision? Will [names] be there?" 3. "And this is about [product], right?" 4. "We have you down for [day], [date], at [time]. Still good?" All four yes: APPROVED. Now it goes on the calendar. "Perfect, you're all set. We'll see you [day] at [time]." Any no, or a maybe: BACK TO SETTER, with the box that missed. Nothing goes on the calendar. No answer: NOT CONFIRMED. Nothing goes on the calendar. Try again at the time you set as your rule.Set the rule: miss one, it doesn't go on the calendar
Any box missed goes back to the setter with the box named. The setter calls back and fixes it, like a new time when both decision makers can be there, or the right rep for a door job. Then QA checks again. No exceptions for a "pretty sure" one, because that's exactly the one your rep drives forty minutes for.
Start the log
One row per appointment, in a sheet or as fields in your CRM. Appointment numbers only: keep homeowners' names, phone numbers and addresses where they already live, not in a log people pass around.
QA LOG: one row per appointment (appointment numbers only: no homeowner names, phone numbers or addresses) Appt # | Booked (date, time) | Setter | QA by Box 1 homeowner Y / N Box 2 everyone who decides Y / N Box 3 right product Y / N Box 4 time confirmed Y / N Result: APPROVED / BACK TO SETTER / NOT CONFIRMED Box that missed: ____ Fixed and approved later? Y / N What happened: SAT / CANCELLED / NO ONE HOMEEvery week, read the log
Count which box misses most, overall and by setter, and coach that one box. It's about the process, not about catching anybody. On our floor, box two is the one that gets skipped most.
Example (made up)
Everything here is made up: a fictional window and door company, one afternoon of bookings, five appointments.
| Appt | What QA heard | Result |
|---|---|---|
| #101 | Owns the home, both of them will be there, windows, time confirmed | Approved, on the calendar |
| #102 | Owns the home, but her husband decides and works that day | Back to setter: box 2. New time on Saturday with both, QA again, approved |
| #103 | Rents the house: the landlord would decide | Back to setter: box 1. Setter asks for the landlord's number. Not on the calendar |
| #104 | Wants a new front door, booked with a window rep | Back to setter: box 3. Door rep instead, QA again, approved |
| #105 | No answer on the callback, twice | Not confirmed. Not on the calendar |
Two of the three that made the calendar only got there because QA caught a box. Without the callback, #102 is a rep sitting with one spouse who can't say yes, and #104 is a window rep standing at a door. That's the whole check: no surprises when the rep shows up.
First test: check the appointments you already have (free)
Before you change anything, find out where you are. Have whoever will do QA call the homeowners on your next 10 appointments, or the ones already on the calendar for the next few days, and ask the four boxes with the QA script. Fill in a log row for each one. It costs nothing but the calls.
Good: you can tick all four boxes on most of them from what the homeowner actually said. What you'll probably find: a box that keeps missing. Fix that one first, then start the rule.
After a week of logs, paste them into this prompt and it does the counting. Before you paste: take out homeowners' names, phone numbers and addresses. In Claude you can also choose whether your chats help improve its models: Settings → Privacy → Help Improve our AI models (or go straight to claude.ai/settings/data-privacy-controls).
Below is my appointment QA log for [this week]. Each row is one appointment the setters booked, with four boxes: 1 homeowner, 2 everyone who decides at the table, 3 the right product, 4 the time confirmed. Then the result (APPROVED, BACK TO SETTER or NOT CONFIRMED), the box that missed, and what happened at the appointment.
Please:
1. Count how many were booked, how many were approved the first time, how many were approved after the setter fixed them, and how many never made the calendar.
2. Count which box missed most often, overall and by setter.
3. Of the approved ones, count how many sat, cancelled or had no one home.
4. Show it as two small tables, then three lines in plain words: which box to coach on first, and one line I can say to my setters about it.
Rules: count only what's in the log. Never guess a number or fill in a blank; if a row is missing something, list it under "Incomplete rows". Plain words, short sentences.
My log:
[paste it here, appointment numbers only: no homeowner names, phone numbers or addresses]Good: two small tables whose counts match your log, and one box to coach first. Bad: a number you can't find in the log. Count that one by hand, and tell it: "Count only what's in the log."
What it costs
| What | Plan | Price |
|---|---|---|
| The four boxes, the scripts and the log | None | $0 |
| The QA callbacks | Your own team | One short call per appointment |
| Claude (the prompts) | Free | $0 |
| Claude, if you want more use | Pro | $20 a month billed monthly, or $17 a month billed yearly ($200 up front) |
| ChatGPT | See OpenAI's pricing page | Not checked: OpenAI's pricing pages didn't load for us on 2026-10-18 |
When it breaks
Setters skip box two
"My husband will probably be there"
The setter does their own QA
Appointments go on the calendar "just for now" while QA is pending
QA can't reach the homeowner
Homeowners are annoyed by the second call
Fewer appointments on the board
A clean appointment still cancels
The product changes at the house
The AI counts something that isn't in the log
ChatGPT or Claude can't open the guide link
Four boxes, then the calendar
The homeowner, everyone who decides, the right product, and the time, confirmed, then asked again by someone else. A calendar can't tell a real appointment from a name and a time, so somebody on your floor has to.
It's the same QA every appointment gets on the call floors we build.
Checked on Oct 18, 2026 against
Every claim about a third-party tool in this guide (plans, prices, menu paths, commands, limits) was checked against these official pages on Oct 18, 2026. These screens change often: if something looks different, trust the page over this guide.
- Claude: Plans and pricingFree at $0; Pro at $20 a month billed monthly, or $17 a month billed yearly ($200 up front) (checked 2026-10-18).
- Claude Privacy Center: How do I change my model improvement privacy settings?Settings → Privacy → Help Improve our AI models (or claude.ai/settings/data-privacy-controls), for Claude Free, Pro and Max (checked 2026-10-18).
- 47 CFR 64.1200 (Cornell LII)(a)(2) and (a)(3): marketing calls with an autodialer or a prerecorded or artificial voice need prior express written consent; (f)(9): what that consent is (checked 2026-10-18).
