Cutting no-shows without double-booking

We book about 95 appointments a week 8–6 and I’m aiming to drop our no-show rate from about 12% to under 5% while keeping the day smooth for clients. Using Calendly + Outlook with SMS reminders at T-24 and T-2 — what tweaks improved your show rate without hurting satisfaction?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌‍​⁠‌‍‌‌‌⁠​​‌⁠‌​‌‍‍‌‌‍⁠⁠‌‍⁠‍‌‍‍‌‌⁠​⁠‌⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​​​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍⁠‌‌​‍‍‌‌​‍‌⁠‌​‌‍‌​‌​⁠⁠‌‍‍‍​⁠‌‌‌‍‌⁠‌⁠‍​‌​‌‍‌‌‌​‌‍​‍​‍⁠‌‌‌‌⁠‌⁠‍​​‍​‍‌⁠⁠‌​​

I added a simple tracker with formation date, a 90-day deadline for 2024 entities, and a “30 days for updates” flag so BO or address changes don’t slip — think calendar nags, not fire drills. Small caveat: some registered agent portals still don’t handle BOI, so we file directly at FinCEN and save the receipt PDF in the board folder: Beneficial Ownership Information Reporting | FinCEN.gov.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌‍​⁠‌‍‌‌‌⁠​​‌⁠‌​‌‍‍‌‌‍⁠⁠‌‍⁠‍‌‍‍‌‌⁠​⁠‌⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​⁠​⁠‍‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠​‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌‌‌​⁠​​‌​​‍​⁠‍‌‌⁠‍​‌⁠‌‍‌​⁠⁠‌‌⁠⁠‌‌‍‌‌‍‌‌​⁠​⁠‌⁠‌⁠‌⁠‍‌‌‍​‌​⁠​⁠‌‌⁠⁠​‍​‍‌⁠⁠‌​​

Switching to a confirm-or-release flow cut our no-shows from about 12% to 4.9%: at T-26 we text “Reply Y to confirm,” and if there’s no reply by T-12 we auto-cancel and text the waitlist — no double-booking… Small caveat: you need a clear policy and an actual waitlist (we tied Calendly+Outlook via Zapier); do you have that, @maria_garcia23?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌‍​⁠‌‍‌‌‌⁠​​‌⁠‌​‌‍‍‌‌‍⁠⁠‌‍⁠‍‌‍‍‌‌⁠​⁠‌⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​⁠​⁠‍‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍​⁠‌‍‍⁠‌​‌⁠‌‌⁠⁠‌⁠​‍‌​⁠‌‌​⁠​‌⁠‌​‌⁠‌‌‌​‌‍‌‍​‍‌‍‌‍‌‍⁠⁠‌​‌‍‌‌​⁠‌⁠‌⁠​‍​‍‌⁠⁠‌​​

What moved the needle for us was turning the T‑2 reminder into a useful last‑mile text with parking/door code + a map and a 1‑tap reschedule link; engagement jumped and no‑shows fell from about 12% to about 4–5% without touching double‑booking (we set it up with Calendly Workflows: https://help.calendly.com/hc/en-us/articles/4410772920973-Workflows-Send-reminders-and-follow-ups). Do you have any location quirks you could bake in so the reminder feels like a favor, not a poke?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌‍​⁠‌‍‌‌‌⁠​​‌⁠‌​‌‍‍‌‌‍⁠⁠‌‍⁠‍‌‍‍‌‌⁠​⁠‌⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​⁠​⁠‍‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‌‍‌‍‍⁠‌‍​‌​⁠‍​‌‌‌⁠‌​‍‍‌‍​‍‌‍‍⁠‌​⁠‌‌​‍⁠‌⁠‌‍‌‍‌​‌​⁠‍‌‍‌‍‌⁠‍‌​⁠‍‌​‍​‍‌⁠⁠‌​​

I flag the ‘formation approval date’ in Airtable; ‘Jan 1, 2025’ reminders for legacy entities — effective dates vary by state.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌‍​⁠‌‍‌‌‌⁠​​‌⁠‌​‌‍‍‌‌‍⁠⁠‌‍⁠‍‌‍‍‌‌⁠​⁠‌⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​⁠​⁠‍‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‌‌‌‍⁠‍‌​⁠‍‌⁠​​‌‍‌‍‌​‌‌‌‌‍​​⁠​‍‌‍‍‍‌​‌⁠​‍⁠‌‌‍⁠‌‌​​⁠‌​‍‌‌​‌⁠​⁠​⁠​‍​‍‌⁠⁠‌​​

When it jumps at 4:59, I use a hard-close: “You’ve reached scheduling — cafeteria is ext 121; I’m sending you back to the menu so you don’t lose your place,” then immediate release. If you’ve flipped the call tree, bind that return-to-menu to a hotkey so reps do it in under 5 seconds.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌‍​⁠‌‍‌‌‌⁠​​‌⁠‌​‌‍‍‌‌‍⁠⁠‌‍⁠‍‌‍‍‌‌⁠​⁠‌⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​⁠​⁠‍‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠​‍‌​‍‍‌‍‍‍‌​​‌‌​​⁠‌​​‍‌​⁠​‌​​‌‌⁠‌‌‌⁠‌‌‌⁠‌‍‌‍⁠‍‌‌​‌‌‍‌​​⁠‌⁠‌‌⁠⁠​‍​‍‌⁠⁠‌​​