News

Datamonitor prediction on speech and call centres rings true

Arif Mohamed

Research from analyst Datamonitor three years ago predicted that speech-enabled self-service technology will compete with offshore contact centre customer service agents.

Today, the analyst said its prediction came true as Lloyds TSB, the UK’s fifth largest bank, announced it is to close its contact centre in Mumbai, which typically handles overflow calls when UK agents are busy.

Lloyds TSB said the widespread use and success of its automated speech-enabled phone self-service system has eliminated the need for additional agent capacity in Mumbai.

Daniel Hong, lead analyst of voice business research at Datamonitor, said, “As we roll out the tape over the next several years, cost pressures and globalisation will undoubtedly continue to create strong tailwinds for offshoring.

"However, speech self-service will also proliferate and in many instances compete with offshoring as companies scramble to assemble the optimal blend of automation and agents for customer care.

However, he added that speech technology will not replace the need for offshore contact centres for a lot of companies.

Peter Ryan, senior analyst of contact centre outsourcing research at Datamonitor, added that Dell’s recent expansion into the Philippines is a sign that customer care from foreign locations is still a model that works.

Click for Datamonitor report

Related article: Somerfield's IT helpdesk moves to India

Related article: End-users see ignorance as biggest block to outsourcing

Related article: Credit Suisse considers massive switch to offshore

Comment on this article: computer.weekly@rbi.co.uk

 


Email Alerts

Register now to receive ComputerWeekly.com IT-related news, guides and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
 

COMMENTS powered by Disqus  //  Commenting policy