[{"data":1,"prerenderedAt":289},["ShallowReactive",2],{"blog-post-\u002Fblog\u002Fholiday-waitlist-priority-not-first-come":3},{"id":4,"title":5,"body":6,"description":275,"extension":276,"howToSteps":277,"itemList":277,"meta":278,"navigation":279,"path":280,"publishedAt":281,"readMinutes":282,"seo":283,"stem":284,"tags":285,"updatedAt":277,"__hash__":288},"blog\u002Fblog\u002Fholiday-waitlist-priority-not-first-come.md","The holiday waitlist: priority, not first-come",{"type":7,"value":8,"toc":264},"minimark",[9,13,20,27,34,39,47,50,76,79,83,94,97,120,127,140,144,150,168,174,178,190,194,201,214,218,232,236],[10,11,12],"p",{},"It's December 21st. A client cancels a Saturday 11am color slot — a $200 appointment, in the most valuable week of your year. You have a waitlist. So you push the opening out, and within a minute someone's grabbed it.",[10,14,15,16],{},"Here's the question nobody asks: ",[17,18,19],"em",{},"did the right person grab it?",[10,21,22,23,26],{},"Because on a plain shared waitlist, the slot went to whoever happened to be looking at their phone that minute. That might be a new client you've met once. It might be someone who books cheap services. Meanwhile your six-year regular — the one who'd have taken that Saturday in a heartbeat, tips well, rebooks every time — was mid-haircut with ",[17,24,25],{},"her own"," client and never saw the notification. The slot's gone. To the fastest thumb, not the best fit.",[10,28,29,30,33],{},"In a slow season, that's fine; a filled slot is a filled slot. In peak season, when that chair is the most valuable it'll be all year, \"somebody filled it\" and \"the ",[17,31,32],{},"right"," somebody filled it\" are very different outcomes.",[35,36,38],"h2",{"id":37},"how-a-shared-waitlist-actually-works","How a shared waitlist actually works",[10,40,41,42,46],{},"A shared waitlist is first-come-first-served with extra steps. When a slot opens, the tool notifies everyone on the list — or lets everyone see the opening — and the first person to tap it wins. The mechanism rewards exactly one thing: ",[43,44,45],"strong",{},"speed of response."," Not loyalty, not ticket size, not how much you'd like that specific person in that specific chair. Just who was fastest.",[10,48,49],{},"That produces a few predictable problems in a busy week:",[51,52,53,64,70],"ul",{},[54,55,56,59,60,63],"li",{},[43,57,58],{},"It rewards availability, not value."," The people fastest to tap are the ones sitting idle with notifications on. Your best regulars are often the ",[17,61,62],{},"busiest"," people, least able to respond in the sixty seconds that decide it.",[54,65,66,69],{},[43,67,68],{},"It's a scramble, not a choice."," You don't get to say \"I'd love Maria in that slot.\" You broadcast, and you take whoever's quickest.",[54,71,72,75],{},[43,73,74],{},"It can feel like a lottery to clients."," Everyone gets pinged, most lose the race, and the ones who keep losing stop bothering to respond at all.",[10,77,78],{},"None of that means a shared waitlist is useless. It's better than an empty chair. But it's optimizing for the wrong thing in the exact week you can least afford it.",[35,80,82],{"id":81},"the-priority-approach","The priority approach",[10,84,85,86,89,90,93],{},"The alternative is to stop broadcasting and start going ",[17,87,88],{},"in order",". When a slot opens, you contact your regulars ",[43,91,92],{},"one at a time, in the order you'd actually want them",", and each person gets a short, real hold — a window where the slot is theirs before the offer moves on.",[10,95,96],{},"The mechanism, step by step:",[98,99,102],"blog-aside",{"label":100,"type":101},"How a priority blast works","note",[103,104,105,108,114,117],"ol",{},[54,106,107],{},"A slot opens. You (or the tool) have a ranked list of who you'd want in it — your top regulars first.",[54,109,110,111],{},"The first person on the list gets a text: ",[17,112,113],{},"this slot just opened, it's yours if you want it, you've got a few minutes to grab it.",[54,115,116],{},"If they say yes, it's theirs. Done. Nobody else was ever bothered.",[54,118,119],{},"If they don't respond within the hold, the offer rolls automatically to the next person — and the next — until someone takes it.",[10,121,122,123,126],{},"The difference is the ",[17,124,125],{},"hold",". On a shared list, everyone's notified and it's a race. In a priority blast, one person at a time gets a genuine, private window to claim the slot before it moves on. Your six-year regular mid-haircut doesn't lose the slot because she was slow — she gets her turn, and if she truly can't, it rolls to the next-best fit, not to whoever's fastest.",[10,128,129,130,135,136,139],{},"That's the mechanism ChairCal is built around — ",[131,132,134],"a",{"href":133},"\u002Ffeatures\u002Ffill","priority-blast auto-fill",", texting your top regulars one at a time with a real hold on each. I'm describing what it ",[17,137,138],{},"does",", not promising a result: I'm not going to tell you it fills X% of slots or recovers Y dollars, because we don't publish outcome numbers and I'm not about to invent one for a blog post. What I'll stand behind is the mechanism — priority-and-hold instead of broadcast-and-race — because that's a real, describable difference, and in a high-value holiday slot it's the difference you care about.",[35,141,143],{"id":142},"an-illustrative-walk-through","An illustrative walk-through",[10,145,146,147],{},"Made-up scenario to show the two mechanisms side by side — ",[43,148,149],{},"these are invented details, not measured results:",[98,151,153,156,162],{"label":152,"type":101},"Illustrative — invented example, not data",[10,154,155],{},"A Saturday color slot opens at 9:40am for an 11am appointment. On your waitlist: Maria (regular, six years, high ticket), Jenna (regular, two years), and Alex (new client, booked once).",[10,157,158,161],{},[43,159,160],{},"Shared waitlist:"," all three get pinged at 9:40. Alex is scrolling and taps first at 9:41. Slot's his. Maria, foiling a client, sees the text at 10:15 — too late.",[10,163,164,167],{},[43,165,166],{},"Priority blast:"," Maria gets the offer first at 9:40 with a short hold. She's busy, doesn't answer within the window, so at ~9:48 it rolls to Jenna. Jenna grabs it. Maria was never in a race she couldn't win; she got first refusal and simply passed, and the slot still landed with a two-year regular instead of a one-time client.",[10,169,170,171,173],{},"Same opening, same three people, different rule — and the priority version put the slot with someone closer to who you'd have chosen, without you having to babysit the phone. That's the whole idea: not \"fill it faster\" (a shared list can be plenty fast) but \"fill it ",[17,172,32],{},".\"",[35,175,177],{"id":176},"where-this-fits-with-process-time","Where this fits with Process Time",[10,179,180,181,184,185,189],{},"There's a second peak-season lever worth naming, because it's the other half of how you get more out of a full December: ",[43,182,183],{},"Process Time."," When a color's developing, that's 30–45 minutes where you're not actively working but the chair-hour is ticking. Booking a second client into that window — a cut, a blowout — is how a fully-booked day quietly becomes a more-than-fully-booked day. We cover it in ",[131,186,188],{"href":187},"\u002Fblog\u002Fwhat-a-saturday-with-process-time-looks-like","What a Saturday with Process Time looks like","; the point here is just that priority-fill and Process Time are the two things that make peak weeks pay, and neither is a first-come waitlist.",[35,191,193],{"id":192},"the-honest-bottom-line","The honest bottom line",[10,195,196,197,200],{},"A shared waitlist beats an empty chair. If that's what your current tool gives you, use it. But understand what it's optimizing for — speed of response — and notice that in your most valuable week, speed of response isn't the thing you actually want to reward. You want the ",[17,198,199],{},"right regular in the right chair",", and that's a priority problem, not a race.",[10,202,203,204,208,209,213],{},"Publish a real holiday waitlist option to your clients (the exact policy language is in ",[131,205,207],{"href":206},"\u002Fblog\u002Fholiday-booking-policy","Your holiday booking policy","), and if you can, run it as a priority list rather than a broadcast. When the exact wording of the text matters, ",[131,210,212],{"href":211},"\u002Fblog\u002F5-text-templates-for-filling-a-same-day-slot","5 text templates for filling a same-day slot"," has copy you can lift.",[35,215,217],{"id":216},"references","References",[10,219,220,221,224,225,231],{},"This post makes no statistical claims requiring a source. The industry cancellation and no-show baseline referenced across this series comes from Zenoti's ",[17,222,223],{},"2025 Beauty & Wellness Benchmark Report"," (8% cancellation, 3% no-show): ",[131,226,230],{"href":227,"rel":228},"https:\u002F\u002Fwww.zenoti.com\u002Freports\u002Fbeauty-and-wellness-benchmark-report-2025",[229],"nofollow","zenoti.com\u002Freports\u002Fbeauty-and-wellness-benchmark-report-2025",".",[35,233,235],{"id":234},"related-reading","Related reading",[51,237,238,245,252,257],{},[54,239,240,244],{},[131,241,243],{"href":242},"\u002Fblog\u002Ffill-same-day-cancellation","How to fill a same-day cancellation"," — the priority-blast recovery workflow in full.",[54,246,247,251],{},[131,248,250],{"href":249},"\u002Fblog\u002Fsquare-appointments-for-solo-stylists","Square Appointments for solo stylists"," — where a shared waitlist sits, and what it does and doesn't do.",[54,253,254,256],{},[131,255,212],{"href":211}," — the exact copy for the offer text.",[54,258,259,263],{},[131,260,262],{"href":261},"\u002Fblog\u002Fthe-holiday-no-show-problem","The holiday no-show problem"," — why that peak slot is worth protecting in the first place.",{"title":265,"searchDepth":266,"depth":266,"links":267},"",2,[268,269,270,271,272,273,274],{"id":37,"depth":266,"text":38},{"id":81,"depth":266,"text":82},{"id":142,"depth":266,"text":143},{"id":176,"depth":266,"text":177},{"id":192,"depth":266,"text":193},{"id":216,"depth":266,"text":217},{"id":234,"depth":266,"text":235},"A shared waitlist rewards whoever's fastest on their phone — not the regular you actually want in that peak slot. The case for a priority approach, and how it works.","md",null,{},true,"\u002Fblog\u002Fholiday-waitlist-priority-not-first-come","2026-10-10",6,{"title":5,"description":275},"blog\u002Fholiday-waitlist-priority-not-first-come",[286,287],"process-time","cancellations","LRwnMnUODOuRjgISjgSxiIZWfmE3WybCfikhn2ipsU4",1791643603279]