Sign up for this newsletter now!
Delves into the issues vital to network managers who support branch offices and remote workers.
- Share/Email
- Tweet This
- Print
Of the dozen or so triggers that cause companies to implement VoIP, branch-office communications is high on the list. IT leaders
recognize the number of remote workers and the number of branch locations continues to rise — and having dozens of un-interoperable
PBXs at these sites doesn’t do anything to unite the company.
Without a cohesive phone system, employees work on islands with rudimentary phones that don’t distinguish between a call made
within the company vs. outside. They cannot do abbreviated dialing, transfer calls, intercom, or view more advanced features,
such as presence data or directories.
Recognizing this does affect employee productivity, many IT decision-makers decide VoIP is the right way to streamline their
communications among branch-office employees talking to one another or to those at headquarters.
But what they often overlook is how they plan to monitor and manage the communications capabilities at the branch. On average,
only 18% of branch locations have IT personnel working there, leaving 82% of branch offices without on-site IT expertise.
The majority of companies implements VoIP and counts on the tools that come with their PBXs — perhaps combined with some existing
network management and manager of manager tools — to do the job.
What we have found, however, is companies that buy specialty IP telephony management tools — such as those from Infovista,
Integrated Research (better know by its product name, Prognosis), Fluke Networks, NetIQ, NetQOS, and several others — spend
less per employee to operate their VoIP system than those who rely on PBX or no tools at all.
Robin Gareiss is executive vice president and senior founding partner of Nemertes Research. Click here for the newsletter archive.
Comment