Before changing your business phone system, document what callers should experience: where incoming calls go, which team answers, how transfers should work and what happens when nobody is available. Include business hours, after-hours behavior and the person responsible for confirming each requirement.

Start with business decisions rather than configuration settings. Your team can describe the desired caller journey in plain language; your phone-system provider can then explain what is supported, what needs clarification and where a different approach may be necessary.

Note This worksheet describes desired behavior, not confirmed platform capabilities. Treat routing, transfer and messaging options as requirements to discuss—not promises that every system supports them.

Start with incoming numbers and their purpose

Use existing business records to identify the incoming numbers in scope. For each, record why people call it and whether callers expect a particular department, location or person. Keep actual numbers in a controlled internal document rather than publishing the completed worksheet.

For numbers serving the same team, ask stakeholders: Should these calls reach the same initial destination? Should callers hear the same closed-hours message? Record the agreed requirements separately wherever the answers differ.

Define the initial destination and answering responsibility

Describe what should happen when a call arrives during normal business hours. Should a person answer directly, should a team receive the call, or should callers hear choices before reaching someone? Record the intended experience without deciding which technical feature will deliver it.

  • Initial destination: Identify the role, team or caller choice that should receive the call.
  • Answering responsibility: Identify the team expected to answer, not simply the desk where a phone happens to sit.
  • Coverage responsibility: Clarify who should cover calls during breaks, meetings or staff absences.
  • Caller instructions: Describe what callers need to know before choosing a destination, if choices are wanted.

Distinguish the team answering calls from the person approving the requirement. The answering team can explain daily needs, while a business stakeholder may need to resolve competing expectations about coverage.

Describe transfers and unanswered calls together

For each desired transfer destination, ask: Do staff need to speak with the recipient before connecting the caller, or should they send the call directly? Are transfers needed between departments or locations? Record the answers as requirements for the provider to confirm.

Then describe what should happen if the recipient is busy or does not answer. Should the caller reach another team, return to someone who can help or leave a message? Avoid vague instructions such as “send to backup” unless the backup destination and its responsibility are defined.

  • For an unanswered incoming call, record the desired next destination and the point at which the caller should move there. Leave timing undecided if stakeholders have not agreed.
  • For an unsuccessful transfer, record who should retain responsibility for helping the caller.
  • For messages, identify the responsible role or team, who should have access and who is expected to follow up.

Make business hours and exceptions explicit

Record the days, opening and closing times, and applicable time zone for each call purpose. Where departments or sites keep different hours, describe those differences rather than applying a single office schedule to every destination.

Separate a closed office from an unanswered call during open hours. Decide what callers should hear after closing, whether they should be able to leave a message and which team is responsible for those messages. Do not imply that someone is monitoring calls after hours unless that responsibility has been confirmed.

List exceptions that need a decision, including holidays, temporary closures and department-specific schedules. Identify who approves exceptions and who can request future schedule or message changes. Exact wording can remain pending, but the intended message and its owner should be clear.

Reusable call-handling requirements worksheet

Copy this blank worksheet for each incoming number or distinct call purpose. Complete it in an access-controlled working document. Use business roles where possible; do not include private customer details or personal employee contact information.

  • Incoming number or internal reference: ______; business purpose and relevant department or site: ______
  • Current behavior, as reported or documented: ______; source and details needing confirmation: ______
  • Desired initial destination during open hours: ______; caller choices or instructions, if needed: ______
  • Team responsible for answering: ______; coverage during staff unavailability: ______
  • Transfer destinations and needs: ______; recipient consultation before connecting, if needed: ______
  • Busy or unanswered-call behavior: ______; desired transition timing to confirm: ______
  • Unsuccessful-transfer behavior: ______; role responsible for helping the caller next: ______
  • Message destination: ______; access and follow-up responsibility: ______
  • Business days, opening and closing times, and time zone: ______; after-hours behavior and message purpose: ______
  • Holiday or temporary-closure exceptions: ______; exception approver and change-request role: ______
  • Unresolved decisions: ______; decision owner: ______; provider feasibility questions: ______
  • Person responsible for confirming this requirement: ______; confirmation status: ______

Keep current behavior separate from desired behavior

Do not treat the existing setup as automatic approval for the replacement. Ask stakeholders to label what should stay, what should change and what remains undecided. If staff describe current behavior differently, preserve the disagreement as a question rather than choosing an account without confirmation.

Before the provider discussion, have the answering teams and responsible business stakeholders confirm their parts of the worksheet. Give unresolved decisions an owner. This lets the provider distinguish approved business needs from assumptions and questions about feasibility.

Use the worksheet for the requirements conversation

Requirements gathering defines the intended caller experience. It is separate from troubleshooting a fault or planning the system change itself. For the later implementation stage, see the business phone system cutover checklist.

Accutech Communications installs, services and repairs business phone systems for companies in Massachusetts, New Hampshire and Rhode Island. Learn about its business phone system services, or request an estimate for your phone-system project. Use your worksheet to explain the desired call handling and highlight decisions that still need discussion.