Skip to main content

​
Configuring alerts

Alerts tell you an athlete needs attention without you having to check the roster. From your alert settings you decide what to be alerted about, how loud, and where it lands.

​
What happens if you change nothing

A coach who never touches a dial gets in-portal notifications only. No email, no push. Under-fueling, symptoms, low session ratings and dialing-down trends are on in the in-portal lane from day one; the hyponatremia pattern, the sleep trend, and the gone-quiet flag start off and are opt-in.
Editing alert rules needs Pro Coach or higher, and so do the paid channels. On the free Coach tier, and after a paid tier lapses, you can still read your configuration and receive in-portal notifications, but email and push are not delivered.

​
Start with a preset

The fastest setup is a preset applied across your whole roster, which you then refine.

​
Then refine by scope

Rules resolve at three scopes, layered from broadest to narrowest:
  • Overall, your whole roster.
  • Group, one group. Create groups first in your roster.
  • Athlete, a single athlete, which wins last.
So you might run Balanced overall, Hands on for your race-prep group, and a custom rule for one athlete you are watching closely. When an athlete belongs to more than one group, Saturday does not pick a group arbitrarily. It reduces across every group the athlete matches and takes the most sensitive setting, then applies any athlete-level override on top.

​
What you can configure

  • Triggers. Seven of them: under-fueling, symptoms, low session ratings, a hyponatremia pattern, a dialing-down trend, a sleep trend, and an athlete who has gone quiet.
  • Thresholds. The line that counts as a concern, which defaults to the shared concern cutoff of 70% of prescribed, and a separate urgent line for real-time pings, which defaults to 50% for under-fueling. Leave either unset and it inherits the shared cutoff.
  • Urgent versus digest. Real time for urgent items, a once-a-day bundle for the rest, one bundle per athlete per day.
  • Channels. In-portal, email, and mobile push. SMS is not offered.
  • Quiet hours. Suppress non-urgent pings overnight, in your own time zone.
  • Combinations. Two-trigger AND rules, for example “ping me only when sodium is short and there is a symptom in the same session”. Both legs must be session-level triggers; the sleep trend and the gone-quiet flag describe a window rather than a single session, so they cannot be combined.
Webhook delivery is not live yet. You can select the webhook channel on a rule, and the portal marks it as pending rather than silently dropping it. Managing an organization’s webhooks is a Business and Enterprise capability. For programmatic alerting today, use the Coach API or the Claude connector, which read and write the same rule model the GUI does.

​
Payment-failure alerts

You can be alerted when any roster athlete, coach-paid or self-paying, has a payment failure, so an athlete never quietly loses access on your watch. This rule is configured alongside the fueling triggers and carries no percentage threshold. When the athlete is the payer they are alerted too, at a noise level you set, and deep-linked to update their card. Who pays for each athlete is set from the athlete’s row menu on your roster, under Cover, Stop covering, and Change payer; see Take over & relinquish for the grace-window behavior behind this.

​
See also