Trace one appointment from the homeowner's yes to the rep at the door, count every time it's typed, and make the step before do it. Plus the one check to keep.
Swipe or tap Next · checked on 2026-10-25
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 163. 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: "Type every appointment once: the handoff map for your office"
The guide is here: https://receiptsgroup.com/guides/type-every-appointment-once (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.This is how one appointment moves on our floor. Your tools can be different. The shape is what you copy: one typing, one check, and everything after that reads the same record.
The catch: QA is the only stop where a person looks at what was typed. If a wrong time gets past QA, every stop after it copies the wrong time perfectly. Typed once means checked once, so that check has to be good.
Any one that made it to the house. Write down its appointment number, not the homeowner's name: this sheet gets passed around, and names, phone numbers and addresses stay where they already live.
Start at the call and ask each person who touched it four things: where did it come from, what did you type, what did you only read, and where did it go next? Keep going past the appointment, too: how did the result (sat, sold, cancelled) get back to the office, and who typed it? Do it with them, not from memory. The doubles hide in the stuff people do without thinking, like the quick text to the rep.
One block per stop. Use job titles, not names, so it's about the process and not about anybody.
The handoff map · Part 1 of 2 · Copy copies all 29 lines
HANDOFF MAP: one appointment, from the yes to the door
Appointment #: ______ (the number only: no homeowner
name, phone number or address on this sheet)
Fill in one of these for every stop, starting at the
call and ending when the result (sat, sold, cancelled)
is back in the office:
STOP #: __
Who touches it (job title): ______________
Where (the dialer, the CRM, the calendar, a text,
a spreadsheet, paper): ______________
What they TYPE (day, date, time, address, name,
phone, product, notes): ______________
What they only READ: ______________The handoff map · Part 2 of 2 · Copy copies all 29 lines
How it gets to the next stop:
[ ] it moves by itself
[ ] someone types it again
[ ] someone copies and pastes it
[ ] someone asks somebody
THE COUNT
Times the day and time got typed: ___
Times the address got typed: ___
Times the name and phone got typed: ___
Times someone asked "did that one confirm?": ___
Where someone checks the booking against what the
homeowner said: ______________
(nowhere, or "the rep at the door"? that's fix #1)Anything typed at a stop that was already typed at an earlier stop. Copy and paste counts too, because it's still a person moving it by hand. And every time somebody asks “did that one confirm?”, write it down: that's a status that isn't riding along.
Where does somebody compare what got booked with what the homeowner actually said? If the answer is “nowhere” or “the rep, at the door”, that's your first fix, before you connect a single thing.
For every circled double, the stop before should be doing it for you. I'd go down this list in order and stop at the first one that works:
The question for your software's support · Part 1 of 2 · Copy copies all 17 lines
Hi, quick question about [the software's name].
When [this happens: a setter books an appointment in
____], can it automatically [do this: create the
opportunity / put it on the rep's calendar / text the
rep / add a row in ____] without anybody typing it
again?
1. Is that built in, or does it need an integration,
Zapier or a developer?
2. Which details come across: day and time, address,
name, phone, product, notes?
3. If someone changes the time later, does the change
come across too, or only the first booking?
4. Does it cost extra, and on which plan?The question for your software's support · Part 2 of 2 · Copy copies all 17 lines
Thanks!The other half of the map is all the “hey, did that one confirm?” stuff, which is a pain. That's a status that doesn't ride along. Put one status in one place that every department reads, and give each change to one job title.
One status, everyone reads it
ONE STATUS, EVERYONE READS IT
(one field, in one place: your CRM, not a group text)
WAITING ON QA set by: the booking itself
BACK TO SETTER set by: QA, with what's off
QA APPROVED set by: QA. Now a rep can drive.
SAT set by: the rep, from the house
SOLD / NOT SOLD set by: the rep
CANCELLED set by: whoever hears it first,
the same day
The rule: if somebody has to ask what's going on
with one, a status is missing. Find who should have
changed it, and make it their step.Connecting your tools doesn't make a wrong time right. It just makes it fast. So the check sits right after the one typing, before anything copies it. If your map has no check yet, do the next section first.
Paste your finished map into this prompt and it lists every double with the fix that fits. Before you paste: appointment numbers only, no homeowner names, phone numbers or 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).
Prompt: turn my map into a fix list · lines 1-1 of 13. Copy all copies the whole prompt; read it in full on the page.
Below is my handoff map for one appointment, from the homeowner's yes to the rep at the door. Each stop says who touches it, where, what they type, what they only read, and how it gets to the next stop.Good: every double from your map, each with one fix and a question for support where it needs one. Bad: it tells you a menu or a setting in your software. It can't see your software, so check that with its help pages or support before you click.
Type it once, check it once. When the copies happen by themselves, the check right after the booking is the only place a person still looks, so it has to be good, and it has to be somebody other than the setter. On our floor that's QA with the call recording attached.
The QA check card · Part 1 of 2 · Copy copies all 24 lines
QA CHECK: before anything moves
(done by someone other than the setter who booked it)
Open the booking and the booking call side by side.
1. DAY, DATE AND TIME
Does the booking match what the homeowner said
yes to on the call? Listen for the read-back.
2. ADDRESS
Same street and number as the call?
3. PRODUCT
What they asked about, so the right rep goes?
4. WHO'LL BE THERE
Everyone who decides, named on the call?The QA check card · Part 2 of 2 · Copy copies all 24 lines
All four match: QA APPROVED. Now it moves.
Anything off: BACK TO SETTER, with what's off.
The setter fixes the booking itself (never a side
text to the rep), and it comes back to QA.
No read-back on the call: BACK TO SETTER.
If the time was never said back and agreed to,
there's nothing to check it against.Want the four boxes in more detail, with the setter's lines? That's my four-box appointment check.
HighLevel's own help says that in many U.S. states, playing a recording disclaimer is legally required. In Florida, for example, the law (Florida Statutes 934.03) makes recording a call lawful when all of the parties to it have given prior consent.
Plain English, not legal advice: the rules depend on the state and on who's on the call, so ask your lawyer before you record. No recording? QA can call the homeowner back instead, and the four-box guide has that callback script.
Everything here is made up: a fictional roofing office, one appointment, before the fixes.
The count: the time 4 times, the address 4, the name 3, and a sales manager asking “did that one confirm?” every morning. The check: none.
After the fixes (still made up): the setter books it once, right on the customer's record in the CRM, on the call. QA checks it against the recording. QA's approval moves it to QA approved and sends the sales manager the alert. The board is the pipeline, so nobody keeps the spreadsheet, and the rep moves it to Sat from the driveway. The time is typed once, the address is typed once, and the morning question goes away because the stage answers it.
HighLevel (also called GoHighLevel) can do most of our floor's flow with call recording, one pipeline and two workflows.
One thing it can't do: its list of workflow actions has no action that makes a calendar appointment, so the calendar event gets made when the setter books, not when QA approves.
So in HighLevel the status is the pipeline stage, and the rule for reps is simple: go by the stage. Every click here is from HighLevel's own help pages, checked 2026-10-25.
It looks like the obvious switch. But HighLevel's help doesn't say what status an appointment starts in when your team books it by hand, so I wouldn't hang QA on it. A pipeline stage only moves when somebody moves it, and that's exactly what you want from a check.
Check Call Recording, and set Play Call Recording Message, like “This call will be recorded for quality purposes.” Do it on every number your setters call from. Recordings play back in Conversations: find the contact, and the playback controls sit on the call entry. A call from a setter's own cell never reaches HighLevel, so setters book from HighLevel's phone.
Name it Appointments and click Save. Type each stage name and click Add stage, in this order: Waiting on QA, Back to setter, QA approved, Sat. Add your sales stages after that if you track them here. Stage names have to be unique in a pipeline.
Name it “Booked: into QA.” This one turns the setter's booking into a card in Waiting on QA, so nobody types it into the pipeline.
Under Filter By Appointment Status, pick New (HighLevel: a new appointment is scheduled). Add the In Calendar filter for the calendar your sales appointments go on. If you add Modified By, make sure it includes User (your team booking by hand), or the setters' bookings slip right past it.
Pipeline: Appointments. Pipeline Stage: Waiting on QA. Leave Opportunity Name blank, and HighLevel names the card after the contact. Turn on Duplicate Opportunity: HighLevel's help says that with it off, a contact who already has an opportunity doesn't get a new one, so a repeat customer's booking would never show up for QA. The card is tied to the contact, so the name, the phone and the address come along without anybody typing them.
Turn it on, so a second booking or a reschedule makes a new card. HighLevel's help says a rescheduled appointment is treated as a new one, which is what you want here: a changed time goes back through QA. Click Save, and leave it in Draft until the first test.
Name it “QA approved: send it.” Add the filters In Pipeline: Appointments, and Pipeline Stage: QA approved. HighLevel's help says dragging a card by hand fires it, and so does a card moving back into that stage later.
Pick your sales manager, or whoever runs the reps' schedule (or the rep, if one rep owns that calendar). Paste the alert, and use the tag icon to drop in the contact's name instead of typing it. Each person needs a phone number set in HighLevel to get the text.
The QA approved alert
QA approved: {{contact.name}}.
The time is on the calendar and the address is on
the contact. Only drive on cards that say QA approved.Allow Re-entry, so a card that went back and got approved again sends again. Allow multiple Opportunities, so a customer with two cards gets an alert for each one (HighLevel's help: with it off, only the first opportunity that meets the trigger gets in). Save, and leave it in Draft until the test.
A third workflow, built like workflow 2 with Pipeline Stage: Back to setter, sending the setter a text, so a fix doesn't sit there all afternoon.
Before you trust it, plant a mistake and see if it gets caught. You play the homeowner with your own phone, so no customer is involved, and in HighLevel it costs a few cents.
Your own name and your own cell number. Never a customer.
Switch both from Draft to Publish. They only notify your team, but workflow 1 makes a card for every new appointment on that calendar from now on, real ones included. That's the point, just know it's on.
The setter calls your cell from HighLevel's phone. You say yes to Thursday at 4. The setter reads it back, you say yes again, and then the setter books it for Wednesday at 4. Only you and the setter know.
A card should show up in Waiting on QA. QA does the normal check. Good: QA hears Thursday on the call, sees Wednesday on the calendar, and drags it to Back to setter. Bad: it gets approved. That's not the software, that's the check, and it's the most useful thing this test can tell you.
The setter reschedules the appointment itself to Thursday at 4. A new card shows up in Waiting on QA. QA checks it and drags it to QA approved, and the alert should land on your sales manager's phone. Then set both test cards to Abandoned, so they don't count.
Not on HighLevel? Same test in your own tools: book a test appointment with the wrong time on purpose and see if your check catches it before the rep hears about it. If the wrong time reaches the rep, you just found where your check needs to go.
What it costs in HighLevel: a couple of minutes of calling your own cell (US calls are $0.0166 a minute, recording $0.0025 a minute) and one alert text (about 1.2 cents with the carrier fee). Call it a nickel.
Checked 2026-10-25 on gohighlevel.com/pricing, HighLevel's phone and text pricing pages, claude.com/pricing and zapier.com/pricing. Prices change, so check before you buy.
What one appointment costs to run through it in HighLevel, let's say the booking call runs 5 minutes: recording it is about 1.25 cents, storing it is a quarter cent a month, and the QA approved alert is one text at about 1.2 cents with the carrier fee. The call minutes you'd pay anyway. Zapier counts a task each time it finishes a step for you, so one booking moving from one tool to another is one task.
QA approved it without hearing the time on the call. No read-back, no approval, and QA listens to the part where the time gets said, not just the summary.
Somebody fixed a copy (a text, the board) instead of the booking. Fix the booking itself, and it goes back through QA. Then find out why there's still a copy on the map.
Workflow 1 isn't published, the In Calendar filter points at the wrong calendar, Modified By leaves out User, or Duplicate Opportunity is off and the customer already had an opportunity.
That's a reschedule: HighLevel treats it as a new appointment, so workflow 1 makes a new card. Check the new one, and set the old one to Abandoned.
In HighLevel the calendar event shows up when the setter books, before QA. The rule is the stage: only drive on QA approved. Say it out loud at the next sales meeting.
Workflow 2 isn't published, its Pipeline Stage filter isn't QA approved, or the person has no phone number set in HighLevel (the text fails for that person). Still nothing? Ask HighLevel's support to check your texting setup, including your business texting registration (A2P 10DLC).
Recording is set per number: turn it on for every number the setters call from. A call from a setter's own cell never reaches HighLevel, so there's nothing to play.
A status isn't getting changed. Look at the status list and find the step nobody owns, then give it to one job title.
Ask the software's support whether it has an API or webhooks a developer can use. Until then, keep the copy as a known double with a read-back against the source.
That's question 3 in the support message. If changes don't come across, every reschedule is retyping again: put it on the map and get an answer before you count it as fixed.
It can't see your software and may be guessing. Check its help pages or support before you click.
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.
Map it, make the step before do every double for you, and keep the one check right after the booking, because now your mistakes travel as fast as your appointments do.
If you'd rather have the whole floor built this way, dialer to CRM to calendar with QA on every appointment, that's our call center buildout.
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).