4 ms·

So Twilio as an unsupported service which they charge others for it. They choose to close the service and don't have the courtesy to inform users before that an

by bond 16y ago

So Twilio as an unsupported service which they charge others for it. They choose to close the service and don't have the courtesy to inform users before that and now say the service was beta/unsupported and they are sorry for it? That's really lame... They have the obligation to inform users they're going to close a service, whether it's beta or not. The answers they gave is not the way to do it, giving an excuse because the service was unsupported and completely ignoring their fault in warning their users shows that they don't give a damn about the users. There's nothing wrong in coming here and apologize for not giving a warning before closing the service, but they choose not to do it...

jacquesm 16y ago
They already did, and 6 hours before you posted this. http://news.ycombinator.com/item?id=1726444 http://news.ycombinator.com/item?id=1726444
- bond 16y ago
  No they didn't: "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." This is not an apology for not informing the developer before closing the service...
  - jacquesm 16y ago
    Just quoting what you quoted: "Our apologies that we weren't clear enough about that fact, which caused you to roll international SMS features into your app." Reads like an apology to me. Read on for a bit, they acknowledge that their communications were lacking and have improved on that by making it easier to find this information. What do you expect of them? Groveling? A refund?
    - bond 16y ago
      Look, what he's doing his apologizing for not making clear it was an unsupported service. What he should have done is apologizing for closing the service without telling developers about it. They can try to deflect this as they want but the fact remains, he should have sent a warning the service would be closed at date X, not closing the service and tell afterwards they're sorry for not making it clear...

by bond 16y ago

jacquesm 16y ago

They already did, and 6 hours before you posted this. http://news.ycombinator.com/item?id=1726444 http://news.ycombinator.com/item?id=1726444

bond 16y ago
No they didn't: "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." This is not an apology for not informing the developer before closing the service...
- jacquesm 16y ago
  Just quoting what you quoted: "Our apologies that we weren't clear enough about that fact, which caused you to roll international SMS features into your app." Reads like an apology to me. Read on for a bit, they acknowledge that their communications were lacking and have improved on that by making it easier to find this information. What do you expect of them? Groveling? A refund?
  - bond 16y ago
    Look, what he's doing his apologizing for not making clear it was an unsupported service. What he should have done is apologizing for closing the service without telling developers about it. They can try to deflect this as they want but the fact remains, he should have sent a warning the service would be closed at date X, not closing the service and tell afterwards they're sorry for not making it clear...