Intern
What you actually do
You count and score. Definitions written if the count took a story.
Library / Tool / Show-rate score: held ÷ booked, by event type
Show rate is held divided by booked for a named event type, weekly. This scorecard asks whether you can compute it, whether no-show is a sequence, whether reminders have one owner, and whether booked-but-missing-in-CRM exists. Calendar occupancy is not show rate. Score the rows; the leaky type is the one you fix first.
Show rate is held divided by booked for a named event type, weekly. This scorecard asks whether you can compute it, whether no-show is a sequence, whether reminders have one owner, and whether booked-but-missing-in-CRM exists. Calendar occupancy is not show rate. Score the rows; the leaky type is the one you fix first.
Always by event type. Discovery vs kickoff vs recare. Blended hides ghosts on discovery.
If GHL never saw the booking, you cannot compute this honestly. Write-in first.
One reminder owner. Two nags train mute and do not raise show.
Recover is a sequence. Founder text only scores low on the recover row.
Use this score before you buy more traffic onto that event type.
Intern
You count and score. Definitions written if the count took a story.
Operator
By type. Write-in. One reminder owner. Recover. Honest stages.
CEO
Ghosts are an ops number. Show rate by type is the number. Until it is computable, occupancy is theatre.
Event type, booked count, held count, no-show count, reminder owner, recover workflow, CRM write-in on book.
Book → GHL opportunity booked
Reminders from one system
No-show → recover same day; stage not left as 'will appear'
Held → stage held; denominator is booked for that type
Discovery or first visit or estimate.
Why: One leaky type is the work.
Done when: Type named.
Booked, held, no-show. Same definition of held.
Why: Occupancy ≠ held.
Done when: Three integers.
Held ÷ booked. Write it.
Why: The score needs a headline number plus the row score.
Done when: % written.
Write-in, one reminder owner, recover, stage honesty.
Why: A high % with no recover still fails the next spike.
Done when: Row total.
Usually write-in or recover or reminder owner — not a new event type.
Why: More types multiply the mess.
Done when: Action logged.
Counts by type. % . Tick the system rows. You are not redesigning the booking page until write-in and recover are scored.
Refuse more ads to a type that scores low on write-in or recover. You will buy more ghosts.
Blended %. Two reminder systems. No-shows stay booked. Calendar occupancy as the slide.
Last week’s three integers exist. Recover test on a cancel. One reminder owner.
Write the rule: reschedule is not a no-show if they rebook same week, or it is — but write it. Inconsistent rules make the % a fight.
If they do not match GHL, you have two databases. The operating % is the one on the opportunity.
It depends on type. The system score is whether you can defend the number and recover the rest. Do not hunt a vanity target while write-in is broken.
Each row is a pass/fail. 0% is not a grade for the brand — it is whether the objects exist. Under 50% means do not add traffic. 50–80% means finish write-in. Above 80% means review Monday, then the next leak.
1 if one type. Blended only = 0.
1 if an integer exists in GHL.
1 if definition is on the page.
1 if written. Story = 0.
1 if last write-in test included this type.
1 if Calendly xor GHL, not both.
1 if a cancel test moved.
1 if a workflow or tasked sequence.
1 if yes. Argument every Monday = 0.
1 if owner + date. 'Try harder' = 0.
This week
This week: one event type, three counts, %, system row score, one action. No new event type.
Working notes
The minimum CRM, pipeline, and nurture spec before you add more pages. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.