No visible privacy policy. No visible pricing information. Not good.
Twilio can do this without any help from these guys.[https://www.twilio.com/labs/twimlets].
https://www.twilio.com/blog/2009/05/dialing-multiple-numbers...
- I could just create an account with nothing entered on the password field and could also login to that account that way.
- https://thisnumber.rocks/ is not being pointed to this same app.
The menu one in particular: https://www.twilio.com/labs/twimlets/menu
Full disclosure: I'm an early (and former) employee @ Twilio
Then we switched to more of a "ring all the lines at once and the first one who picked up got the call" -- much better for the person dialing in... but meant every one of our support people got distracted every time the phone rang... they hated it.
Eventually we just went back to something like ZenDesk for customers to write in to create tickets, and then expanded it to something more like what Apple does... where the user creates a request to be called back at a certain time. This is what the client still uses. It's a better system for everyone than trying to sort out incoming calls in real-time.
If you're Amazon/Apple/eBay and the "call me on my phone" allows 1-5 minute time windows to being called, that makes sense, but if the customer is sitting around for 10+ minutes you've already frustrated them.
Ah, hang on the slide-away at the side says £10, whilst the "STEP 5" says £0. Looks like there might be an issue with your business logic?
[FF51 on Ubuntu.]
Which combo did you select to get the £10 and £0?
Making a claim without constructive supporting points is usually not useful and worst appears you may know nothing other than how to cause problems seeding doubt.
[1] Use-Case: Create a virtual number on Twilio and whenever someone calls, a list of real numbers will be tried sequentially. You can set up opening hours. If nobody answers, a voicemail is recorded and sent to you by email.
No need to be rude. This is Show HN. Sharing first attempts is the whole point.
Although with that said... knowing the Twilio API and looking at this design I think someone could build this in about a day.
I don't want to shit on the idea, but with the amount of "build this thing with twilio" content twilio puts out, the benefit of this is saving the time of setting something similar up for yourself.
The only thing I can think of is if a competitor enters the space and blows them away. In which case, there is your answer, you go to whomever blew them away.
I can't imagine a lawsuits or something like that taking them down at this point. They have been around too long, it would have happened already.
But the chances of that are so remote I'd still feel comfortable putting mission critical systems on it.
BTW, anyone interested in a tutorial? I can create one.
I'm not saying this will be the next Dropbox, but dismissing products so offhandedly because you underestimate the average user's aversion to "writing a few lines of Javascript" is silly.
This is nothing like dropbox. This is barely a hello world app on the Twilio platform. I have little doubt he could write a tutorial to walk people through it in an hour two two.
This would be a good analogy if you dropbox was literally just provisioning a user and setting an FTP password. And if it was, Dropbox would hit scaling problems on almost day one.
This won't hit scaling problems because it doesn't do anything... Twilio's API has built-in API calls for all this stuff and the webhooks can (and should) be hosted on AWS Lambda or Google Cloud Functions for pretty much free with automatic scaling.
