Archive for June, 2006

Mayhem to come?

Friday, June 30th, 2006
It would be a nice feature for my own CRM system if it populated my calendar with significant events such as bank holidays, international public holidays, and other noteworthy occurrences, like say major sporting events. That way I might have avoided scheduling a workshop for the day of the England V Trinidad and Tobago match. Anyway, from what I could gather from the commentary it was one of those matches best watched on radio. As way of consolation the journey home at least was rapid – I can’t remember the M4 quite so devoid of traffic during rush-hour – and I did at least make it home for the last ten minutes.



At least the workshop went well. The client is well down the road to defining their requirements, so our focus was to help further shape them in the context of what is available ‘out of the box’ with some of the mainstream packages. This involved running through point by point and illustrating how each requirement could potentially be delivered through a CRM application. One benefit of doing this is that the client gets quick feedback as to the complexity and associated cost of delivering each functional requirement. They can consequently refine their needs by more effectively judging when to customise and when to live with standard functionality, and it becomes far easier to structure the project in the context of any budgetary constraints.



Anyway, given the inherent lack of certainty of predicting England’s progress through the remainder of the competition, there is significant potential for diary mayhem to come. Then again if we go on to win I guess I can live with it!

AHT Cartoon

Saturday, June 24th, 2006

When too much effort is put into improving handle time, reps tend to get very creative regarding ways to lower their AHT.  Sometimes the drive to improve yields positive results, other times this cartoon may reflect what happens.

Call center monitoring cartoon from callcentercomics.com

Cartoon-8.JPG

 

 

 

Share the Fun Without Doubling the Price

Friday, June 23rd, 2006
As we rush into Web 2.0, maybe we should start with multichannel 1.0.

I went to book a summer flight through my credit card company's travel department. After finding the perfect flight and learning there were three seats left, I tried to use my membership travel points. "The rewards system is currently unavailable." OK, so I call customer service. They couldn't help me, but they would transfer me. Nine minutes on hold later, I am still waiting. On my other line, I call the airline directly, because they are listed as a partner. But, in fact, they are not a partner. They do, however, have a partner who is a partner, and if I call the partner's partner and set up an account, then they could transfer points to my account. So, I call the partner of my card's partner and hear, "We are experiencing technical difficulties. If the line goes dead while you are on hold, please call back later."

Web sites down, call centers that can't handle basic calls, wait times lasting 20 minutes or longer; are any of them making money? You guessed it: the credit card company; and it doesn't seem to be in a hurry to improve. And no, I did not get the frequent flyer seats.

Web 2.0, Web-oriented architecture, service-oriented architecture, Ajax, rich clients, semantic HTML, REST and so forth. While your technologists get excited about all the new toys, maybe the lines of business that interact with customers might see how the basics can be improved. Who is in charge of determining your priorities, and what is it based on? Who in the CEO's office will see these daily insults to your customers? Or maybe you have fixed this problem. If so, we'd love to hear from you.

Share the Fun Without Doubling the Price

Friday, June 23rd, 2006
As we rush into Web 2.0, maybe we should start with multichannel 1.0.

I went to book a summer flight through my credit card company's travel department. After finding the perfect flight and learning there were three seats left, I tried to use my membership travel points. "The rewards system is currently unavailable." OK, so I call customer service. They couldn't help me, but they would transfer me. Nine minutes on hold later, I am still waiting. On my other line, I call the airline directly, because they are listed as a partner. But, in fact, they are not a partner. They do, however, have a partner who is a partner, and if I call the partner's partner and set up an account, then they could transfer points to my account. So, I call the partner of my card's partner and hear, "We are experiencing technical difficulties. If the line goes dead while you are on hold, please call back later."

Web sites down, call centers that can't handle basic calls, wait times lasting 20 minutes or longer; are any of them making money? You guessed it: the credit card company; and it doesn't seem to be in a hurry to improve. And no, I did not get the frequent flyer seats.

Web 2.0, Web-oriented architecture, service-oriented architecture, Ajax, rich clients, semantic HTML, REST and so forth. While your technologists get excited about all the new toys, maybe the lines of business that interact with customers might see how the basics can be improved. Who is in charge of determining your priorities, and what is it based on? Who in the CEO's office will see these daily insults to your customers? Or maybe you have fixed this problem. If so, we'd love to hear from you.

Broken Phones, Promises and Processes

Tuesday, June 20th, 2006
Whenever I arrive at the airport in Tel Aviv, my first stop before leaving the terminal has been to the counter of one of the country's largest cellular communications providers. I have done this three times a year for the past five years. I rent a pre-paid cellular GSM phone. I never question the price. I always replenish the phone account with extra minutes. (Yes, I know it would be cheaper to buy a phone. Don't ask why I rent, but you do have to wonder!) This cellular company always profits handsomely from my business. That is, until yesterday, when it lost me as a customer, likely forever. As in most industries, it has a strong competitor, and next time I will try them out. My experience highlights how the marriage of poor processes and bad technologies can cost a business revenue and hurt profits.

My rented mobile phone died within 48 hours of picking it up. I dialed the main number of the cellular provider from my hotel phone, which transferred me to service. I asked if I could stop into a local store and swap phones. No, was the reply, I would have to travel to one of the service centers and deal with it there. I told them I was only in the country for four days on business and was unable to get a cab to travel to a repair center in the next town. Well, they said, that is all we can do.

