Use BroadSoft-approved phones. In the past we have been partial to Polycom, but more manufactures are now working with BroadSoft. The VoIP provider typically dictates what works and what doesn’t when it comes to equipment. Moreover, it is best to find out what makes and models they will support. Just because it can connect BroadSoft does not mean the provider is prepared to support it.

Remember, BroadSoft can be deployed in both a public Internet connectivity and a private connectivity (MPLS, private line) model.

Multi-location companies will typically favor routing voice over private connection with Class of Service (CoS) and Quality of Service (QoS).

We lead with a design for automatic failover in the event of a circuit outage. Typically, this is a failover from a private connection to a lower-cost public connection. This also gives physical redundancy because they are typically two different types of connections from two different providers, which may even have two different entrances into the building.

Large organizations may consider hot sparing (local storage of replacement equipment) of critical equipment.

Most companies start out with similar features and functionality as their old phone systems, but a scheduled review of design and available features to address business needs is crucial to maximizing the value. We redesigned our voice communications from the ground up three times in eight years without having to change our provider and without additional cost.

There truly are some great and powerful features with Skype for Business. My strong caution at this time is that if you (or your customer) are unwilling to innovate and transform how you communicate, you will probably struggle with Skype for Business. You need to (and eventually will) get used to the presence status showing up in other applications.

There should be a quality technical team inside the company, or it should have a strong provider on call. As with any solid computing environment, we can’t stress enough the need for standards. You don’t want to be chasing ghosts caused by uniqueness with individual users. Standardize everything you reasonably can.

The growth both in deployment and features is making it hard for Microsoft to focus on PSTN connectivity for Skype for Business. There are Microsoft Partners that have stepped up, and are consulting on, VoIP readiness assessments, managing the PSTN voice connectivity and supporting both Office 365 and on-premises customers.

Schedule time with any prospective provider to review features and configurations prior to making a decision. Ask questions. Think out of the box.

Come up with a game plan and then schedule a review for a week or two AFTER implementation. Gauge employees’ responses. Schedule more training if needed. Find out what is working well and what may not be meeting expectations. Reconfigure items if needed.

Remember that mobile employees may well decide they no longer need desk phones, so be prepared with a standard headset, preferably one that can be used either over the ear or over the head.