Rules
Part of Making sense of VoIP systems: live or die on the network path
VoIP Systems Features for Small Businesses
VoIP systems features shape caller routing, reporting, compliance, and administration. See which settings affect callers and what to review before buying.
VoIP systems features often appear in long lists because software makes them easy to add. Only a few of them change anything a caller notices, and a slightly different few change what you know about your own business.
This page sorts the list into those two piles and one more.
What to take away
- Routing features decide what a caller experiences. Get the out-of-hours path and the queue behavior right and most complaints disappear.
- Reporting features decide what you can see. Unanswered calls are the number most businesses never look at and should.
- Anything that records or transcribes a conversation is a legal decision before it is a feature.
Routing: what the caller experiences
Hunt groups and queues. A hunt group rings several phones in an order. A queue holds callers and answers them in turn. They are different products for different problems: a hunt group is for coverage, a queue is for volume. Using a hunt group where you need a queue produces callers who ring out during a busy period and quietly go elsewhere.
Prove out-of-hours routing fires
- Build the schedule
- Call in from outside at 7pm
- Call again on a public holiday
- Confirm what actually happens
- Fix before a customer complains
Out-of-hours and holiday routing. The single highest-value setting on any phone system, because it runs unsupervised. Building the schedule and proving it fires belongs with voip systems setup. Build it, then call in from outside at seven in the evening and again on a public holiday to confirm what happens. Almost nobody tests this until a customer complains.
Time-of-day and overflow rules. Where a call goes after ringing for a set period. The default is often voicemail. For many businesses a better default is a mobile.
Presentation number. The number the recipient of your outbound call sees. Set it per team. A call from an office nobody staffs after four should return to a queue, not to that office.
Reporting: what you learn
| Report | The question it answers | Why it earns its place |
|---|---|---|
| Unanswered inbound calls | How much demand you never met | It is usually larger than anyone guesses |
| Time to answer, by hour | When to move people | It turns staffing into a measurement |
| Calls by number dialed | Which advertised number produced the call | This is the only honest way to attribute a phone lead |
| Abandonment in a queue | Where your hold time crosses a caller's patience | It gives the queue a target |
The third row is why several published numbers are worth having.
Four reports worth running
- Unanswered inbound callsdemand you never met
- Time to answer by hourwhen to move people
- Calls by number dialedattribute the phone lead
- Abandonment in a queuewhere patience crosses
Features that come with obligations
Call recording. In the United States, the federal Wiretap Act (18 U.S.C. §§ 2510–2523) and state call-recording statutes govern whether you may record and what notice or consent is required; some states require all-party consent. Check the laws for every state where a participant may be located, and set retention to meet applicable requirements and your business policy. Make sure the archive is covered by whatever protects the rest of your data. This is not a setting; it is a policy with a setting attached.
Transcription and automated summaries. Same questions, plus a third: the audio and the text usually leave your building to be processed. Ask where, and by whom, and whether that is compatible with what you told the caller. If the material includes protected health information, HIPAA may apply; California privacy requirements under the CCPA, as amended by the CPRA, may also apply depending on your business and the data.
Voicemail to email. Convenient, and it moves recordings of your customers into a mailbox that may be less protected than the phone system, which is the kind of gap voip systems security works through. Guidance from the Cybersecurity and Infrastructure Security Agency (CISA) on multifactor authentication is relevant to that mailbox more than to the phone system.
Features that mostly matter to whoever administers it
Bulk changes, templated handset settings, and an export of the configuration.
These sound dull and they decide whether a small change takes five minutes or an afternoon. Ask to see the administration screen before you buy, and ask whether the configuration can be exported. An export is what lets you rebuild elsewhere if the provider fails.
Examples of US business VoIP providers include RingCentral, Nextiva, Ooma, and Dialpad; this is not a ranking, and feature availability varies by plan. When evaluating a system, ask to see an auto attendant, call forwarding, a mobile app, and CRM integration, and confirm support for number porting and a written service-level agreement (SLA) or uptime commitment in the quoted plan. Request the itemized price for the plan and add-ons and the expected installation date in writing; both vary by provider and order. For emergency calling, verify 911 access and dispatchable location under FCC requirements, including Kari's Law and the RAY BAUM'S Act, and confirm what applies to your system.
The FCC's guide to stopping unwanted robocalls and texts is worth reading before you enable anything that dials automatically, because the rules that protect you as a recipient also constrain you as a caller.
Common questions
Do we need an interactive menu?
Only if you have enough call volume that a person cannot triage it. A menu in front of three people adds delay and removes the thing small businesses are better at.
How long should a queue hold someone?
Shorter than you think, with an honest position or an offer of a callback. Measure abandonment and set the limit from the data rather than from taste.
Are software phones as good as handsets?
For quality, they depend on the computer, the headset and the network path more than on the software, and the path is the part voip systems is mostly about. For reliability, a handset has fewer things to go wrong. Mixed fleets are normal.
Can we keep a feature the old system had?
Ask specifically, with the behavior described rather than the name. Feature names differ between systems and the behavior is what your staff will miss.
