Four boxes every appointment passes before it hits the calendar, plus the QA callback that asks them again. Setter script, QA script and log to copy.
Swipe or tap Next · checked on 2026-10-18
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.
The walkthrough prompt (copy all of it) · lines 1-4 of 139. Copy all copies the whole prompt; read it in full on the page.
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.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.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.
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.
If you can't tick it with what the homeowner actually said, it isn't ticked.
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.
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 setter's four boxes · lines 1-14 of 33. Copy all copies the whole file; read it in full on the page.
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.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.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.
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.
The QA callback script · Part 1 of 2 · Copy copies all 26 lines
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?"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 callback script · Part 2 of 2 · Copy copies all 26 lines
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.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.
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.
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 HOMEQA 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 HOMECount 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.
Fewer appointments hit the board, and honestly, that's good. The ones that didn't make it were missing something, and your rep finds that out at a locked gate forty minutes from the office, which is a really fun drive, let me tell you.
Everything here is a person calling by hand. If you want to automate it, the federal rule (47 CFR 64.1200) requires "prior express written consent" for marketing calls to cell phones made with an autodialer or a prerecorded or artificial voice, and for prerecorded marketing calls to home phones. Plain English, not legal advice: states add their own rules and texting has its own questions, so have your lawyer look before you automate any of it.
Everything here is made up: a fictional window and door company, one afternoon of bookings, five appointments.
Five booked, three on the calendar. Made-up numbers, just to show how the rows read.
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.
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).
The weekly log prompt · lines 1-1 of 12. Copy all copies the whole prompt; read it in full on the page.
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.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."
Checked 2026-10-18 on claude.com/pricing. Prices change, so check before you buy.
It's the awkward question, so it gets skipped. Give them the exact line ("Is anyone else part of a decision like this?") and look at box 2 first in the weekly log.
Probably isn't yes. Book a time they can both make, and have QA ask by name: "Will [name] be there?"
Then it's the same call twice. QA has to be someone else, even if that's you at the end of the day.
That's how a name and a time becomes an appointment by accident. Pending lives on the QA list. Only QA puts it on the calendar.
Not confirmed means not on the calendar. Use the no-answer rule you wrote in step 4, and tell the homeowner on the first call that someone will call back, so they pick up.
Keep it to a minute, say it's so you send the right person, and have the setter mention it at the end of the booking call.
That's expected, and that's the point. Watch what happens to the ones that pass, in the last line of the log.
Life happens to everybody. The check catches the ones that were missing something, not every cancellation. Log it and move on.
Have QA ask, "Anything else you wanted us to look at?" and book the rep who sells what they said.
Count that row by hand, then tell it: "Count only what's in the log. If a row is missing something, list it as incomplete."
That's fine. Everything it needs is in the walkthrough prompt. Tell it to keep going without the link.
What each page backs up is listed at the end of the full guide.
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.
Want help setting this up? Receipts Group builds these systems.
Open the full guide as a page (every file in full, plus the table of contents).