The shop with Lesson 1's receptionist architecture deployed and Lesson 2's recovery loop running captures 85-88% effective booking floor at day 90. Show rate is the next number that decides whether those bookings convert into completed jobs. CSR show rate — the percentage of booked appointments where the truck actually runs and the homeowner is there — sits at 84% industry baseline at residential trades shops. Top-quartile shops run 92%+. The 8-point gap is structurally CSR-coachable: it lives in the booking conversation, not the dispatch board. At a 7-truck shop running 180-230 booked calls per week, an 8-point lift is 14-18 additional weekly completed jobs at $387 average diagnostic-plus-repair ticket — $5,400-$7,000 per week of recovered revenue, $280K-$365K annualized. This lesson is the named workflow for the L3 service manager to pull every booked-and-lost call from the prior week, AI-tag the kill reason against four standardized buckets (price-shock, no-window-commitment, dispatch-fee-objection, after-hours-confusion), and build next Monday's CSR huddle in 20 minutes. Target: lift CSR show rate from 84% to 92%+ inside 90 days. The workflow is the third workflow in the L3 Ch2 stack and the one that converts the architecture-plus-recovery booking gains into completed-job revenue rather than no-show write-offs.

Why Show Rate Is the Third Leg of the L3 Ch2 Stack

A shop can run a perfect receptionist architecture, a tuned recovery loop, and an 87% effective booking floor — and still leak $280K-$365K per year through no-shows. Booking percentage moves the top of the funnel; show rate moves the bottom. The two metrics are independent: a CSR row can book at 87% and show at 78%, or book at 70% and show at 94%. The shops that pair architecture-driven booking gains with no show-rate discipline see their booking-% scorecard rise while their average-ticket and RPT scorecards stall because dispatched-but-not-run calls do not produce revenue. The L3 service manager who completes Lesson 1 and Lesson 2 without Lesson 3 watches the dashboard show recovery wins and EBITDA hold flat.

