Before spring 2020, many organizations didn’t let people work from home for one reason: security.

Sure, business leaders also may have had concerns about potential issues with productivity and collaboration if people weren’t in an office. But perhaps more than anything, there was concern about the heightened possibility of critical data breaches.

The coronavirus pandemic, of course, left many companies with few, if any, other options. In March, managers were forced to send employees home to comply with regional lockdowns and protect the safety of their workers. For the most part, organizations have been pleasantly surprised with the ability of their employees to work productively outside the office. And, with a few exceptions, organizations are also largely finding that their technology tools are up to the task of keeping their environments secure.

In particular, Cisco Systems has gone to great lengths to make enterprise security a key component of the popular collaboration platform Webex. Here are some important features to be aware of that are helping keep organizations safe.

If you haven’t moved some portion of your collaboration needs to the cloud yet, you are likely thinking about it. While on-premises communications platforms had been popular for the past several decades, “the times they are a-changin.” Almost every customer I talk to is planning a move to the cloud for at least some portion of their communications strategy. Most are doing it to get out of the server management business, while others are more focused on the continued advancements that cloud brings.

Luckily, I have had the opportunity to focus on the Unified Communications as a Service (UCaaS) market for the past couple years and have witnessed the growth of some of our closest partners here at CDW. Over the past couple months, I’ve worked to get our Avaya Cloud Office (ACO) services off the ground, and I thought I would share some of what I learned through that process, as much of what I saw will be compelling to many of our customers.

A customer of mine, a tech company, receives relatively few customer calls overnight — usually just a couple dozen. Currently, the employees fielding those calls are all working from home, separated from one another, and it wasn’t until the end of a recent shift that all of them realized that no one had received a single call. The company’s telephone line was out, but no one knew it for about eight hours.

This happens far too often: Companies experience problems with their collaboration systems, but don’t catch them for hours or even days. Synthetic testing — in which a tool simulates user traffic to proactively detect and resolve outages or performance issues — is an effective solution to this problem. Through synthetic testing of collaboration systems, a partner such as CDW can automatically test the phone systems several times an hour to ensure that they are working as expected and record the entire customer experience.

Here are three scenarios where synthetic testing can add value to your collaboration systems.

Big changes are upon us when it comes to Cisco licensing. On Jan. 23, 2021, everything changes with Cisco Unified Communications Manager licenses. For some organizations, this will be a moment to celebrate, given the detailed complexity of Cisco’s reporting. Who hasn’t struggled at times to figure out what your organization owns, what’s covered and whether or not that’s reflected in the Cisco report?

You can say goodbye to perpetual license purchases and multiyear support contract renewals. No more deciphering what type of license you need based on the phone model you plan to buy. No more reviewing your Prime License Manager to see if you even need licenses. No more wading through the PLM output. Cisco has finally simplified its license consumption model.

Take a look under the hood of many companies’ collaboration environments today, and you’ll find what I call “organized chaos.” Employees are using collaboration tools to get things done, but they’re frequently toggling between different applications to message colleagues, manage calendars, share documents and initiate video meetings.

Many organizations support different collaboration tools across departments. This might make sense if, say, an engineering team benefits from a different collaboration workflow than what other business units use. However, collaboration environments are often not the result of strategic decisions, but rather an ad hoc approach when deploying technology tools.

In many cases, business units adopt a given collaboration solution simply because it’s one that employees are already familiar with. As a result, companies miss out on the benefits that come from adopting the tools that are best suited to helping them meet their business goals.

When I begin working with an organization on its collaboration efforts, I often find that the company already supports a number of tools. Some have different solutions for different functions, such as calling, messaging, file sharing and video meetings. And others run multiple platforms that essentially do the same things.

It’s sometimes necessary, of course, for organizations to adopt and support multiple collaboration solutions. But there really can be such a thing as too much when it comes to these tools. It’s not just that the cost of purchasing and supporting more solutions will naturally be higher than the cost of purchasing and supporting fewer platforms. There’s also the danger of employees becoming confused about the differences among the various tools — and, therefore, using them less (or less effectively).

An unwieldly, sprawling collaboration environment can lead to an organization paying more for less productivity. Here are some steps we take to help business and IT leaders find the right mix of collaboration tools for their organizations.