Choosing a business phone system for a service company

What a service company needs from its phones

A home service phone system is not an office phone system. Calls arrive in bursts when the weather turns, half your team is in vans, emergencies come in at night, and a missed call is often a lost job rather than a delayed one. The system has to ring the right people, never ring forever, and send calls somewhere useful when nobody can answer.

Most companies now choose a cloud phone system (VoIP), which runs over the internet and includes apps for mobiles and computers. The choice between providers comes down to how well each handles your call flow, your texting and your software, and how easy it is for an office manager to change rules without calling support.

The selection checklist

Ring groups and overflow

A ring group is a set of phones that ring together or in order. A queue holds callers while they wait for the next free person. Most service companies need one group for booking, one for dispatch and sometimes one for billing or sales. The rules that matter are what happens when nobody picks up.

1. 01

   Ring the first group briefly

   Ring all available CSRs at once for about 20 seconds. Simultaneous ringing answers faster than ringing one person at a time.

2. 02

   Overflow to a second group

   If no CSR answers, ring dispatchers or the office manager next.

3. 03

   Offer a choice, not a dead end

   After a short wait, give the caller an option: hold, request a callback or press a key for an emergency.

4. 04

   Send unanswered calls somewhere live

   At the end of the chain, route to an answering service or call-handling service, never to an overflowing voicemail box.

5. 05

   Report on the overflow

   Review how often calls reached each step. Frequent overflow at the same hours means a staffing problem, not a phone problem.

If you run several trades or locations, our guide to call routing for multi-trade companies goes further on routing by trade, ZIP code and caller history.

Caller ID and outbound calls

Your phone system also makes calls: callbacks, confirmations and estimate follow-ups. Those calls go unanswered more often than most owners realize. Only 19% of US adults say they generally answer calls from unknown numbers, while 80% don't^[1].

Wariness is part of it: 91% of adults think people often or sometimes pretend to be someone else by phone or online to steal personal information^[3]. Set the outbound caller ID to the number customers already know, register your business name for caller ID display where your provider supports it, and text before you call. Never let staff call customers from personal mobiles with the caller ID hidden.

Recording calls

Recording is worth turning on for booking and dispatch lines, for coaching and for resolving disputes. Federal law allows recording when one party to the call has given prior consent^[4], but some states, including Florida, permit it only when all parties have consented^[2]. Because you can't always know where the caller is, a short notice at the start of recorded calls is the common approach. Check that your system can play notices per number and set how long recordings are kept. This is general information, not legal advice.

Business texting

Customers text the number on your truck, invoice and website whether you planned for it or not. A phone system that can send and receive texts on your main and tracking numbers, in a shared inbox, keeps those messages from disappearing.

• Shared inbox with assignment, so two CSRs don't answer the same text.
• Templates for confirmations and on-my-way messages.
• Opt-out handling built in.
• Carrier registration support for business texting, which most providers now require before you send at volume.

Mobile apps for the field

Your techs, managers and on-call staff already carry smartphones; 91% of US adults do^[5]. A good mobile app lets them make and take business calls with the company caller ID, see call history and transfer a call back to the office. Test the app on a weak cellular signal, because that is where your techs will use it.

Integration with field service software

The best time saver is a screen pop: when a known customer calls, their record opens with past jobs, equipment and open invoices. Ask which field service and CRM systems the phone provider integrates with, what data passes in each direction, and whether call recordings attach to the customer record. If you also use a separate call tracking platform, check how the two fit together; our call tracking software comparison explains what to ask.

Reliability and backup

A cloud phone system is only as reliable as the internet connection in your office and the provider's own network. For a company whose phones are its order book, plan for failure.

• Use a business-grade internet connection in the office, and add a second connection from a different provider or a cellular backup router.
• Set an automatic rule: if the office desk phones go offline, calls ring the mobile apps of the CSRs and the manager instead.
• Ask the provider where its data centers are, how it handles regional outages and how it tells customers about incidents.
• Keep a printed sheet of how to switch routing from a mobile phone, so the office manager can move calls during a power cut.
• Test the backup twice a year by unplugging the office router during a quiet hour and calling in.

Storms are when calls spike and when power and internet fail. The phone setup that works on a calm Tuesday must also work on that day.

Contracts, support and admin

Read the contract as carefully as the feature list. Check the term length, what happens at renewal, and whether the price can rise during the term. Ask whether you can add and remove users month to month as seasonal staff come and go. Find out who can change call flows: if every routing change needs a support ticket, your office manager will stop adjusting the system to the season. Ask for the support hours and channels in writing, and whether they include evenings and weekends, because a forwarding fault on a Saturday night during a freeze cannot wait until Monday.

Example: a call flow for a ten-person company

Example: a fictional electrical contractor with two CSRs, one dispatcher, six electricians and an owner sets up this flow. Weekdays 7 am to 6 pm, calls ring both CSRs for 20 seconds, then the dispatcher and owner for 15 seconds, then a callback option. After hours, a short greeting offers an emergency key that rings the on-call electrician's app, with the backup electrician after 30 seconds. All other after-hours calls go to an answering service that books routine visits and texts a summary. Every morning the office reviews missed and overflowed calls from the night before.

Porting and cutover

1. 01

   Gather your numbers

   List every number you use, including tracking numbers and fax lines, with the account details from the current provider.

2. 02

   Build the new call flow first

   Set up users, groups, schedules and greetings on temporary numbers and test them.

3. 03

   Request the port

   Submit the port with the exact account name and address on the old bill to avoid rejections.

4. 04

   Schedule the cutover

   Choose a quiet day and time. Keep the old service active until the port completes.

5. 05

   Test every path

   Call each number from outside, during and after hours, and check recording, texting and the on-call route.

Once the system is live, measure it. Answer rate, abandoned calls and time to answer belong on your CSR scorecard. Pair the phones with clear dispatch tools, as covered in our guide to moving from whiteboard to digital dispatch, and use call tracking numbers to see which marketing makes the phones ring.