Show rate failures concentrate in four kill reasons that are CSR-conversation-rooted, not dispatch-rooted. Roughly 80% of no-shows trace back to something the CSR said or did not say during the original booking conversation. The remaining 20% are genuine homeowner-side cancellations (emergency, family event, financial change). The 80% is what this workflow targets. Price-shock no-shows happen when the CSR mentioned the dispatch fee in passing but did not anchor the credited-against-repair frame, the homeowner sleeps on it overnight, gets price-anxious, and cancels in the morning. No-window-commitment no-shows happen when the CSR left the slot loose ('we'll see you Tuesday morning sometime'), the homeowner is not ready when the truck pulls up, and the call is abandoned. Dispatch-fee-objection no-shows happen when the CSR booked over a soft objection without resolving it; the homeowner thinks more about it overnight and cancels. After-hours-confusion no-shows happen when the AI receptionist booked overnight and the morning CSR did not call to confirm; the homeowner is unclear about the slot and is not home.

Each kill reason has a CSR-conversation-level fix that the weekly huddle can address. The fix is not theoretical training — it is a 20-minute, kill-reason-specific coaching cycle that ships next Monday's CSR row with the language to prevent that no-show pattern from repeating. The compounding effect over 12 weeks lifts show rate from 84% to 92%+ as each weekly fix closes one kill reason's distribution share.

The Four Kill Reasons and Their CSR-Conversation-Rooted Causes

The named CSR show-rate kill-reason taxonomy is four categories. Stable, mutually exclusive, and observable from a 90-second listen to the original booking call. The AI tags each lost call against this taxonomy during the Friday data pull; the service manager validates the AI's tag during the 20-minute huddle prep.

Price-Shock No-Shows

The dispatch fee was mentioned but not anchored. The CSR said something like "and there's a $79 dispatch fee" without immediately reframing it as credited-against-repair. The homeowner agreed in the moment because the rest of the call felt good, but slept on it, talked to a spouse, or compared against a friend's recent service experience, and decided overnight that $79 felt expensive. The cancellation comes at 7:15 a.m. before the truck rolls, or the homeowner is just not home when the tech arrives. Roughly 30-40% of show-rate failures at residential shops trace to this pattern. The fix is the credited-against-repair anchor language deployed on every booking that mentions the dispatch fee — the same L2 Ch2 price-shopper rebuttal applied to the booking-confirmation phase. Coaching focus: rehearsed language in three variants depending on whether the homeowner expressed price concern, neutral acknowledgment, or active enthusiasm.

No-Window-Commitment No-Shows

The CSR booked the call but left the slot ambiguous. "We'll see you Tuesday morning" is a no-window-commitment booking; "we'll be there between 8 and 10 Tuesday morning, and Marco will text you when he's 20 minutes out" is a window-committed booking. The homeowner without a specific window does not plan their morning around the call, schedules competing errands, and is gone when the truck arrives. Roughly 25-35% of show-rate failures trace to this pattern. The fix is the two-hour window discipline (always offer a 2-hour window, never four or open-ended), the on-my-way-text commitment ('Marco will text 20 minutes out'), and the day-before reconfirmation text. Coaching focus: window-specific language and the on-my-way-text protocol from L2 Ch3 L3.

Dispatch-Fee-Objection No-Shows

The homeowner raised an explicit objection to the dispatch fee during the call and the CSR booked anyway without resolving it. Common patterns: 'Can you waive the fee?' 'Is the fee really necessary?' 'Other shops told me no fee.' The CSR who responds 'I understand, but the fee is our policy' and books the call has not resolved the objection — the homeowner is committed to the booking but ambivalent, and overnight ambivalence resolves to cancellation. Roughly 15-25% of show-rate failures trace to this pattern. The fix is the explicit-objection resolution language: acknowledge, reframe with credited-against-repair, offer the call-without-fee path (escalate to manager) if the homeowner remains firm, but do not book over an unresolved objection. Coaching focus: objection-resolution language and the explicit cue 'are you comfortable with the dispatch fee before we lock the slot.'

After-Hours-Confusion No-Shows

The AI receptionist booked an overnight call; the morning CSR did not call or text to confirm before the truck rolled. The homeowner is unclear which shop is coming (maybe they called multiple), the slot details are fuzzy (the AI's confirmation text was deleted), or they have already moved on (they called another shop in the morning and forgot about the overnight booking). Roughly 15-25% of show-rate failures at architecture-deployed shops trace to this pattern. The fix is the 7:30 a.m. morning-CSR confirmation call or text — the named workflow that mirrors the L3 Ch2 Lesson 1 morning CSR overnight-review discipline. Coaching focus: the confirmation script ('I'm calling from Tampa Comfort to confirm Marco's 10-to-12 arrival window today; gate code still 4-2-1-9?'), the question pattern that surfaces homeowner doubt, and the warm reschedule path if the homeowner has changed their mind.

The Weekly Friday Pull and 20-Minute Huddle Build

The workflow's central cadence is Friday afternoon: the service manager pulls every booked-and-lost call from the prior week, AI-tags the kill reason, builds the next Monday's CSR huddle in 20 minutes, and ships it to the CSR-floor lead before 5 p.m. Friday. The 20 minutes break into four 5-minute blocks.

Block One: The Pull (5 Minutes)

Open the FSM (ServiceTitan, Sera, HCP, FieldEdge, or BuildOps) and the AI receptionist's post-call audit log. Filter for the trailing 7 days. Pull every booked appointment that did not run — no-show, cancel-day-of, cancel-night-before. Export to a spreadsheet with the booking date, the original CSR, the homeowner name, the call recording link, and the FSM cancellation reason if logged. Typical 7-truck shop: 18-28 booked-and-lost calls per week.

Block Two: The AI Tag (5 Minutes)

Run the lost-call list through a kill-reason classifier prompt that the service manager wrote once and reuses weekly. The prompt loads the four-kill-reason taxonomy, the call recording's transcript (auto-transcribed via CallRail Conversation Intelligence, ServiceTitan, or Avoca's post-call summary), and the homeowner-side cancellation reason if available. The classifier outputs one of the four kill-reason tags per call plus a 1-sentence rationale citing the transcript phrase that drove the classification. Service manager scans the output, validates the AI's tags by spot-checking the rationale against the transcript (typically 3-5 minutes of spot-checking 18-28 calls), and overrides any miscategorization. The validated distribution surfaces: this week, 40% price-shock, 30% no-window-commitment, 18% dispatch-fee-objection, 12% after-hours-confusion. The largest share defines this week's coaching priority.

Block Three: The Huddle Deck (5 Minutes)

The huddle deck is a single page or two slides. Top section: this week's kill-reason distribution chart. Middle section: the three most representative lost calls (one for each of the top kill reasons) with the homeowner anonymized, the CSR identified, the specific transcript phrase that drove the classification quoted, and the corrective language the CSR should have used instead. Bottom section: this week's coaching focus — the single kill reason with the largest share, the rehearsed language to deploy, and the practice script for the Monday huddle. The deck reads in 4 minutes; the service manager spends 5 minutes drafting it because the AI-tagged distribution and the transcript phrases pre-populate.

Block Four: The Floor Handoff (5 Minutes)

The deck ships to the CSR-floor lead Friday 5 p.m. with a brief Slack or email note: 'this week's coaching focus is no-window-commitment. Three example calls in the deck. Monday huddle runs the rehearsed language from page 2. Side note: CSR Jamie has 3 of the 5 no-window-commitment cases — pull her aside Monday afternoon for a 1:1 if the huddle doesn't land.' The CSR-floor lead reads the deck, prepares the Monday morning huddle (using L2 Ch2 Lesson 1's Monday huddle structure), and the floor walks in Monday with the language ready to deploy. Total service-manager time: 20 minutes Friday. Total CSR-floor-lead time: 15 minutes Monday morning. Total floor time: 15-minute huddle plus active deployment through the week.

The Monday Huddle and the Rehearsed Language for Each Kill Reason

The Monday huddle is the artifact that converts the Friday analysis into next-week's show-rate movement. The CSR-floor lead opens with this week's coaching focus (the largest-share kill reason from the Friday pull), walks the floor through the three example calls, has each CSR rehearse the corrective language out loud once, and closes with the metric target for the week.

Price-Shock Rehearsed Language

Three variants depending on the homeowner's tone when the dispatch fee comes up. Variant A (neutral acknowledgment): 'Standard dispatch is $79, and that's fully credited toward any repair you approve — so really it's just a free diagnostic when we get the work. I've got Marco coming Tuesday between 10 and 12.' Variant B (price concern signaled): 'Heard you on the price. The $79 dispatch is fully credited toward any repair you approve, which means as soon as Marco diagnoses and you give him the go-ahead, the $79 comes off the top of the repair invoice. Most folks find that's the most honest way to price this kind of work because the alternative is the phone quote that turns into the surprise bill at the end.' Variant C (enthusiasm): 'Easy — $79 dispatch credited toward any repair. I'll get you on the schedule Tuesday between 10 and 12 with Marco.' Each CSR rehearses Variant A once during the Monday huddle; Variants B and C live in the digital reference for in-call use.

No-Window-Commitment Rehearsed Language

The window discipline language: 'Marco will be there between 10 and 12 Tuesday morning, and he'll text you when he's 20 minutes out so you've got time to put the dog away or wrap up anything you're in the middle of. We'll also send you a confirmation text tonight and another one Monday morning so it's locked in your phone.' Every booking gets a 2-hour window and the on-my-way commitment. The CSR-floor lead practices this language with each CSR Monday morning until it lands in 12-15 seconds of phone time.

Dispatch-Fee-Objection Rehearsed Language

The objection-resolution sequence: acknowledge ('I hear you'), reframe ('the $79 isn't a fee like other shops charge — it's a credit toward your repair'), offer the no-fee option if applicable ('we do also offer free estimates on full-system replacement; if you're thinking that direction we can send a Comfort Advisor at no charge'), and the explicit cue if the homeowner remains firm ('are you comfortable with the dispatch fee before I lock the slot — I don't want to schedule the truck if you've got reservations'). The cue is the show-rate-saving move because it converts overnight ambivalence into a 1:1 escalation rather than a no-show.

After-Hours-Confusion Rehearsed Language

The morning confirmation script: 'Good morning {name}, this is Sarah from {shop}. I'm calling to confirm Marco's arrival window today between 10 and 12. He'll text you when he's 20 minutes out. Quick question — is the gate code still 4-2-1-9 and the dog still goes by Biscuit?' The question pattern surfaces homeowner doubt because the gate-code-or-pet recall test pulls cooperative confirmation; a homeowner who hesitates on the gate code has often forgotten the appointment, and the CSR can warm-reschedule rather than send the truck to an empty house. The CSR-floor lead rehearses this script with the morning CSRs at the Monday huddle for the week.

The Metrics and the 90-Day Rollout for Show-Rate Coaching

The show-rate coaching workflow moves three headline numbers and three diagnostic numbers. The service manager reads them Friday at 4 p.m. before the weekly pull.

Overall CSR show rate. Baseline 84%; target 92%+. Each point is approximately 1.5-2.5 additional completed jobs per week at a 7-truck shop, $580-$970 of recovered weekly revenue. The 8-point lift compounds to $280K-$365K annualized.

Kill-reason distribution shift over trailing 4 weeks. The largest-share kill reason should rotate every 2-4 weeks as last week's coaching focus closes its share and a new pattern surfaces. A kill reason that stays largest for 6+ weeks signals coaching is not landing — the language is not being deployed, the floor lead is not running the huddle, or the kill reason is structurally trickier than the workflow assumed.

Show rate by CSR. Per-CSR distribution surfaces who is structurally underperforming. The top performer typically lands 4-7 points above the floor average; the bottom performer typically lands 6-9 points below. The 1:1 coaching at the Monday afternoon side-meeting addresses bottom-performer drift before it compounds into a write-off termination.

Three diagnostic numbers: kill-reason-mix volatility (excessive week-to-week swings suggest small-sample noise rather than workflow signal; smooth with 4-week trailing average), morning-confirmation completion rate (target 95%+; below 90% means the morning CSR is not running the confirmation script and after-hours-confusion no-shows are unaddressed), and same-day cancellation rate within the cancellation distribution (target under 20% of total cancellations; rising same-day cancellation means homeowners are deciding against the call last-minute, which often signals over-promising on dispatch-fee credit or window commitment).

The 90-day rollout. Week 0: write the kill-reason classifier prompt, build the huddle deck template, train the CSR-floor lead on the Monday huddle structure, brief the floor on the new coaching cadence. Week 1: Friday pull at 4 p.m., huddle deck shipped Friday 5 p.m., Monday huddle at 8:00 a.m., active coaching through the week. Show rate moves 1-2 points by week 4. Weeks 5-8: depth phase — second-pass language for variant patterns (elderly homeowner pacing, multi-property landlord windows, high-emotion objection-resolution). Show rate moves another 2-3 points to 87-88%. Weeks 9-12: polish — edge cases and per-CSR 1:1 coaching for any CSR still 5+ points below floor average. Show rate lands at 92%+ by day 90.

The Failure Modes the Show-Rate Workflow Defends Against

Three failure modes kill the workflow. First, the "Friday pull skipped" failure: the service manager skips the pull. Show rate stops moving because no kill-reason distribution surfaces. Fix: the 20-minute Friday cadence is non-negotiable; if the service manager cannot run it, the ops manager or floor lead runs it. Second, the "Monday huddle reduced to information" failure: the CSR-floor lead reads the deck out loud but does not have CSRs rehearse. Show rate moves 1-2 points and stalls. Fix: every Monday huddle includes 60-90 seconds of CSR-by-CSR rehearsal of the focus-kill-reason language. Third, the "kill-reason taxonomy drift" failure: the classifier prompt is not maintained and categorizes inconsistently across weeks. Show rate movement looks erratic. Fix: quarterly prompt audit against 20 sample calls.

The workflow also defends against an upstream failure mode: the L2 Ch2 rebuttal library not being calibrated. If the L2 Ch2 library was deployed with vendor-default language, the show-rate coaching's price-shock rehearsed language inherits chatbot voice and homeowners pattern-match-and-reject the credited-against-repair frame. Show rate movement plateaus at 87-88% instead of reaching 92%+. The fix is the L2 Ch2 rebuttal library rebuilt against the brand-voice anchor document before the L3 Ch2 show-rate workflow can compound to target.

The Weekly Owner Report and the Quarterly Show-Rate Review

The show-rate coaching workflow reports weekly to the owner with two numbers and one paragraph. Friday 5 p.m. email: (1) overall CSR show rate this week vs. trailing 4-week average and the dollar value at $387 average ticket; (2) this week's coaching focus and the kill-reason it targets. Paragraph commentary: 4-6 sentences from the service manager naming the wins, the gaps, and the next-week priority. The owner reads in 3 minutes. The chart belongs to the L3 Ch2 dashboard from Lesson 4 — the show-rate metric integrates with the architecture-and-recovery dashboard rather than living separately.

The quarterly show-rate review (60 min, service manager with ops manager) re-evaluates the kill-reason taxonomy stability, the classifier-prompt calibration, the per-CSR coaching distribution, and the integration with the L2 Ch2 rebuttal library. The review catches structural shifts the weekly cadence misses — a kill-reason becoming obsolete (price-shock shrinking below 15% as L2 Ch2 library matures), a new kill-reason emerging (financing-anxiety as replacement mix grows), or a CSR-distribution shift (one rookie consistently 8+ points below average needing PIP). Output: refreshed taxonomy if needed, recalibrated prompt, updated per-CSR coaching plan.

Key Takeaways

• Show rate is the third leg of the L3 Ch2 stack. Lesson 1 builds the architecture (75% Tier-One capture). Lesson 2 builds the recovery loop (85-88% effective booking floor). Lesson 3 lifts CSR show rate from 84% to 92%+ — converts booking gains into completed-job revenue.
• Eight points of show-rate lift = $280K-$365K annualized at a 7-truck shop. Each point is approximately 1.5-2.5 additional weekly completed jobs at $387 average ticket. The workflow is the highest-ROI 20-minute Friday build in the L3 Ch2 stack.
• Four kill reasons cover 80%+ of CSR-conversation-rooted no-shows. Price-shock (30-40%, dispatch fee not anchored as credited-against-repair). No-window-commitment (25-35%, slot left ambiguous). Dispatch-fee-objection (15-25%, booked over unresolved objection). After-hours-confusion (15-25%, no morning confirmation).
• The 20-minute Friday cadence breaks into four 5-minute blocks. Pull (export booked-and-lost calls from FSM and AI receptionist log). AI tag (classifier prompt outputs kill-reason taxonomy with rationale). Huddle deck (one page, three example calls, focus kill reason, rehearsed language). Floor handoff (ship to CSR-floor lead Friday 5 p.m. with brief context note).
• Monday huddle rehearses language, not information. Every Monday huddle includes 60-90 seconds of CSR-by-CSR rehearsal of the focus-kill-reason language. Reading the deck out loud without rehearsal moves show rate 1-2 points and stalls; rehearsal compounds the lift to 92%+.
• Each kill reason has a rehearsed language artifact. Price-shock: three variants (neutral, price-concern, enthusiasm) of the credited-against-repair anchor. No-window-commitment: the 2-hour window plus on-my-way text plus day-before reconfirmation. Dispatch-fee-objection: the acknowledge-reframe-offer-cue sequence with explicit comfort check. After-hours-confusion: the morning confirmation script with the gate-code or pet-name recall test.
• Three failure modes to defend against: Friday pull skipped (no kill-reason distribution surfaces), Monday huddle reduced to information (no rehearsal, language stays informational), kill-reason taxonomy drift (classifier inconsistent, show-rate movement looks erratic). Each has a documented fix.
• The workflow integrates with L2 Ch2 rebuttal library and L3 Ch2 Lesson 1 architecture. Show-rate coaching depends on the L2 Ch2 library being calibrated (chatbot voice in price-shock language plateaus show rate at 87-88%) and on Lesson 1's morning CSR confirmation discipline. The three pieces compound together; deploying one without the others underperforms.