3 ms·

Another coachup dev here: how have others' experiences with Twilio been? We actually moved off Tropo because Twilio seemed to be better documented and we were

Another coachup dev here: how have others' experiences with Twilio been? We actually moved off Tropo because Twilio seemed to be better documented and we were having SMS deliverability issues with Tropo. Anyone used Twilio for SMS? That's next up on our Twilio integration.

patio11 13y ago
Yep, we're (heavy) users of Twilio SMS. Aside from maybe two incidents that I can think of in the last 3 years, they've been rock solid for us. I am struggling to remember any customer complaints from SMSes not being delivered -- while I think our scale guarantees that this has probably happened (yay telephony), it doesn't happen often enough for it to impact customer results for us. (The typical customer will be sending dozens to hundreds of them a week, so one or two going undeliverable do to carrier issues/user error/etc is not the worst thing in the world for us.)
dkeskar 13y ago
As patio11 said, this is a good approach and that was a well written post. I wrote twilioflow for similar reasons, including ease of testing interactions. https://github.com/dkeskar/twilioflow https://github.com/dkeskar/twilioflow Its been 3 years and Twilio has come a long way. All the best to you guys!
sologoub 13y ago
Used Twilio at two companies, primarily for voice. Support has always been stellar. The biggest advantage has been not worrying about infrastructure as we grew from X,000,000 minutes per month to XX,000,000. Essentially, you convert any CAPEX to OPEX, with all benefits and penalties thereto. SMS, we had to move over in a pinch (less than a day from zero to production), so integration is definitely super easy. Our volume was much less impressive - XXX,000 per month. The biggest outages have been during elections season. That said, Twilio has taken a lot of steps to ensure that won't happen next time around. The response times and follow-ups to any outages have always been very quick and transparent, which is all one can ask of a vendor. As far as I know, Twilio is still the major provider for that company, but I have moved on to ad tech space. :)

patio11 13y ago

Yep, we're (heavy) users of Twilio SMS. Aside from maybe two incidents that I can think of in the last 3 years, they've been rock solid for us. I am struggling to remember any customer complaints from SMSes not being delivered -- while I think our scale guarantees that this has probably happened (yay telephony), it doesn't happen often enough for it to impact customer results for us. (The typical customer will be sending dozens to hundreds of them a week, so one or two going undeliverable do to carrier issues/user error/etc is not the worst thing in the world for us.)

dkeskar 13y ago

As patio11 said, this is a good approach and that was a well written post. I wrote twilioflow for similar reasons, including ease of testing interactions. https://github.com/dkeskar/twilioflow https://github.com/dkeskar/twilioflow Its been 3 years and Twilio has come a long way. All the best to you guys!

sologoub 13y ago

Used Twilio at two companies, primarily for voice. Support has always been stellar. The biggest advantage has been not worrying about infrastructure as we grew from X,000,000 minutes per month to XX,000,000. Essentially, you convert any CAPEX to OPEX, with all benefits and penalties thereto. SMS, we had to move over in a pinch (less than a day from zero to production), so integration is definitely super easy. Our volume was much less impressive - XXX,000 per month. The biggest outages have been during elections season. That said, Twilio has taken a lot of steps to ensure that won't happen next time around. The response times and follow-ups to any outages have always been very quick and transparent, which is all one can ask of a vendor. As far as I know, Twilio is still the major provider for that company, but I have moved on to ad tech space. :)