Weekly round-robin or day-of-week, holiday overrides that always win, print it or export CSV. This isn't a template: it runs the same rotation resolver that routes Hello AI's live after-hours escalations.
Overrides always beat the rotation, exactly as in Hello AI's live resolver.
Mon Aug 3
Dr. Patel
Tue Aug 4
Dr. Patel
Wed Aug 5
Dr. Patel
Thu Aug 6
Dr. Patel
Fri Aug 7
Dr. Patel
Sat Aug 8
Dr. Patel
Sun Aug 9
Dr. Patel
Mon Aug 10
Dr. Nguyen
Tue Aug 11
Dr. Nguyen
Wed Aug 12
Dr. Nguyen
Thu Aug 13
Dr. Nguyen
Fri Aug 14
Dr. Nguyen
Sat Aug 15
Dr. Nguyen
Sun Aug 16
Dr. Nguyen
Mon Aug 17
Dr. Rivera
Tue Aug 18
Dr. Rivera
Wed Aug 19
Dr. Rivera
Thu Aug 20
Dr. Rivera
Fri Aug 21
Dr. Rivera
Sat Aug 22
Dr. Rivera
Sun Aug 23
Dr. Rivera
Mon Aug 24
Dr. Patel
Tue Aug 25
Dr. Patel
Wed Aug 26
Dr. Patel
Thu Aug 27
Dr. Patel
Fri Aug 28
Dr. Patel
Sat Aug 29
Dr. Patel
Sun Aug 30
Dr. Patel
Email me this schedule (CSV attached)
Generated by the same rotation resolver that routes Hello AI's live after-hours escalations, so what you print here is exactly what our AI would do with the same settings.
The honest limitation
A printed rotation fixes who is responsible. It doesn't fix the 2am mechanics: someone still has to answer, triage, reach the on-call provider, try the backup when they sleep through it, and write down what happened. Hello AI runs this exact schedule live: it answers every after-hours call, deflects emergencies to 911, lets the patient flag urgency, dials your on-call provider until someone accepts, and logs every attempt with talk time. See how after-hours triage works or what coverage options actually cost.
FAQ
The two patterns that survive contact with real life are a weekly round-robin (each provider takes a full week, trading fairness for longer stretches) and day-of-week assignment (Dr. A always has Mondays, which suits fixed personal schedules). Whichever you pick, the schedule is only as good as its override handling: holidays, vacations, and swaps must beat the rotation, or the calendar is fiction within a month.
Three things, in order: the schedule lives in someone's head or a stale spreadsheet, so the answering service pages the wrong provider; overrides get handled by group text instead of the system of record; and nobody logs who was actually reached at 2am, which matters for both fairness and liability. Fixing the artifact (a current, printed or shared schedule) fixes the first two; logging needs tooling.
Identically. This page runs the same resolver that Hello AI uses on live calls: when an urgent after-hours call comes in, it computes who is on call at that exact moment in your practice's timezone, applies any date overrides first, then dials that provider, cascades to backups if they don't accept, and logs every attempt with timestamps.