Translation Guy Blog
The Consortium of Service Innovation of the Translation Automation Users Society (if you can get around that mouthful) shares an interest in localizing customer support. Unfortunately, I missed the November Conference, but Andrew Joscelyne provides a report at the TAUS site. “Customer support (CS) used to be all about running call centers. It then shifted to user searches of knowledge bases, with all the complexity this means for multilingual delivery pipelines. And now it has spread to sharing information on social media.”
CSI’s Greg Oxton shared a holistic view of the new “content explosion” for customer support. Today’s document stream includes informal content from many authors. And instead of being marketed top down, brands are being redefined as the conversation a company has with its customers. This means that the one-on-one call center experience is no longer a key function (only 2.4% of CS), and that 97% of the audience now engage with the relevant information via portals and communities on a many-to-many basis. Content is, once again, king.
Surveys show that customer satisfaction is based on customer loyalty (not profitability figures, for example) and that customer loyalty in turn depends on experience of content. The user’s emotional experience of this content is therefore decisive, and the support agenda is a major driver of this experience.
And its other customers who are providing that emotional experience. Content from the community is three times more important that knowledge found on a portal. Seekers of knowledge on a web page are ten times greater than call center volumes.
So the ROI becomes real back-of-the-envelope easy. The high cost of live one-on-one interaction for interpreter or human translated chat or email, offers the opportunity for an in-depth high-emotion customer experience, but that’s not always what customers want or companies can afford to provide.
Once the content sources have been identified, it is necessary to decide on the right flows. Some content, for example, should be frozen into books and updated at regular intervals; other content will need to propagate more fluidly and unstably across social communities, and any attempt to control this will damage the community. These choices will also influence what should be translated and how: centrally or by the crowd?
Crowd-sourced translation is a natural for customer support, and making it easy for community heros to chime in, and to cross barriers allows a rapid, fluid response not possible in more formal translation processes, even if it isn’t cheaper. (See it always comes back to money for me…)
I like the guys at TAUS because they are on the bleeding edge of the technology scimitar. These kinds of sophisticated approaches to localizing the customer experience are still too rare. Its the classic customer support dilemna. Is CS a cost center or a profit center? Guess it depends on what you make it.