Definition
A booking-system check is the pass you run on one test contact before a form, a booking page, or a follow-up email reaches a real customer. The October 10, 2026 video shows eleven breaks on our own build, including a confirmation that went out twice.
Eleven things broke when we tested our own booking system, including a confirmation that went out twice, and the video shows each break on screen before a customer was on the list. Run the five checks below on one test contact before your form, your booking page, or your follow-up email touches a real address.
The October 10, 2026 video is "11 Things That Broke While I Built a Booking System (Real Screens)." It is narrated with an AI clone of Ángel Castro's voice, and he approves every script. The screens are from our own build, with personal data blurred, and any screen marked example was recreated with test data. We had a form, a booking page, a pipeline, and follow-up email inside the CRM. The chapters group the eleven breaks into before go-live, how a lead gets in, one job per automation, what the customer sees, and the double confirmation.
What should you check before a booking email goes to a customer?
Check five things, in this order: a stop at the top of every automation, a gate that allows one test contact, a fallback on every merge field, a time zone saved when the contact arrives, and the booking status read again before any confirmation sends.
The video lists those five as this week's changes. It also says eleven things broke, each one shown with a fix, and the chapter titles group them. The description does not name the other ten in prose, so this note does not invent those names.
| Check | Pass looks like | Fail looks like |
|---|---|---|
| Stop check first | An empty required field ends the automation before any email | A later step still sends because the stop sat underneath it |
| One test contact | Only an address you control receives mail | A real customer is in the pipeline while you are still editing |
| Merge-field fallback | A blank first name still reads as a sentence | The email opens with a hole where the name should be |
| Time zone on the way in | The confirmation shows the customer's zone | "Tuesday at 8" means a different hour than the customer heard |
| Status before send | A visit already confirmed does not get a second "you're booked" | The same person receives the booked note twice |
How do you keep a half-built automation from emailing a customer?
Put one stop at the top of every automation, and make the stop mean "this contact is not cleared." A stop that lives under the send step fires too late to help.
That stop is the video's first weekly change. The build it names has a form, a booking page, a pipeline, and follow-up email. This note puts the stop on each of those, because the video says the check goes at the top of every automation.
Then gate the whole set to one test contact until the mail is right. Use an address you open yourself, run the form as a homeowner asking for a tune-up, and leave every real customer off the list. The video opens on a confirmation that sent "You're booked" twice. This note treats a second row, or a second email, on that test contact as the sign to stop and look.
What has to be true in the email the customer reads?
Every merge field needs a fallback. Clear the first name on the test contact and send again. When the sentence collapses, write a fallback or drop the name and keep the sentence whole. The video's third change is that fallback. A customer reading the email on a phone at night will not fill in the blank for you.
Save the time zone when the contact first comes in, and print that zone in the confirmation. The video's fourth change is storing the zone on the way in. This note's example is a shop that books 8 a.m. in the office zone and arrives an hour off in the next state.
Open the test email on a phone and check the date, the arrival window, the address, and who is coming. If a price is in the note, it has to match the quote a person already approved. The video has a chapter called "What customers actually see," covering items 7, 8, and 9, and it does not name those items in the description. Judge the pass from the test contact's phone.
How do you stop a second confirmation?
Read the booking status before any confirmation goes out, and skip the send when the visit is already confirmed or already cancelled. The video's fifth change is that status check. A chapter titled "The double confirmation" covers items 10 and 11, after the chapter on what the customer sees.
Cause the second send on purpose with the test contact. Submit once, let the confirmation arrive, then trigger the same automation again the way a refreshed form or a second click would. The status check passes when the second run sends nothing. It fails when another "you're booked" lands. Leave the gate on the test contact until that second run is quiet.
Give the automation one job. The video has a chapter by that name, items 5 and 6, and it does not spell the jobs out in the description. This note keeps one automation on the confirmation, and a different one for the next step after a person says the job is done.
Who watches the first week of real bookings?
A person in the office watches the first week, with the test gate opened only after the five checks pass on the test contact.
Keep the stop check in place after go-live. It is how a blank form fails closed.
The note on appointment booking covers how an agent prepares a visit. This one is the test you run before that mail is allowed to leave. When you want the five checks walked through on the tools you already use, get your free Systems Plan and bring one real confirmation you were about to send.
Questions and answers.
What broke while the booking system was being built?
Eleven things broke on our own build before a customer was on the list. The October 10, 2026 video opens on a confirmation that sent "You're booked" twice. The chapter titles group the rest, and the description does not name those ten breaks.
Which checks should pass before a confirmation reaches a customer?
Five, in this order: a stop at the top of every automation, a gate that allows one test contact, a fallback on every merge field, a time zone saved when the contact arrives, and the booking status read again before any confirmation sends.
Are the screens in the booking video a customer's account?
No. The video says the screens are from our own build, with personal data blurred, and that screens marked example were recreated with test data. The narration is an AI clone of Ángel Castro's voice, and he approves every script.
Sources.
Topics covered
Related resources
Industry paths