ManagementSpeak: Our customers are part of the team.
Translation: They’re the test department.
This week’s anonymous contributor is part of the ManagementSpeak Translation Team.
Month: January 2002
Another CEM case study (first appeared in InfoWorld)
According to Yoda, “Fear is the path to the dark side. Fear leads to anger. Anger leads to hate. Hate leads to suffering.”
While the road to the dark side of customer relationship management (CRM) — dubbed “customer elimination management” (CEM) by a different Lewis — follows a different path, it also leads to suffering. As evidence:
My broadband service works great, but I’ve been traveling, which means I need dial-up capability. No problem: My ISP has a mobile access option, which I duly set up according to the instructions. Just one glitch: I can receive mail, but can’t send it.
That was over a month ago. Through endless hours with this CEM practitioner’s on-line chat and telephone-based technical support I’ve learned that:
- The two help channels use different problem management systems and have no access to each others’ records.
- Level Three support, also known as “Network Operations,” isn’t allowed to talk directly to customers. That’s their policy, and it’s unbreakable.
- For that matter, Level Three support can’t talk directly to Level Two, either. The telephone system has been carefully engineered to prevent it, even though the two groups work in the same building.
I’ve extracted some lessons for establishing a successful CEM practice in your own organization:
1. Make sure organizational boundaries are high. Use technology and your accounting system to reinforce them. In the case of my service provider they’ve gone the extra mile: While the parent company owns an excellent dial-up ISP with the same core brand, broadband is a different division, so it set up its own dial-up service rather than piggyback on one that works exceptionally well.
2. Institute bad metrics. From my various conversations it’s clear this company only measures the number of problems resolved. This ensures an unrelenting focus on dealing with the easy ones. Letting a few tough ones go for a month or three won’t affect the performance reports.
3. The more policies the better, and make sure every employee knows they’re all that matter. Since my first article on CEM I’ve received an avalanche of CEM stories, and most included at least one episode of “That’s our policy.” A thick policy manual and CEM go together like toast and jam.
If you’re wondering, I tried to offer my provider a chance to respond. Unfortunately, the company keeps its media relations group well-hidden, as carefully sequestered as its Level Three support engineers.
Hey, do you think it’s the same guy?