Search

Domino Upgrade

VersionSupport end
5.0
6.0
6.5
7.0
8.0
8.5
Upgrade to 9.x now!
(see the full Lotus lifcyle) To make your upgrade a success use the Upgrade Cheat Sheet.
Contemplating to replace Notes? You have to read this! (also available on Slideshare)

Languages

Other languages on request.

Twitter

Useful Tools

Get Firefox
Use OpenDNS
The support for Windows XP has come to an end . Time to consider an alternative to move on.

About Me

I am the "IBM Collaboration & Productivity Advisor" for IBM Asia Pacific. I'm based in Singapore.
Reach out to me via:
Follow notessensei on Twitter
(posts)
Skype
Sametime
IBM
Facebook
LinkedIn
XING
Amazon Store
Amazon Kindle
NotesSensei's Spreadshirt shop
profile for stwissel on Stack Exchange, a network of free, community-driven Q&A sites

« Getting inspiration from existing work is part of the creative process and NOT something a copyright lawyer should need to go after | Main| When Sofware matures you need to cut development to stay profitable, isn't it? »

Customer Care Expectations

There is a whole industry providing happiness to the people that ultimately decide over a company's success and failure: the customers. However it seems to be incredibly difficult to get customer service right (Yes Starhub and AIA, I'm talking to you). The rules however sound simple:
  • Customer care is for the most important person in the company: the customer. It deserves to be a VIP service
  • Customers are humans and like to be treated like one (VoiceMenu hell isn't human - tip for Starhub: answer every question with 0 and ignore the machine lecture about invalid answers and you will get to a human fast)
  • Every case needs to stay visible to both the customer and corporation until it is resolved
  • Every case needs to have a person in charge until resolved. That person might change during the course of a care engagement, but there is always a person in charge. (S)he is visible to the customer.
  • Every case has a status and that status is visible to the customer. Ideally it also has an ID, so it is easy to track when using different support channels. That ID must be suitable to be communicated verbally or in a short message
  • A case is resolved when the customer says so. Not earlier, not later. CSR (Customer service representatives) can suggest closure, but it is the customer's decision
  • Support is multi-channel. If the company allows login to their website (e.g. to check accounts), then all support cases need to be accessible there too, regardless of where they were filed in the first place. If a company uses SMS for support updates, one must be able to reply to it (Starhub fails there). If the call centre receives a call, they need to have access to the support cases opened through eMail, web or in a branch office. If support uses Facebook, Twitter or other social channels, they need to be linked to the support system
  • At any point in time a customer can use any channel to provide additional information or inquiry the status of a ticket
Customer Care puts the customer in the middle
You now can ask: "Stephan, what are you dreaming at night?". So what is going wrong with Customer Care in most places?
Customer care is treated as cost centre disconnected from the associated income. Instead of being treated as cost of sales, it is treated as general, to be eliminated, cost. The old management wisdom goes: you get what you measure. What typically can be found are things like: "# of calls handled" or "ticket open time", while measurements like "customer satisfaction" or "resolution of complex matters" are in short supply. If ticket open time is all you measure, then closed tickets (and angry customers) is all you get. More interesting would be (but that requires well integrated systems): do customers buy again after contacting customer support? Is there a feedback on Twitter, Facebook or a blog on the experience? How many tickets stay closed (I have re-opened quite some of them)? I hear the hordes of customer care managers howl: "But we need cold hard facts, don't take away our ticket open time". So if you have to: measure the time from ticket opening until the CSR suggest of closure for tickets that get closed thereafter. Measure how many closures get rejected. But be aware: you get what you measure. Want to change, see what people smarter than me have to say
As usual YMMV

Disclaimer

This site is in no way affiliated, endorsed, sanctioned, supported, nor enlightened by Lotus Software nor IBM Corporation. I may be an employee, but the opinions, theories, facts, etc. presented here are my own and are in now way given in any official capacity. In short, these are my words and this is my site, not IBM's - and don't even begin to think otherwise. (Disclaimer shamelessly plugged from Rocky Oliver)
© 2003 - 2017 Stephan H. Wissel - some rights reserved as listed here: Creative Commons License
Unless otherwise labeled by its originating author, the content found on this site is made available under the terms of an Attribution/NonCommercial/ShareAlike Creative Commons License, with the exception that no rights are granted -- since they are not mine to grant -- in any logo, graphic design, trademarks or trade names of any type. Code samples and code downloads on this site are, unless otherwise labeled, made available under an Apache 2.0 license. Other license models are available on written request and written confirmation.