Requirements before providers
Phone-system requirements for a small plumbing outfit
Start with the calls, people, schedules, and failure paths the outfit must support. Replacing a phone system can improve the workflow, but it can also put the business number, routing, texts, and customer access at risk if the requirements are unclear.
No vendor rankings. No assumption you need a full VoIP platform. No reason to switch before the requirements are clear.
The short answer
Choose the smallest reliable setup that runs the workflow
The right phone setup is not the one with the longest feature list. It is the smallest system the team can operate consistently, including when a person, device, connection, or provider does not behave as planned.
- Keeps the business number under the outfit’s control
- Gets calls to the right person or clearly owned queue
- Preserves missed-call follow-up
- Supports only the communication channels the outfit genuinely uses
- Has a workable failure and rollback path
Do you even need to switch?
Test the current process before replacing it
Your existing mobile line plus a simple routing/text-back process may already be enough. The answer depends on whether that setup reliably performs the work the outfit actually needs—not on a universal call-volume threshold.
The current setup may be enough when
A small number of people can reliably own the phone
- Call volume is manageable with the people already responsible for the phone.
- One or two people reliably answer calls or return them through a clearly owned process.
- Voicemail or missed-call text-back covers the short gaps the outfit actually experiences.
- After-hours service is limited, clearly defined, or not offered.
- Calls do not require complex routing, queues, or rotating destinations.
- Ownership of the current number and access to the account are clear.
- The call and message records the outfit genuinely needs are available.
A fuller system may deserve evaluation when
The workflow now needs coordination, visibility, or control
- New calls need simultaneous ringing, sequential routing, or a real queue.
- Several people must answer and return calls from the same business identity.
- On-call routing changes by day, time, or schedule.
- Customer text threads need shared ownership instead of living on one person’s phone.
- Missed calls, voicemails, or replies regularly fall through the cracks.
- The owner needs central visibility into call and follow-up activity.
- A defined workflow genuinely depends on an integration or recording capability.
- Growth is making the personal-phone process unreliable or difficult to administer.
One-page requirements worksheet
Write the operating requirement before comparing systems
Mark each item required, optional, or not needed. Add the outfit’s exact answer beside it in a working copy. A candidate system passes only when the team can show how it supports the written workflow.
Number ownership and portability
Keep the main business number under the outfit’s control before, during, and after a change.
- Who legally or administratively controls the main number?
- Can the number be ported out later?
- What account information will be required to port it?
- Will the outfit use a temporary number during migration?
- What happens to the old service while the number moves?
- Can number ownership be verified before signing?
Inbound routing
Write what should happen to a call, in order, rather than naming a feature.
- Do any people or devices need to ring simultaneously?
- Should any destinations ring sequentially?
- What is the exact office-hours route?
- What is the exact after-hours route?
- How does the on-call destination change?
- Where do overflow calls go?
- When does voicemail become the fallback?
- What does the caller experience when nobody answers?
Outbound caller identity
Customers should see a consistent business identity without exposing personal numbers unnecessarily.
- Which business number should appear on customer calls?
- Can technicians call from personal devices without revealing personal numbers?
- Will caller ID stay consistent across users and devices?
- Does outbound identity depend on an app or a specific carrier setup?
Missed-call recovery
Define how an unanswered call becomes visible, owned, and resolved.
- Who receives missed-call alerts?
- Who owns the voicemail queue?
- Is immediate text-back genuinely needed?
- Does the outfit need one shared follow-up queue?
- How is each follow-up assigned to a person?
- Can everyone see whether somebody already responded?
SMS and customer texting
Specify the real shared-texting workflow and what happens when access changes.
- Does the outfit need shared business texting?
- Must the main number support two-way SMS?
- Which users need to see the same thread?
- Are attachments or MMS genuinely required?
- What happens to conversations when an employee leaves?
- What number eligibility or registration requirements apply to this setup?
After-hours and on-call
Make the written after-hours policy possible to operate, including when the first route fails.
- Does routing change automatically by schedule?
- Who is the primary destination and who is the backup?
- Can an authorized person apply a manual override?
- Can the workflow support the outfit’s urgent-call policy?
- What happens when the on-call person does not answer?
Call recording
Treat recording as a governed business requirement, not a default checkbox.
- Does the outfit have a specific reason to record calls?
- Who should be able to access recordings?
- How long should recordings be retained, and how are they deleted?
- How will applicable consent and legal requirements be handled?
Administration and ownership
Keep the account recoverable and under current business control.
- Who owns the primary administrator account?
- Who is the backup administrator?
- Which business-controlled recovery email and phone are used?
- What is the employee onboarding process?
- What is the immediate offboarding process?
- Which roles and permissions does each person receive?
- Who controls billing and contract records?
Reliability and failure handling
Assume that connections, apps, devices, or the service itself can fail.
- What happens during an internet outage?
- What happens during a power outage?
- What happens when mobile data is unavailable?
- What happens during a provider outage?
- What happens when the calling app fails or a user is logged out?
- Can calls fall back to forwarding?
- What backup number or manual process is available?
- How does the outfit learn that something failed?
Integrations
List only systems the call workflow actually needs; an available integration is not proof of workflow fit.
- Is calendar access required for the defined workflow?
- Does customer context need to reach a CRM?
- Must calls connect to field-service software?
- Is contact synchronization necessary?
- Is call tracking required and, if so, for what decision?
- Are automations or webhooks already part of a real process?
K
Total monthly cost
Look beyond the advertised per-user price. Record zero when an item truly does not apply; leave it unknown when pricing has not been verified.
| Cost category | Monthly amount | One-time, term, or cancellation notes |
|---|---|---|
| Base service | Blank | Blank |
| Users or seats | Blank | Blank |
| Phone numbers | Blank | Blank |
| Usage or minutes, if applicable | Blank | Blank |
| SMS or MMS | Blank | Blank |
| Toll-free usage, if applicable | Blank | Blank |
| Call recording or storage | Blank | Blank |
| Integrations or add-ons | Blank | Blank |
| AI or answering features | Blank | Blank |
| Setup or onboarding | Blank | Blank |
| Taxes and fees, where applicable | Blank | Blank |
| Hardware, headsets, or desk phones | Blank | Blank |
| Porting or migration | Blank | Blank |
| Contract or cancellation exposure | Blank | Blank |
| Estimated totals | Blank | Blank |
Migration and number portability
Do not make the business number the experiment
Port timing and procedures can differ. Build a controlled change plan around the outfit’s number and tested call paths instead of assuming every service moves them the same way.
- 01
Document ownership
Record the current number, account holder, authorized users, account identifiers, and recovery details.
- 02
Preserve what matters
Export or save contacts, greetings, routing rules, and critical logs when the current system makes them available.
- 03
Define target routing
Write the new office-hours, after-hours, overflow, voicemail, and no-answer behavior before migration begins.
- 04
Confirm both sides
Ask the current and proposed services what information they require, without assuming their processes or timing are identical.
- 05
Keep old service active
Do not cancel the existing service until the number move is confirmed and the new path has been tested.
- 06
Test calls and texts externally
Use devices outside the new system to test inbound calls, outbound calls, and SMS that the outfit relies on.
- 07
Test voicemail and no-answer
Let calls time out on purpose and verify the caller experience, notification, ownership, and follow-up record.
- 08
Test after-hours routing
Run the real closed-hours route through primary, backup, and failure behavior.
- 09
Verify caller identity
Confirm the expected business number appears when each authorized person calls a customer.
- 10
Keep a fallback
Maintain a documented rollback or forwarding process until the new setup is proven in normal operation.
Failure testing
Test the workflow, not the settings screen
Use outside phones and real user accounts. Observe what the caller experiences, who is notified, what record is created, and who owns the next action.
- 01
The owner does not answer.
- 02
The office person is already on another call.
- 03
A technician needs to return a customer call.
- 04
The after-hours primary does not answer.
- 05
The after-hours backup also does not answer.
- 06
The internet connection is down.
- 07
A mobile device has no data connection.
- 08
An app user is logged out.
- 09
A customer sends a text instead of calling.
- 10
A former employee’s access has been removed.
- 11
An inbound caller leaves voicemail.
- 12
A spam call arrives or one caller rings repeatedly.
- 13
A caller asks for a person who is unavailable.
Requirements before features
Replace vague labels with observable behavior
The examples below show the level of specificity to aim for. They are not universal configurations; timing, destinations, and policies should match the outfit.
“Needs auto attendant.”
“During business hours, new inbound calls should ring the office person and owner simultaneously for 20 seconds, then enter a named callback queue.”
“Needs texting.”
“The office person and owner must both see and reply to the same customer text thread without exposing personal numbers.”
“Needs after-hours routing.”
“Between 5 PM and 8 AM, calls should follow the outfit’s written after-hours policy, with a primary destination, backup, and honest failure message.”
Decision framework
Buy only when the requirement calls for it
Match the response to the gap the outfit has documented. More software is not the default outcome.
Keep current setup
The existing line and process reliably handle the required workflow, ownership is clear, and failure behavior is acceptable.
Document it, test it, and review it again when the operation changes.Add a small fix
The core line works, but forwarding, voicemail discipline, text-back, or shared follow-up ownership would close a specific gap.
Change the smallest part that solves the observed problem, then test it.Evaluate a business phone system
Routing, shared identity, administration, logs, texting, or reliability now require one coordinated system.
Compare candidates against the written worksheet and migration plan.