Library / Tool / Recare clock: due date, journey, coverage %

ToolHow to wire it

Recare clock: due date, journey, coverage %If the next visit is not on the contact, you are hoping they remember you.

Recare (and next-service, next-session, replenish-of-a-service) is a clock on the person. This worksheet is the field spec: what due means, who sets it, what journey fires, what coverage % you will defend Monday. Card boxes and 'we’ll call them' are not clocks. Dental, chiro, gyms, HVAC memberships, cleaning — same object, different interval.

00

The short version

Intern through CEO

Recare (and next-service, next-session, replenish-of-a-service) is a clock on the person. This worksheet is the field spec: what due means, who sets it, what journey fires, what coverage % you will defend Monday. Card boxes and 'we’ll call them' are not clocks. Dental, chiro, gyms, HVAC memberships, cleaning — same object, different interval.

  1. 01

    Name the interval. 90-day hygiene and 6-month HVAC are different rows, not one postcard.

  2. 02

    Coverage % = due in window with appointment or open task, over due in window. If you cannot compute it, you do not have recare.

  3. 03

    Unscheduled treatment is not recare. Do not use this sheet for that job.

  4. 04

    HQ/DSO: definition locked. Local hours can vary. 'Due' cannot mean three things.

  5. 05

    A blast to the whole list is not this journey.

Who

Same system. Three jobs.

Read your row

Intern

What you actually do

Dates and the %. You are the clock clerk.

Operator

What you protect

Due is a field. Journey is not acquire. Definitions locked if multi-site. Treatment ≠ recare.

CEO

What you refuse to fund

Unnamed holes in the book are the leak. Coverage % is the number.

Wire

How to connect it

Objects, then edges

due_date, last_completed, journey (due / booked / done), coverage %, location if multi, journey vs acquire blast.

  1. 01

    Completed job → due_date set (interval written)

  2. 02

    Due → sequence or task; booked → stage change

  3. 03

    Done → clock resets; not a forever 'we miss you'

  4. 04

    Acquire campaigns exclude due-in-journey if the copy would collide

Steps

Do this in order

Why, then done when
  1. 01

    Write the interval

    Per service type if needed.

    Why: One interval for all services is a lie.

    Done when: Days named.

  2. 02

    Who sets due_date

    PMS sync, checkout checkbox, or intern load.

    Why: Unowned field stays empty.

    Done when: Role named.

  3. 03

    Journey steps

    Due, remind, book, done. Owner.

    Why: A date without a journey is a spreadsheet.

    Done when: Steps listed.

  4. 04

    Compute coverage once

    Even ugly. Last 30 days due.

    Why: The first number is the baseline.

    Done when: A % written.

  5. 05

    Exclude from acquire

    People in recare journey do not get 'new patient' copy.

    Why: Manners.

    Done when: Segment rule.

Intern

Fill interval, owner, first coverage %. Load or sync due dates. You are not designing a postcard.

CEO

Refuse postcard vendors and more ads until coverage % exists. Ads into unnamed holes are loud.

Failure

Card box. Annual mail merge. One 'we miss you' to everyone. No %.

Test

Complete a test job. Due appears. Journey would fire. Coverage math has a numerator and denominator.

Why

Questions people actually ask

Pushback is normal

Our PMS already recalls.

Then this sheet maps what GHL still owns (SMS, HQ %). If PMS coverage is a number you defend, write that here and thin GHL.

Patients/customers hate reminders.

Two-way book is not a marketing blast. Track opt-out. Skipping the clock is how the book holes open.

We’re too small.

Then the intern can set due_date on completed visits this week. Small is why the card box hurts.

Sheet

Fill this in

0 marked

This lives in the browser until you copy it out. The point is to write the spec before anyone opens Workflows or Flows. Print or screenshot when it is true.

  1. Service / interval (days)

    e.g. hygiene 180, filter 90, next session 7.

  2. Field name for due_date

    One name. Synonyms banned.

  3. Who sets it after completed work

    Role + tool (PMS, GHL, intern).

  4. Journey: due → booked → done

    Workflow or task names.

  5. Two-way book? (yes/no)

    If no, how do they confirm?

  6. Coverage % this week (due with appt or task / due)

    Write the fraction, not a vibe.

  7. Window used for coverage

    e.g. due in next 14 days.

  8. Acquire exclusion rule

    In-journey contacts off new-patient copy.

  9. Not this journey (list)

    Unscheduled treatment, win-back of never-patients, etc.

  10. Multi-site definition lock (yes/n/a)

    Due means the same in every location.

This week

This week: interval, owner, due field, first coverage %, acquire exclusion. No list-wide miss-you blast.

Working notes

GHL Engine Checklist

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.

Request the notes ↗
Next

If the leak is expensive, talk.

Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.