Local language voice support is expensive. Different providers offer different degrees of coverage. Some claim to provide support in 120+ languages for instance. But is this really real? What is the coverage split by product mix and technical expertise / experience level? How does this vary by time of day and time zone? Quoting a banner headline number doesn’t really tell anyone anything. It is misleading and can be undermined by competitors picking holes in local market scenarios very very easily.
Some providers don’t claim overly inflated language coverage numbers. In fact, some would undoubtedly claim (if they ever went on record for such things) to offer a number significantly lower than 120 during working hours and a lower number still out of hours (the exact number being defined by the inbound customer’s product group / technical discipline requirement and shift patterns (i.e. the multi language skills of the agents on duty that night). But the difference is that these providers have a bullet proof process behind their statements and have made significant investments to actually make it work in practice. They augment their out of hours coverage reduction with the use of machine translation for chat sessions if customers want to go down this route. I.e. A Swedish customer calling the local Swedish support number at 9pm in Stockholm will be told (by a very polite IVR system using perfect native Swedish phrasing) that he/she can speak to someone now in either English, French, or German (i.e. a context specific subset of today’s available out of hours languages that are most relevant to the caller e.g. a southern European caller may only be offered English or Spanish instead). If they don’t want to do this they can opt for an online chat session with a non-native Swedish speaker using real time machine translation into Swedish. Or if they prefer they can request a call back at a time of their choosing when the staff Swedish speakers are on shift.
An alternative high end solution is the potential to use a contracted real time translation bureau to have an interpreter on the line as the call is being conducted – This is obviously not the cheapest option but I could see it potentially working very well for the higher priced higher levels of service in order to help differentiate them and be seen to add significantly more value. A professional interpreter + the world’s best technical expert in the specific subject area of concern is likely to be much much better than the best person that knows about the specific product and who happens to speak the required language… In fact, such a process model would make the 120+ language provider’s approach look a little silly.
But why did I pick Swedish as the example? Well it demonstrates another point. A software provider I know well offered Swedish localized products and Swedish voice support – Was Sweden a major market for their solutions? Not really. But they had one massive customer in Sweden that they had agreed to do this for. What I am getting at here is the need to take into account the commercial realities of the subject. If your Latvian sales team is willing to sign up for X million in sales if corporate deliver product and/or support in Latvian (and product management and sales management believe that they will actually deliver the sales) then they (the decision makers) should balance the costs of delivery and the X million revenue / margin return and make a value based judgement. Maybe they should. Maybe they shouldn’t. But only they will know which way is right.
As for local language support being a competitive differentiator… This implies that you may be overly focusing on the wrong constituency within your target customer base. The average CIO and VP of Operations are unlikely to be swayed by 24×7 local language support if there is a viable alternative in place (as described above) – In fact it could be argued that 24×7 local language cover is an expensive luxury that they should forego. However, if you are only talking to the technical rank and file then yes, local language cover is more important to them… But should you really be talking to those folks in isolation…? Maybe, that’s the real question that needs to be addressed here.
Remember that local language support is only one potential enabler of the support process. Its role is to facilitate the effective communication between a customer with an issue and the most appropriate technical resource within the support provider’s organization that can help resolve it. If the most appropriate technical resource doesn’t speak every language that your customers speak then you have to come up with a process to allow them to communicate with those in need or accept that you may very well be compromising service quality by seemingly offering a better service in the customer’s native language…
View Free, Relevant Gartner Research
Gartner's research helps you cut through the complexity and deliver the knowledge you need to make the right decisions quickly, and with confidence.Read Free Gartner Research
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.