Intern
What you actually do
Link hunt and the test book. Killer of leftover URLs. You do not keep the old link 'for A/B'.
Library / Wire / One appointment source of truth — native GHL calendar or Calendly, not both as public doors
Native GHL calendars write contacts easily and still get abandoned because the team lives in Calendly. Calendly writes easily and still fails GHL if the integration is a second thought. The wire is a choice: which tool is the public booking door for which job, reminder owner, and how the other tool is demoted. This is not a feature comparison grid — the compare essay lives elsewhere. This is how to wire the choice you already made, or to make it.
Native GHL calendars write contacts easily and still get abandoned because the team lives in Calendly. Calendly writes easily and still fails GHL if the integration is a second thought. The wire is a choice: which tool is the public booking door for which job, reminder owner, and how the other tool is demoted. This is not a feature comparison grid — the compare essay lives elsewhere. This is how to wire the choice you already made, or to make it.
Count public links. If the site, Instagram, and email signatures disagree, you already have two doors. Pick Discovery’s door this week.
Round-robin in both tools is how availability lies. Users live in one scheduler for public jobs.
Embeds: a GHL form that then opens Calendly is fine if the form already wrote the contact and Calendly matches email. Two embeds that both create contacts are doubles.
Timezone and buffers must be set in the source of truth. The other tool will not save you from a double-book if it is still public.
Migrating: unpublish the loser, 301 or replace links, keep the old tool read-only for history if needed. Do not 'run parallel for a month' as a lifestyle.
Intern
Link hunt and the test book. Killer of leftover URLs. You do not keep the old link 'for A/B'.
Operator
One door per job. Write-in on that door. Migrate leftovers. Settings live where bookings live.
CEO
Two booking products on the same job is an unowned pipeline. One public URL is the number. Until it is true, show rate is not comparable.
GHL calendar event type, Calendly event type, public booking URL, contact, opportunity, reminder owner, round-robin users, timezone, embed vs link.
Public Discovery URL exists in exactly one tool; the other is unpublished for that job
That tool writes GHL contact + opportunity on book
Reminders owned once; round-robin lives in the chosen tool, not both fighting availability
Internal-only events (kickoff already paid) may use the other calendar if named as internal
Site, bios, ads, email footers, QR codes. Who uses Calendly, who uses GHL. List event types.
Why: You cannot choose a source of truth you have not seen.
Done when: A table of live URLs and tools.
One sentence: public discovery is GHL calendar or Calendly. Internal kickoff may differ if named. Unpublish the other discovery event.
Why: Without a kill, 'choice' is two doors.
Done when: Old discovery URL does not take new bookings (or redirects).
Book as a stranger. Contact + opportunity + reminders from one owner. Round-robin if you use it: correct user.
Why: Choosing Calendly without write-in is the original leak. Choosing GHL without the team using it is a ghost calendar.
Done when: Test booking is true in GHL. Team knows which link to send.
Site, ads, signatures, lead magnets, ScoreApp outro. Search the repo and the brand. A leftover Calendly in a PDF is still a door.
Why: Parallel month becomes parallel year via leftovers.
Done when: Search pass: no stray public discovery link on the losing tool.
Do not keep 'the good reminder settings' on the unpublished tool. Recreate on the source of truth. No-show path as in calendly-to-ghl.
Why: Settings left behind are how show rate dips after migration and people blame the new tool.
Done when: Reminder and buffer settings live on the public door. No-show test passes.
URL inventory. Unpublish the losing discovery event. Test-book the winner. Grep the site and ads for leftover links. Recreate reminders on the winner. You are not 'evaluating UX'. You are closing a door.
Calendly Teams seats and GHL calendar rebuilds in the same quarter without a chosen door. Paying both to be public is paying for double-bookings.
Site has GHL embed. Instagram has Calendly. Ads have a third scheduling link from a freelancer. Reminders from two tools. Round-robin in neither correctly. Pipeline half-empty. That is not a preference. That is three CRMs.
One public discovery URL. Write-in true. Leftover links dead. Reminders once. Team sends only the winner. No-show path on the winner.
That is two doors. You can split jobs (discovery vs webinar), not split departments on the same job.
Yes if write-in is perfect and you accept one door. Ugly with a pipeline beats pretty with two databases. Then still only one public discovery link.
A third door. Either it writes GHL as a named event type or it is banned.
This week
This week: inventory, pick Discovery’s door, unpublish the loser, replace links, recreate reminders, test write-in. No parallel month as a plan.
A full calendar and an empty pipeline is two databases.
Read ↗A high score in a CSV is not a qualified opportunity.
Read ↗If the thank-you does not change the contact, the page was a brochure.
Read ↗If paid lives in Stripe and the opportunity is still open, reporting is theatre.
Read ↗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.