Sideways customer service

-

After reviewing my credit card statement, I realized I was paying every month for efax (a service I used twice in 2006, one more time in 2013, and subsequently just missed on my billing statements every month for the last...yes...9 years...). The following is the somewhat surreal interaction I had when I cancelled... 


 Greg Curtis: Thank you for providing the information. Please allow me a moment while I pull up your account. 
In the meantime, please type the number corresponding to your reason for cancellation:
1) Moving to another provider
2) Bought a fax machine
3) Business or role changed
4) Short term project completed
5) Financial reasons
6) Problems with faxing or billing
7) Dissatisfied with quality of service
8) Too costly
me adding my own answer 
 Michael Mainguy: 9) only needed it once 2 years ago and forgot to cancel :) 
 Greg Curtis: As we'd like to keep your business, I can offer you a discount and also waive your subscription fee for 1 month. The discounted monthly fee would be $12.95 per month. This new plan includes 150 free inbound and 150 free outbound pages monthly. 
 Greg Curtis: There is no contract and you may cancel anytime. Shall I switch you to this 1 month free $12.95 monthly plan? 
 Michael Mainguy: No thank you. 
 Michael Mainguy: I literally need to fax once every 3 or 4 years 
 Greg Curtis: I completely understand your wish to discontinue. Conversely, I can offer you a discount and also waive your subscription fee for 2 months so that you can re-evaluate your needs. After the free period, pay just $12.95 per month. This new plan includes 150 free inbound and 150 free outbound pages monthly. 
 Greg Curtis: There is no contract and you may cancel anytime. Shall I switch you to this 2 months free $12.95 monthly plan? 
 Michael Mainguy: No thank you 
 Greg Curtis: OK, I will go ahead and cancel your account.
An email confirmation will be sent at your registered email address.

Is there anything else, I may assist you with? 
 Michael Mainguy: No, thank you very much 
 Greg Curtis: Thank you for contacting online Fax support. I hope you found our session helpful. Goodbye and take care. 
 Greg Curtis has disconnected.

My evaluation...they do not understand the needs of an occasional user who would be willing to pay a premium to send 1 or two pages of faxes every couple of years (as only ancient banking institutions and outdated consulting organizations do this any more...but I digress).

Comments

Post a Comment

Popular posts from this blog

Please use ANSI-92 SQL Join Syntax

-
Image
Way back in 1992, a standard was published for SQL. In it, the syntax for specifying joins in SQL Database was finally standardized. This was a good thing because (for folks who've been doing this a while), trying to decode the vagaries of how various Databases handled outer joins could drive you bonkers yielding different results depending on the parse order of things in the from and where clauses. Unfortunately, some DBMS vendors took a while to adopt this standard (Oracle didn't support it until 2001), but at this point if you're using a major RDBMS and NOT using it, you're probably mired in a tradition or habit that bears changing. As an example of what I'm describing, here are some examples of what I mean. Old School (no standard syntax + implementation and evaluation of predicates varied by vendor [and query]): select * from customer, order where customer.customer = order.customerid ANSI way (agreed to standard, predicate evaluation has some rules
Read more

the myth of asynchronous JDBC

-
Image
I keep seeing people (especially in the scala/typesafe world) posting about async jdbc libraries. STOP IT! Under the current APIs, async JDBC belongs in a realm with Unicorns, Tiger Squirrels, and 8' spiders. While you might be able to move the blocking operations and queue requests and keep your "main" worker threads from blocking, jdbc is synchronous. At some point, somewhere, there's going to be a thread blocking waiting for a response. It's frustrating to see so many folks hyping this and muddying the waters. Unless you write your own client for a dbms and have a dbms that can multiplex calls over a single connection (or using some other strategy to enable this capability) db access is going to block. It's not impossible to make the calls completely async, but nobody's built it yet. Yes, I know ajdbc is taking a stab at this capability, but even IT uses a thread pool for the blocking calls (be default). Someday we'll have async databa
Read more

The difference between Scalability, Performance, Efficiency, and Concurrency explained

-
I thought I'd give some explanation of the difference between scalability, performance, Efficiency, and concurrency. To make things more accessible (and because I'm watching a cooking show on TV) I'm going to use a baking metaphor to help explain the differences. In our case, the system in question is baking cookies for consumers. Scalability, is how well something responds to adding more resources. If we can double our capacity by doubling the number of resources, we've got linear scalability. In our baking example, if we add more ingredients, we can scale to a larger number of cookies. To contrast with our other metrics, this doesn't actually increase the performance of creating a single cookie (they still take 10 minutes to bake), and the efficiency is the same (we just have more capacity). We also cannot bake more cookies in a fixed time period, but over a larger time period we can produce more cookies. Performance is how fast something can get done, u
Read more