Show HN: "Never wait on hold again" service built with Rails and Twilio
31–40 of 88 posts
Re: Show HN: "Never wait on hold again" service built with Rails and Twilio
#32Thanks. :)
Re: Show HN: "Never wait on hold again" service built with Rails and Twilio
#33Great idea guys! Just curious, what happens when someone finally picks up and hears nothing? Is there a possibility that the other line will hang up before you have a chance to call us?
Re: Show HN: "Never wait on hold again" service built with Rails and Twilio
#34It would probably make sense to do this only for paid customers in the future so that people don't abuse the feature (and CS reps).
Facebooked.
Re: Show HN: "Never wait on hold again" service built with Rails and Twilio
#35Re: Show HN: "Never wait on hold again" service built with Rails and Twilio
#36Other than that its a great idea which I'm certain people would be willing to pay for (I would be if it was available internationally)
Re: Show HN: "Never wait on hold again" service built with Rails and Twilio
#37One minor gripe -- at least in Chrome, if you type something in ("Verizon") and hit enter without selecting any of the auto-complete options presented, you just get a generic "whoops, something went wrong". Ideally, just pop the user through a screen that lets them select from a list of possible matches.
I'd make a snarky comment about how the site doesn't render properly in IE 5.5, but I think I'm about 2 years late on that trolly.
Re: Show HN: "Never wait on hold again" service built with Rails and Twilio
#38curious how you intend to handle abuse? Maybe have an sms sent to the recipient first and they must confirm? I was just able to enter the example number ("555-555-5555") and it seems to process just fine (currently "Status: Operator on the line! Trying to connect you...") even though I clearly don't own that number. I could cause problems for both customer service people and cellphone users with this. I'm assuming yo…
Great question. There are a few ways we could handle it, but in principle we want to see how the problem happens before solving it. A confirmation process is a great idea but adds friction, and as we roll out we don't want to discourage usage. Basically, we want to see what happens so we don't optimize or problem-solve too early.
Re: Show HN: "Never wait on hold again" service built with Rails and Twilio
#39Re: Show HN: "Never wait on hold again" service built with Rails and Twilio
#40you guys are awesome. A few friends and I have been working on a similar project. You totally upped us on it. Great job :)
Glad someone else is solving this problem :)