All use cases

Engage / Lifecycle

Recovery-score readiness coach

Your recovery score landed red this morning — instead of a number on a dial you have to interpret, the agent tells you exactly how to play today, and on a green day tells you to go for it.

Get aheadSystem triggerTime-based triggerPushIn-appChatWellness (B2C apps)

What it does

A wearable computes a morning recovery or readiness score every day, but the member has to open the app, find the number, and work out what it means for their training — so the single most useful signal the device produces goes unread by lunchtime. Leave it as a passive metric and engagement decays into a dashboard nobody checks; over-train a red day or waste a green one and the member loses trust in the score entirely. The agent turns each morning's reading into one plain-language plan for the day: ease off and keep strain low when recovery is poor, and push for the harder session when it is high. The number becomes a daily coaching conversation rather than a chart the member stops opening.

How it works

  1. 1
    Trigger. the morning recovery/readiness score posts from the connected wearable, or the daily readiness window opens — red, amber, or green against this member's own band.
  2. 2
    Decision. the agent reads the score against the member's personal baseline and recent training load from memory (not a population average), checks it has not already coached them today, and decides whether the day calls for an ease-off, a hold-steady, or a green-light to push.
  3. 3
    Action. it sends one concise readiness plan on the member's preferred channel — a strain ceiling and a lighter suggestion on a red day, an encouraging go-harder prompt on a green day — every unprompted message gated by a quality and tone judge.
  4. 4
    Follow-through. the score and the plan write back to memory so tomorrow's message builds on today's; if the member trains anyway, the next reading is read in that context; a stale morning nudge is cancelled if the member already opened the app and saw the score themselves.
Example
AgentMorning — recovery came in at 31%, in the red for you after three hard days. Today's a back-off day: keep strain under 8, an easy walk or mobility session, and protect tonight's sleep. You'll bounce back faster than pushing through it.
MemberI was going to do legs today though
AgentHold legs one more day — your numbers will thank you. If tomorrow's recovery is back in the green I'll flag it and that's your day to go heavy. For today, easy wins.

Configuration

How the agent is wired for this use case.

Triggerthe daily recovery_score_posted event from the wearable/device feed (or the morning readiness-window timer) carrying the red/amber/green band for the member.
Tools & actions
  • Wearable/device feed · ingest the morning recovery/readiness score, recent strain, and sleep to set the day's plan
  • App backend · read the member's personal baseline band and recent training load to judge whether to back off, hold, or push
  • Persistent memory · recall the member's goal, last few days' scores, and what plan they responded to, and write today's score and plan back
  • Knowledge base · retrieve the program's approved readiness-to-activity guidance for the message
  • Messaging channel · deliver one judge-gated readiness plan on the member's preferred surface
Autonomyscore interpretation, baseline comparison, and the single daily readiness plan run unattended under judge gating, quiet hours, and frequency caps. This is non-clinical training guidance only — no diagnosis, no medical instruction read off a biometric score; under a wellness-safety policy class, any reply suggesting injury, illness, or a health concern beyond training load is detect-and-escalate to a human, never handled by the agent.
Channelspush · in-app · chat
Escalationa reply indicating pain, a medical symptom, or distress, or a reading pattern outside safe lifestyle-guidance bounds, hands off to a human pathway with context rather than being answered; a member who asks to stop the daily coaching is honoured immediately.

What you need

The inputs this use case runs on. Your channels stay yours; the agent supplies the judgment.

Signals

the daily recovery/readiness score event, recent strain and sleep readings, and member replies

Data

the member's personal recovery baseline and band, recent training load, stated goal, channel and notification preference, consent for health-data use, quiet hours, persistent cross-session memory

Guardrails

non-clinical training guidance only — no medical or diagnostic advice from a biometric score, with a stated boundary and human escalation on any health concern; judge gating on every daily message; frequency caps and quiet hours so it coaches rather than nags; explicit consent and compliant handling of sensitive health data; stale-nudge cancellation when the member checks the score themselves; visible opt-out

Metrics it moves

  • dau-mauup: a personal daily plan gives the member a reason to engage every morning instead of ignoring a passive score
  • adherenceup: members train to their actual readiness, so good days are used and bad days are recovered from, keeping the routine intact
  • churndown: a wearable that actively coaches each day stays worth paying for, where a number on a dial quietly stops being opened

Related use cases

Engage / Lifecycle

Wearable-driven rest and recovery nudge

the single rest touch this daily readiness-to-plan loop generalises, including push-harder days

Engage / Lifecycle

Proactive coaching companion for fitness and wellness

the broader habit-and-streak coaching this daily readiness plan feeds into

Engage / Lifecycle

Rich-UI self-serve data exploration in thread

when the member wants to explore the recovery and strain data behind the plan

See it on your own customer journey

Bring one drop-off, one churn cliff, or one silent segment. We will show you what a proactive agent with memory and judgment does with it.

Book a demo