View Touch Points from the Customer’s Perspective – 5/28/13 TOW

I received an email from my wireless telephone provider. They mentioned that I was now eligible for an upgraded phone at a discounted price (and if you’ve seen a 1990s flip phone, you’ll know why they want me to upgrade). Apparently the upgrade date had been reached, and I was eligible for the upgrade. One minute later, I received an email from the same provider telling me that it was an anniversary of sorts, and therefore I was eligible for an upgrade at a discounted price. About one minute later, I received a third email from the same wireless provider noting that I was now eligible for a discounted upgrade to my cell phone as a reward for my loyalty.

What the organization didn’t realize was that they were sending essentially the exact same e-mail at the exact same time with 3 different subject headings. The exact same upgraded cell phones were offered in each e-mail with those discounts available. So there may have been a Touch Point Plan that the provider had developed, but they were not looking at the plan from the customer’s perspective. Something that might have appeared very professional at first to the customer, turned out to be an aggravation after the third – essentially duplicate – e-mail arrived at my inbox.

If you work in a client relationship management role at your organization (for example, you’re a season ticket services representative for a sports team), this Tip of the Week is especially important for you. When you build your Touch Point Plans from the organization’s perspective, you determine when to send out information based on events or timeline triggers; make sure, however, that you’re not just looking at the plans from the organization’s perspective. Invert your Touch Point Plans to test them from the customer’s perspective to know what they’re going to receive and how they might perceive the information.

Develop Touch Point Plans from the customer’s perspective.

Posted on in Customer Service Tip of the Week

Add a Comment

You must be logged in to post a comment.