# Workflows that orchestrate coaching

## Build the play once.  It runs at every location.

A coach writes down the check they’d run, the number that would worry them, and the call they’d make. It happens at every location.

### What the coach typed

"When next week drops below 70% booked, check what campaigns are running and pull the lapsed client list. Draft the reactivation offer. Hold it for the owner to approve."

### Locations

- **Total Locations**: 214
- **Actioned**: 47
- **Adapted**: 31
- **Escalated**: 6
- **No action**: 130

### Status Breakdown

| Location | Status          | Comment                                             |
|----------|------------------|----------------------------------------------------|
| #331     | Actioned         | 62% booked. Draft ready for 340 lapsed clients.    |
| #118     | Adapted          | Promo already live. Suggested extending it.         |
| #402     | Escalated        | New owner, week six. Too early to automate.        |
| #052     | No action        | Seasonal dip. Below this region's threshold.       |

A hundred and thirty locations got nothing, because they didn't need anything.

## A coach’s expertise, arriving the moment it matters

Every workflow here was written by a coach who knew where the growth was hiding. Each one now runs at every location that fits, on that location’s own numbers, at the hour it matters.

### Industries

- Health & Wellness
- Home Services
- Senior Care
- Child-care & Education
- QSR / F&B
- Business Services

### Revenue Workflows

- **Soft week recovery**: Bookings below 70% → lapsed client list pulled, reactivation offer drafted
- **Membership at risk**: Active member, no visit in 30 days → check-in drafted for the front desk
- **Retail attach gap**: Retail per visit below territory median → the script the top quartile uses
- **Marketing review response**: Rating below three stars → response drafted, held for the owner
- **Marketing class fill push**: Class under half booked 48h out → local promo drafted from brand assets
- **Compliance practitioner licence**: Credential expiring in 30 days → renewal chased, escalated at 21
- **Compliance sanitation log**: Nightly close → photo check per station, scored, failures routed
- **Operations no-show pattern**: No-show rate above standard two weeks → deposit policy prompted
- **Operations rebook drift**: Rebook rate declining three weeks, no alert set → surfaced to the coach

## The coach types a play. EZee Assist builds the workflow.

A coach who has never configured anything can write one in a couple of minutes. Dana never opens a canvas.

### Play Example

- **Coach**: Dana R.  
- **Field coach**  
- **Step 1**: typed  
  "When next week drops below 70% booked, check what campaigns are running and pull the lapsed client list. Draft the reactivation offer, hold it for the owner to approve, and tell me it went out."
  
- **Plain language**: 2 min  
- **Soft week recovery**  
  - **Step 2**: what runs  
  - **Trigger**: Bookings for next week below 70%  
  - **Reads**: Scheduling · active campaigns · lapsed client list  
  - **Drafts**: Reactivation offer, brand template  
  - **Approval**: Owner, before send  
  - **Notifies**: Territory coach on send  
  - **Scope**: All locations · adjustable per region  
  - **Author**: Dana R., field coach

## Knowing what to look for was never the problem. Watching for it everywhere was.

### Six kinds of trigger

- **Schedule**: A fixed clock you set  
  Nightly compliance sweep, every location, 2am  
- **Threshold**: A number crosses a line  
  Bookings for next week fall below 70%  
- **Date approaching**: Something expires or comes due  
  Insurance lapses in 14 days  
- **Event**: Something happens in a connected system  
  A new hire is added to the schedule  
- **Inbound**: Someone asks or submits something  
  An owner requests an out-of-policy refund  
- **Hardest to catch**: Drift  
  A number moves quietly over time  
  Rebook rate declines three weeks running

## Every workflow developed is one nobody has to think about again.

A workflow written for one problem keeps solving it, and one that works in a single location can get published to the rest.

### Workflows Adaptation

- These workflows keep adapting after they ship. A workflow reads the same live data your coaches do, so when a threshold stops being the right one, a play is rewritten, or a location’s numbers move, it adjusts what it watches for and what it sends. Nobody reopens it to keep it current.
  
**Month 14**: HQ publishes the first four  
Compliance sweep, soft week recovery, insurance renewal, day-one onboarding.

**Month 3**: Coaches add territory-specific ones  
The plays a coach used to run by hand on a Monday morning.

**Month 6**: Owners submit their own, HQ publishes the best  
A play written in one market runs in 200 locations by the end of the month.

**Month 12**: 290+  
Most recurring work runs without anyone starting it  
Coaches spend their weeks on the four locations that need a person.