Skip to content
Lines open
Map my coverage

Call operations

Build a lunch-hour call coverage plan for a two-person office

A practical lunch coverage plan for a two-person phone team, with staggered breaks, a named queue owner, and a rule for calls that cannot wait.

Build a lunch-hour call coverage plan for a two-person office
Table of contents

Lunch is the most predictable coverage gap in a small phone team, and it is often the least planned. Two agents leave within twenty minutes of each other, the queue backs up, and the first caller after noon hears an apology. A lunch plan does not need a scheduling system. It needs a named order, a fixed handoff, and a rule for the calls that cannot wait.

Key takeaways

  • Stagger breaks by call volume rather than by personal preference.
  • Name one agent as the queue owner during each break.
  • Write a short list of calls that must not wait for lunch to end.
  • Keep the handoff to one page that both agents can see.
  • Compare the first week of the plan with the call records.

Stagger the break by call volume, not by habit

Pull two weeks of call arrival data before choosing a lunch order. Most small offices see a narrow peak around noon, and the plan should keep at least one agent available during that peak. If the data is thin, ask the agents which hour produces the most urgent calls. A break schedule built on habit often leaves the busiest half hour uncovered.

Stagger the starts by at least thirty minutes. One agent leaves at eleven thirty and returns at twelve thirty, while the second leaves at twelve thirty and returns at one thirty. That overlap keeps a live person on the line through the whole lunch window. Write the schedule where both agents can see it, not in a private calendar.

Name who owns the queue during each break

Every break needs one named owner for the phone. The owner answers live calls, checks the shared inbox, and decides when a request needs a callback. The agent on break should not be expected to watch the queue from a phone. A named owner removes the ambiguity that causes a call to ring twice and then stop.

Put the owner's name on a small board beside the phone and update it at each change. If the owner steps away for a minute, the other agent becomes the owner by default. The rule should be simple enough to follow without asking a manager. The queue is never ownerless during business hours.

Set a rule for calls that cannot wait

Write a short list of call types that must reach a person during lunch. A safety issue, an active service outage, a same-day appointment change, and a caller with a hard deadline usually belong on that list. Everything else can receive a callback with a clear time. The list should use plain examples rather than abstract categories.

Give the agent a script for the calls that can wait. "I can have someone call you back by two o'clock, and I am noting the best number to reach you" is enough for most routine requests. Record the promise in the same place the afternoon agent will look. A caller who hears a specific time is less likely to call again during the break.

Keep the handoff to one page

The handoff page should show the break times, the queue owner, the open callbacks, and the urgent list. Add a line for anything that changed since the morning, such as a delivery delay or a closed office. Keep the page to one side of paper or one screen. A long document will not be read during a busy lunch hour.

Use the same page every day so the fields become familiar. The outgoing agent fills in the open items before leaving, and the incoming agent initials the page on return. A simple initial is enough to show that the handoff happened. The page then becomes the record for the next review.

Measure the gap after the first week

Compare the first week of the plan with the call records from the week before. Look at the longest wait, the number of abandoned calls, and the number of callbacks promised for after lunch. A drop in abandoned calls suggests the plan is working. A rise in callbacks may mean the urgent list is too narrow.

Ask both agents what the plan missed. They will know which call type broke the schedule and which handoff detail was missing. Change one item at a time so the effect is visible. A plan that changes every day cannot be evaluated.

Adjust the plan when the team changes

Revisit the lunch order when a new agent joins or someone changes their hours. A two-person plan depends on both people being present, so an absence needs a backup line. Name the person who covers the queue if one agent is out. That person may be a manager or an agent from another team.

Review the plan at the start of each month and after any holiday. Call volumes shift with the season, and a schedule that worked in summer may fail in December. Keep the urgent list and the handoff page in the same file as the phone script. The business hours coverage plan gives the wider frame for holidays and exceptions.

A lunch plan is a small promise to the caller that the phone will be answered. It also protects the agents from choosing between food and the queue. The best plan is short, visible, and tested against real call records. Start with two weeks of data and one named owner.

Sources

Map the first queue

GIVE MISSED CALLS A WAY BACK IN.

Share your call types, hours, tools, and escalation rules. We will turn them into a practical coverage plan with a clear first week.

Book a free consultation ↗See the call lanes