Upon leaving Tel Aviv, I left my mobile phone at the airport office where I picked it up. I asked the representative if I could pay only until the time I called the provider for mobile phone replacement. Basically, I wanted a 50 percent discount for having had no phone for three days. The representative had no record of my call to the service center three days earlier, nor any way to look up a call. She looked at the phone I returned and tried to turn it on. When she couldn't, she returned it to the bag and printed out my bill. I said, "So, you are charging me 100 percent of the total for a phone that does not work?" She, of course, had no authority to do anything else but that. None of the five people at the office had any authority to make any decisions, nor was there anyone with more authority whom they could call. I asked if she could at least make a note in my payment record that I was dissatisfied with the service. She said she would write it down and tell her boss. I asked her why she did not just enter it into the system. "Because sir, there is no system."

Would this be your company's response to a long-standing, profitable customer on his or her first encounter with a defective product or bad service? How do you know?

Broken Phones, Promises and Processes

Tuesday, June 20th, 2006
Whenever I arrive at the airport in Tel Aviv, my first stop before leaving the terminal has been to the counter of one of the country's largest cellular communications providers. I have done this three times a year for the past five years. I rent a pre-paid cellular GSM phone. I never question the price. I always replenish the phone account with extra minutes. (Yes, I know it would be cheaper to buy a phone. Don't ask why I rent, but you do have to wonder!) This cellular company always profits handsomely from my business. That is, until yesterday, when it lost me as a customer, likely forever. As in most industries, it has a strong competitor, and next time I will try them out. My experience highlights how the marriage of poor processes and bad technologies can cost a business revenue and hurt profits.

My rented mobile phone died within 48 hours of picking it up. I dialed the main number of the cellular provider from my hotel phone, which transferred me to service. I asked if I could stop into a local store and swap phones. No, was the reply, I would have to travel to one of the service centers and deal with it there. I told them I was only in the country for four days on business and was unable to get a cab to travel to a repair center in the next town. Well, they said, that is all we can do.

Upon leaving Tel Aviv, I left my mobile phone at the airport office where I picked it up. I asked the representative if I could pay only until the time I called the provider for mobile phone replacement. Basically, I wanted a 50 percent discount for having had no phone for three days. The representative had no record of my call to the service center three days earlier, nor any way to look up a call. She looked at the phone I returned and tried to turn it on. When she couldn't, she returned it to the bag and printed out my bill. I said, "So, you are charging me 100 percent of the total for a phone that does not work?" She, of course, had no authority to do anything else but that. None of the five people at the office had any authority to make any decisions, nor was there anyone with more authority whom they could call. I asked if she could at least make a note in my payment record that I was dissatisfied with the service. She said she would write it down and tell her boss. I asked her why she did not just enter it into the system. "Because sir, there is no system."

Would this be your company's response to a long-standing, profitable customer on his or her first encounter with a defective product or bad service? How do you know?

World Cup Fever: Do Your Fans Tattoo Too?

Monday, June 19th, 2006
With the excitement surrounding the World Cup, Magnus Soderlund's work on customer loyalty led him to note that the highest level of customer loyalty he could identify was when customers tattoo themselves with the logo of their supplier. The obvious and rare commercial example is Harley-Davidson customers. But in soccer, it's common for fans (not customers) to tattoo themselves with their team's insignia. Are your customers so emotionally tied to your organization that they tattoo themselves with your logo?

In asking that question during the past two years, I've only come across two examples where companies found that their customers had tattoos. Both were in the food industry, where branding is strongly funded.

Do you have an example where customers tattoo themselves? Is there a proxy for tattooing that you've noticed emerging among your most loyal fans? I'd love to hear about it.

World Cup Fever: Do Your Fans Tattoo Too?

Monday, June 19th, 2006
With the excitement surrounding the World Cup, Magnus Soderlund's work on customer loyalty led him to note that the highest level of customer loyalty he could identify was when customers tattoo themselves with the logo of their supplier. The obvious and rare commercial example is Harley-Davidson customers. But in soccer, it's common for fans (not customers) to tattoo themselves with their team's insignia. Are your customers so emotionally tied to your organization that they tattoo themselves with your logo?

In asking that question during the past two years, I've only come across two examples where companies found that their customers had tattoos. Both were in the food industry, where branding is strongly funded.

Do you have an example where customers tattoo themselves? Is there a proxy for tattooing that you've noticed emerging among your most loyal fans? I'd love to hear about it.

The international dimension…

Wednesday, June 14th, 2006
Several of our current projects include deployment to international offices and users. This tends to make the implementation more challenging, and I’ve seen a lot of projects get tripped up because they didn’t appreciate the additional complexity. On the one hand requirements are generally a lot more diverse, not just in terms of local currency and language needs, but also because there can be distinct differences in the nature and operation of each market.



Secondly, user adoption can be much more ticklish when you are dealing with independent operations distant from head-office. A situation often exacerbated when international offices end up short of the resources they need to make the project a success because of the cost and relative inconvenience (unless the office happens to be based in one of the more exotic locations) of sending project staff around the world.



One of the key objectives with these implementations is to ensure the project isn’t perceived as a solely head office initiative and that the needs of the international organisations are well represented throughout the project. Resource allocation also needs to reflect the additional user adoption challenge of remotely based users and be weighted accordingly. Sadly our involvement in these projects has not yet resulted in as many travel opportunities I might have hoped for; technology is proving our enemy in that respect. There’s too much we can accomplish these days without leaving the office, never mind the country.

Quality Assurance feedback session – customer service cartoon

Sunday, June 11th, 2006

QA feedback should always be done with the intent of helping agents become better at their jobs.  Taking a heavy handed approach, or an overly negative tone when providing feedback, will give agents the impression that senseless criticism is QA's only aim.

Call-center-comic.JPG