News for hackers. Stuff that matters.
Re:How Twilio screwed us over by jeffiel on Saturday September 25, 2010 @02:11AM (#1726444)
Just posted this on Anthony's blog, but thought I would post it here as well:

--

Hi Anthony,

I'm sorry that you feel we were't straight forward, although our goal was to be completely transparent in our communication with you about the status of this feature. Since the time of launch, we thought we had clearly messaged that international SMS has been an unsupported feature, and that the entire product was in beta status. We had published this fact on our SMS product FAQs, as well as in the public GetSatisfaction forums. Our apologies that we weren't clear enough about that fact, which caused you to roll international SMS features into your app.

We do pride ourselves on putting developers and their applications first, and in being open in our communications, product capabilities and limitations. Please feel free to email me at [email protected], I'm always open to feedback, questions, comments or concern.

Sincerely,

Jeff Lawson Co-Founder & CEO Twilio.com

Re:How Twilio screwed us over by bradgessler on Saturday September 25, 2010 @04:39AM (#1726612)
Guys, I need to back Jeff up on this.

SMS is just a huge pain in the ass. The carriers have a strangle-hold over this and can cut messages off on a whim. We had an experience once with Verizon where they "accidentally" cut-off our short-code to Poll Everywhere on a Friday evening due to some "clerical errors". 72 hours later they finally had somebody "fix" the situation (support doesn't work on weekends there), and in the meantime we were left in a really bad place trying to explain to our customers how Verizon screwed us over.

I've dealt with some total dopes at Celltrust (I need to call these guys out, they're atrociously bad. Please don't do business with them unless you absolutely have to) where our service to Canada was entirely out for a week because they changed how their API worked. They failed to communicate that to us and nobody at their company could tell me how it worked so I had to fire up nc -l, point their gateway at that server, find somebody from Canada who could send a text, and see what came in. After the fact, I told them how horrible the experience was and provided recommendations on how they could improve it. They threatened to cut us off as a client because they felt I was being mean to them instead of acting on the feedback that could have made their service better.

Twilio thinks this is assine and are trying to change how this all works. We've shared with them the pains we've experienced with SMS aggregators and they share the same thoughts with us that its a totally unnecessary amount of pain that developers face to build SMS applications. They're really trying to make this easier and lower the bar.

Anthony, while your experience wasn't that hot, it was far and above what you'd experience elsewhere. At least Jeff acknowledges that Twilio could do better. That is so far above and beyond anything else in the industry. Throw on top of that an amazingly well executed API and the drive to make a difference in this industry and you're in good hands.

Re:How Twilio screwed us over by mariorz on Saturday September 25, 2010 @03:03AM (#1726505)
Hi Jeff, I had the same problem. It was not very clear from your pages or FAQs that international SMS was not supported. Now I see it's been made very clear in this page http://www.twilio.com/faq/international, that's great, the previous message was confusing to say the least. FWIW I complained about this on the getsatisfaction forums some two weeks ago http://getsatisfaction.com/twilio/topics/international_sms-1...

Fortunately I don't have a live app that depended on your service, so all it cost me was $50 deposited to start playing around.

Re:How Twilio screwed us over by redstripe on Saturday September 25, 2010 @02:46AM (#1726488)
Is there a page that lists all the beta features that may become unsupported without warning in the future?
Re:How Twilio screwed us over by rmah on Saturday September 25, 2010 @11:46AM (#1727166)
A professional organization NEVER turns off features -- final, beta, experimental, it doesn't matter what you call it -- without warning unless external pressures force you to. What you do is determine who is using the feature and send a warning to those customers. Then after waiting a while (a few days to a few months), you can turn it off.

Predictability is critical to B2B services. It is more important than price or performance. It allows customers to make an informed decision. It prevents dissatisfaction and PR disasters.

I also think this should be a lesson for younger businessmen. Customers will even get angry if you cut undocumented features. Or fix bugs they relied upon. Any change that impacts customers needs to be communicated in advance.

IMO, if you truly "put developers and applications first", you would have done this. I humbly suggest some soul searching.

Re:How Twilio screwed us over by OoTheNigerian on Saturday September 25, 2010 @06:57AM (#1726726)
Is this an apology? "you feel".... " we thought"

You are not really taking responsibility here. You are good guys. Just say "I am sorry" and ask how you can make him feel better.

http://37signals.com/svn/posts/1528-the-bullshit-of-outage-l...

Re:How Twilio screwed us over by edash on Saturday September 25, 2010 @04:52PM (#1727814)
I like Twilio and I'm a customer. It seems they did the best they knew how with this situation. But that was a really terrible apology and seems more insulting than assuaging to anyone affected. It's like there's a rule that once you have more than 10 employees all written communication needs to be jargon filled, passive-aggressive business drivel.

Better would have been:

"Anthony -

We're glad to have you as a customer, sorry we screwed up here. We posted notices to the status API and support email - but if you didn't get it, we didn't do our job! I definitely gained some perspective from reading your post.

We'll work even harder on future product updates to get notice to all our customers. If there's anything I can personally do to make the situation right, email me: [email protected].

Again, very sorry. Thanks for being our customer and letting us work to earn back your confidence.

Jeff Lawson - Twilio CEO

P.S. Task.fm looks really cool. Best of luck!"

Danielle from Twilio wrote a much more sincere and helpful apology in the thread above...she should probably handle the "responding to blog rants" duties from now on.

Re:How Twilio screwed us over by fredoliveira on Saturday September 25, 2010 @11:04AM (#1727066)
Isn't "I'm sorry" the very first thing he says after "Hi Anthony"? And as if that wasn't enough, he goes on to say "Our apologies" later in the paragraph.
Re:How Twilio screwed us over by javery on Saturday September 25, 2010 @11:18AM (#1727109)
He said he was sorry that you feel we did x. So he is apologizing for for the fact that Anthony feels a certain way, not the same as saying "I am sorry.".
Re:How Twilio screwed us over by sprout on Saturday September 25, 2010 @11:41AM (#1727155)
He has nothing to apologize for. You use features clearly marked 'unsupported,' you are going to get burned.
Re:How Twilio screwed us over by gommm on Saturday September 25, 2010 @12:16PM (#1727233)
I was also planning on using twilio for a project and when looking at their faq for the initial research, it wasn't very clear that it was something completely unsupported that could be disabled at any moments...
Re:How Twilio screwed us over by javery on Saturday September 25, 2010 @01:59PM (#1727439)
This is why programmers make horrible customer support people, it doesn't matter if you have nothing to apologize for. You say your sorry because no matter what the circumstances the person is unhappy with your service and your company - saying your sorry and fixing the problem keeps a customer. Sticking to your guns and saying you have nothing to apologize for just loses you a customer.
Re:How Twilio screwed us over by mariorz on Saturday September 25, 2010 @02:51PM (#1727536)
the features were not clearly marked as unsopprted. there were even price quotes for international SMS.