Anatomy
- A cron schedule (5-field:
min hr dom mon dow). - A target: an agent or a team.
- A prompt body: what to ask.
- An output sink (optional), Slack, email, GHL note, log only.
- A PHI mode (optional), override the default.
Where to add one
- Per-agent: agent detail → Routines tab.
- Per-team: team detail → Routines tab.
- Cross-agency view: Routines in the top nav, one list of every scheduled routine with deep-links into the owning node.
Sample routines
| What | Cron | Target | Prompt |
|---|---|---|---|
| Morning briefing | 0 8 * * * | Agent: Ambrose | "What changed since yesterday? Summarize in 5 bullets." |
| Renewal scan | 0 9 * * 1 | Team: Renewals | "List clients renewing in next 45 days who haven't received a touch." |
| Watchdog daily | 0 7 * * * | Agent: Sam | "Run aca_scan_book + medicare_scan_book. Post findings to Slack #alerts." |
| Weekly social | 0 9 * * 1 | Agent: Morgan | "Generate this week's social pack (LinkedIn + IG + FB)." |
| Fire a Claude Routine | 0 22 * * * | Agent: Ambrose | Run the Claude Routine "Nightly Book Report". (how) |
Routines only run for a live agent
A routine belongs to an agent, and an agent that is not Live is not in service. Set an agent back to draft and its routines are paused automatically, with the reason recorded on the routine.
Setting the agent live again does not switch them back on. That is deliberate: silently re-arming a job that fires at 6am is a bigger surprise than leaving it off. Turn the routine back on yourself.
The Routines page hides routines whose agent is not live, since they cannot run, and offers a toggle to show them.
Teams are not affected: a team has no live/draft state, so its routines run regardless.