Plan 24/7 phone coverage: shifts, peaks and backup owners

01 / A weekly coverage operating plan

Measure demand by interval before assigning the week

Collect your own call arrivals and handling time by interval, including simultaneous demand, unanswered calls and work performed after the conversation. Separate new requests from existing-customer work. A monthly total cannot show whether a quiet night and a short morning burst need different handling.

Amazon Connect’s documentation distinguishes forecasting contact volume and handle time, capacity planning and individual scheduling. Its time-zone documentation also distinguishes forecast/download time zones. Those product concepts inform the planning questions here; neither Amazon scheduling nor workforce automation is asserted as a Revo feature.

Use one explicit operating time zone and dates in your worksheet. Choose interval lengths that expose your observed peaks. The example uses four six-hour blocks only to illustrate the assignment ledger; split those blocks where your records show a peak, break, training session or change of owner. The grid is not a staffing calculation.

02 / A weekly coverage operating plan

Fill the coverage ledger and keep verification separate

The blank CSV contains headers only. The fictional example contains 28 rows for October 26–November 1, 2026 in America/Phoenix, using start-inclusive/end-exclusive hours from 0 to 24. It assigns example roles, never real employees or contact information. Four rows cover each calendar day; the hours add to 168 for that seven-day example, which does not claim the same total for every time zone or daylight-saving week.

Each row identifies the primary answerer, a backup, the unavailable-primary rule, an office-defined peak trigger and peak owner, an authorized urgent-escalation role, the routine-review time and owner, and verification evidence/status. The next routine-review time concerns office follow-up; it is not the time that calls begin to be answered. In this fictional policy, office reviews occur Monday–Friday at 08:00, 12:00 and 18:00. routine_review_at is the first such review at or after the end of the entire row interval, not the review following only its first call. Thus weekday 00–06 goes to 08:00 that same day; 06–12 goes to 12:00; 12–18 goes to 18:00; and overnight/weekend work waits until the next applicable review. Adjust that stated policy to your actual team before use.

Check that each day starts at 0, ends at 24 and has no overlap or gap. Then confirm the named roles correspond to contracted or scheduled coverage. Keep status planned_not_verified until an authorized test and evidence support a verified state. A filled cell alone does not prove someone will answer.

03 / A weekly coverage operating plan

Resolve a peak and an absence in the same interval

Worked planning example: Tuesday’s 12–18 block names the office as primary. A team training session from 13–14 means that label is insufficient. Split it into 12–13, 13–14 and 14–18. For 13–14, name the confirmed backup as primary, its separate fallback, the same business instruction version and the office person who will review resulting requests. Keep the original plan as a dated prior version.

Now suppose observed arrivals show a burst during 14–15. Split that interval again if needed. Define the trigger from the system you actually use, such as an agreed queue condition or unavailable primary, and identify who activates extra coverage and who returns the normal route. Do not assume software removes concurrent-call limits or that an on-call technician can simultaneously answer every overflow call.

If no backup is confirmed, mark that interval unresolved and do not describe the plan as reliable 24/7 coverage. Change the assignment or the public expectation before relying on it. This example concerns responsibility and switching, not employment-law advice or a prescribed shift pattern.

The revised-example CSV implements those Tuesday splits: 12–13, 13–14, 14–15 and 15–18 replace the original 12–18 row. It has 31 rows, still covering 168 hours without overlaps. The training interval names a replacement primary and a different secondary backup. All rows remain planned_not_verified; role acceptance and tests are still required. Each split row uses the first scheduled office review at or after its own end; the training and peak rows therefore point to Tuesday 18:00 in this example.

04 / A weekly coverage operating plan

Accept coverage at handoffs, not only during normal hours

Use consenting test callers in an approved window; this article reports no calls actually placed. Test just before and after a handoff, an unavailable primary, an unavailable escalation contact, and an office-defined peak condition through a provider-supported method. Record expected answerer, actual endpoint, business instruction version, result and evidence reference.

Have the next owner acknowledge the handoff and inspect the first pending request. Where a provider answers continuously, test the change in business instructions and recipients as well as the connection. Phone answering, acceptance by an on-call employee and the next routine office review are three different responsibilities.

Review the plan when demand or availability changes. Keep a version, effective date, decision owner and restoration instructions so a temporary absence route does not become permanent by accident. The worksheet is neutral; it does not implement routing, schedule employees or establish a Revo integration.