How we got rid of 80% of our support calls
The year is 2010 and yours truly is deciding on opening a Groupon like coupon site back in his country. A bit of coding + a bit of selling and we were up in the air.
Beyond being the VP-RnD, CFO and Janitor, I had the dubious role of being the Head (and sole employee) of our “Customer Support”.
A wise man said once, “To know your customers, you must know your customers“. So instead of spamming my visitors with various pop-up/slide-on/drop-left/pop-off tools for suggestions/questions/injestions, I just went on and put my personal mobile phone. Right there on the buy page, in HUGE capital letters.
Number of people who emailed our support email during the next week: 2.
Number of people who called me up (thankful during reasonable hours): ~100
The next bit might surprise you: It appears that even in the year 2010, the average 30 year old mom (that is our main demographic – I asked) is utterly terrified of using her credit card on the web.
“Is it possible to buy by phone ?” She would ask.
“Well yes mam, did you have problems buying on the site ?“.
“Noo.. its just that I am worried about putting my card on-line“.
In the beginning I was naive enough to try:
“No need, we have SSL on the page and our servers are PCI compliant” line…
“Yeeaa… but.. can I buy over the phone ?“ is what I got every time.
So we proceeded with me opening the website on my PC and filling in her details, as she dictated them to me.
Not a a week has passed and the executive team started getting multiple complaints from the support staff (Me). And the VP-RnD decided that something must be done.
Something being done
Option A: Do some bad-ass A/B testing. e.g. : Move button 17 pixels to the left, change the first letter of some words to capitals and maybe even try switching the radio buttons from being round to being square.
Option B: Try to address the issue at hand.
Since my users weren’t very tech savvy and couldn’t/wouldn’t understand that the page is secured with SSL. It became apparent that they needed to be told. Proposed solution: Put a big-red-dotted border around the form and write in large, red and reassuring letters: “SECURE ZONE”
The form before:
The form after:
For the Hebrew challenged, the writing in red is “This area is secured by SSL”.
The test
Next step: Ask (sample user: mom) to buy a coupon and provide feedback.
(In the initial test version, I also had her enter her name and email in fields that were outside the “safe zone”).
Feedback: “I felt a bit uncomfortable filling in the name and email, since they were not secure.. but I filled anyway because its your site” (GREAT SUCCESS !!)
3 minutes later we went live, one week later I took my phone off the site.
Results: Even with increased activity, phone calls went from ~100/week to ~20.
Conclusions
You can A/B test the crap out of your site, but you might try asking your users if something is wrong first.
“Most people will assume a safe is safe if it looks like a safe safe”











