Intern
What you actually do
Split, SMS test, due-list sample. You are not designing a logo for the DSO.
Library / dental groups and DSOs / Dental groups wire recare as a machine, not a card box at each front desk
DSOs inherit a brand. Recare still lives in paper or a PMS the CRM never sees. This vertical wires new-patient speed, two-way reminders, recare clocks, unscheduled treatment as its own journey, and location-correct review asks — with HQ definitions locked so 'recare due' means the same in every site.
DSOs inherit a brand. Recare still lives in paper or a PMS the CRM never sees. This vertical wires new-patient speed, two-way reminders, recare clocks, unscheduled treatment as its own journey, and location-correct review asks — with HQ definitions locked so 'recare due' means the same in every site.
The weekly HQ number is recare-due contacts with an appointment or a task, and new-patient speed-to-lead. Holes in the schedule you cannot name are the leak.
GHL is not a PMS. Do not rebuild charting. Do write the marketing/recall journeys the PMS will not run well.
After-hours missed calls book the group that texts. Honest SMS now, not morning-only.
Locations will invent postcard language. The journeys stay locked. Copy can have local hours.
If PMS and GHL disagree on the person, identity is the first ticket — not more ads.
Intern
Split, SMS test, due-list sample. You are not designing a logo for the DSO.
Operator
Three journeys. Identity with PMS. HQ definitions. After-hours honest. Reviews after visits.
CEO
Schedule holes you cannot name are a system failure. Recare coverage and speed-to-lead are DSO numbers, not front-desk personality.
PMS vs GHL (what each owns), new-patient inquiry, appointment, recare_due_date, unscheduled_treatment, missed-call SMS, GBP per location, HQ recare coverage %, two-way confirm.
Phone/web inquiry → GHL contact + speed path; PMS gets the appointment as the clinical record
Completed new patient → recare_due set; not a postcard hope
Unscheduled treatment → journey, not the recare blast
Review ask after a completed visit, location URL correct
Clinical in PMS. Inquiry, recare journeys, reviews, missed-call in GHL — or admit GHL is decoration.
Why: Two full CRMs is folklore.
Done when: A one-page split.
Web/phone write GHL. SMS under SLA. Source tags.
Why: Paid demand into a pad is a DSO tax.
Done when: Test inquiry in minutes.
From PMS export or a process. Journey: due, booked, completed. HQ coverage %.
Why: Card boxes do not roll up.
Done when: A location’s due list exists in GHL or a synced field.
Do not mix with recare copy.
Why: Treatment plans are not 'we miss you'.
Done when: Two workflows, two tones.
Review journey uses the site’s listing.
Why: Wrong listing is how you decorate a neighbor.
Done when: Location A test gets listing A.
Split page PMS/GHL. Test missed-call SMS. Sample recare_due in GHL. Unscheduled vs recare copy check. One location GBP test.
More locations on ads, a postcard vendor, or a new PMS module as a substitute for recare coverage %. Coverage is the number.
Brand ads. Card box recare. Pad for phones. Reviews at checkout panic. HQ 'recare %' from a story. That is a dental group with a marketing logo.
Recare-due with a next appointment or task, new-patient speed-to-lead, missed-call recover. Definitions locked across sites.
If it runs two-way SMS, speed-to-lead, and HQ coverage you believe, GHL may be thinner. If recall is a mail merge, GHL is the machine.
Then GHL must be the inquiry/SMS layer they actually see, or you accepted the pad. Training is day-1, not optional.
Not recare and new-patient and treatment in one send. Journeys are the product.
This week
This week: PMS vs GHL split, recare_due sample, missed-call SMS, unscheduled path separate, one GBP test. No group-wide blast.
Locations will edit sacred pipelines unless permissions and a change log exist.
Read ↗Call volume is national. Booking is local. Drift is how you pay for ads twice.
Read ↗Day 7–21 after intro predicts member vs lapse. Club WhatsApp is not that clock.
Read ↗Working notes
What HQ should lock, what locations can change, and how rollout actually works. 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.