Merrill Lynch's Six VoIP Deployment Tips

Finance giant's director of 'private client' technology shares advice about rolling out voice over IP in your enterprise.

March 9, 2007

2 Min Read
NetworkComputing logo in a gray background | NetworkComputing

Roll out voice over IP across 250 offices and 10,000 VoIP nodes and you learn a thing or two about the technology. So when Alok Kapoor, managing director of Merrill Lynch, Global Private Client Technology talked about VoIP here at VoiceCon, he had some concrete advice for any implementer. Here are six of his deployment tips:

1. Have good metrics on the performance of legacy systems. Kapoor repeatedly emphasized that because he lacked that information it was difficult for his customers to assess which voice problems were attributable to the new VoIP system and which existed in the legacy environment.

2. Use productivity gains to solicit buy-in. Kapoor sold his users on the productivity gains that VoIP applications could deliver for his company. Key applications included click-to-dial, click-to-answer and screen pops in which the right customer information from Salesforce.com was displayed when a call is answered. Moving forward, he's looking at being able to maintain the context of a transferred call and provide click-to-dial on a number on any Web page.

3. Roll out applications early. Kapoor planned on stabilizing the VoIP environment before deploying computer-telephony integration applications. However, by deferring CTI applications, his project failed to deliver promised productivity gains right from the start. In retrospect, he says, he should have deployed the CTI applications earlier in the process, satisfying customer expectations earlier in the VoIP rollout.4. Factor in training costs. Kapoor and his team spent "countless hours" evaluating the usability of systems. Users helped assess all the products before deployment. Kapoor said he's instituted periodic usability surveys to identify new areas that should be explored. And even all that research hasn't been enough. Users will require retraining and IT had best be ready to provide it.

5. Know your wiring closet. It's amazing what you'll find, or won't find, in a wiring closet, Kapoor said. Dangling cables, limited space and insufficient backup power were some of things with which he had to deal. The shortcomings of existing facilities significantly complicated VoIP deployment.

6. Engage the business. For Kapoor, VoIP isn't about infrastructure. It's about improving customer service and enabling the business to improve its effectiveness. The only way to identify those needs--and determining how to address them--is by regularly working with the business in the design process to understand their requirements.


0

SUBSCRIBE TO OUR NEWSLETTER
Stay informed! Sign up to get expert advice and insight delivered direct to your inbox

You May Also Like


More Insights