In addition to making sure your internet service can handle your VoIP traffic, you also need to make sure your local area network (LAN) can handle it. What makes network management tricky with VoIP is that if you simply drop it onto your network, that traffic will get processed the same as any other traffic, meaning your shared accounting application or those 20 gigabytes worth of files your assistant just moved to the cloud.
The problem is maintaining control over your voice quality at so many different locations. Even if you've got several business-grade routers working in a bunch of branch offices, this problem is surmountable since (1) it's usually not overly difficult to provision those branch office routers remotely, and (2) the routers at those locations were chosen by your IT staff specifically because they work well with the routers at your primary location. That's not the case with home routers.

For those with voicemail greetings that get changed about as often as a new president is elected, know that this is doing a serious disservice to the caller-recipient relationship. It signals to callers that the business is anything but an authority, most likely not very detail oriented, and has questionable overall credibility and competency. Those aren’t traits that any business wants to
When was the last time you gave a thought to your business phone system? Perhaps the last time there was an outage? If your company's roots go deep, it's possible that you're sitting comfortably with a PBX system, thinking that if it's not broken, there's no need to fix it. There are an unfathomable number of choices for business phone systems right now. Do you want something that lives in the Cloud, or something that you can see in a closet? What are you starting with -- do you have an on-site PBX, landlines and heavy technical support, or is your company lean, mean, and completely comfortable relying on an internet service provider (ISP) with tools off-site?