Background
For a few years now, leaders at customer support organizations have talked about moving customers from a ‘transaction-based’ service and support model to a ‘relationship-based’ one. This involves changing customers’ perceptions, from contacting you only when there are break-fix or how do I questions, to one that understands their business, including the technical and business context of their queries.
With this new approach, you don’t just wait for customers to contact you and then react. Your teams embed knowledge sharing into their practices to reduce or eliminate the ‘known’ issues that customers call about, leaving time for ‘new’ issues or queries that need a personal touch to resolve. You help your customers’ business become more successful by improving the way they use your products and services. This evolution in turn is an important first step in moving from
an expert for hire to a trusted advisor.
After early successes in this journey, many organizations run into a seemingly impenetrable wall. Your senior team ‘gets it,’ but this understanding does not seem to trickle down to most mid-level managers and frontline teams. You are able to get people to share knowledge to tackle the proverbial low hanging fruit (answers to simple issues or frequently repeated questions), but you can’t seem to convince other groups to share knowledge around complex and rarely-repeated processes.
Do they just not get it? What exactly is going on?