I built my Call Forwarding app using Plivo. It was pretty straight forward to use. https://www.plivo.com/docs/getting-started/forward-an-incomi... is their official documentation on Call Forwarding. Also, every user gets a pre-built Call Forwarding which requires you just add the numbers for testing which looks like this - http://callforward.herokuapp.com/forward/?Numbers=NUMBER_1_H...

More importantly, why would you want to call your "real" numbers sequentially by default? You might prefer hitting all of them simultaneously, which is also trivial as everyone else here has mentioned.

https://www.twilio.com/blog/2009/05/dialing-multiple-numbers...

That's my first thought. Why not just do it yourself? Especially when twimlets are around.

Try the demo account I created. Username / password = l1647751@mvrht.com / l1647751@mvrht.com.

That link you posted gives me a cert error.

Thanks ! I'll fix this.

Wow, I've never heard of Twimlets; very cool! Thanks for sharing!

Yes, we string a couple of Twimlets together to direct people to support or general inquiry phone lines. Works really well. No problems in 3+ years.

The menu one in particular: https://www.twilio.com/labs/twimlets/menu

We use a twimlet for our business number. It simply plays a recording directing people to our support web page and email (phone support would be too expensive). A surprising number of places need a phone number; for example, Stripe includes it in the charge description.

But now it's bad for the customer again. When they need help, they are ready to call and get their problem solved now, not at some point later in the day.

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.

Yes, it is.

It's more like DNS using Twilio. It's analogous to Google Voice.

Looks like this is "bring your own number". It's neat, but I wouldn't trust this site to stay up under any kind of stress, which means my number would be erratically dead. If the source is available though, this is neat enough I'd consider self-hosting it.

it's available in more countries than the US

That's something I've been looking for, however $75 a month? Ouch!!

I don't understand how you make money, which makes it look like there's going to be hidden costs. If I start at https://www.windsor-telecom.co.uk/memorable-business-number/... and choose, for example, a revenue generating number then go to the payment it says I get a free number that diverts to my phone for no up-front cost and zero monthly fee. So how does that work for you?

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.]

This one is new, so they haven't learned all the corner cases that make VoIP more difficult than anticipated.

I don't think this qualifies as VOIP. It's not even POTS or mobile. It is just an interface for an API.

Although with that said... knowing the Twilio API and looking at this design I think someone could build this in about a day.

You keep control over your number, which you bought on Twilio.

I too would like to know what the thought behind this question is. They are a well established company that runs 2FA and awesome phone apis / systems for thousands of startups and large companies in a field that is high barrier of entry (less competition) and predictable profits since they meter their usage.

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.

Not OP, but I am honestly curious to know why you think they will go anywhere soon. Could you please elaborate?

Dropbox is just an FTP server.

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.

Op got downvoted a lot (and perhaps deserves it because of the tone of his post) but makes a valid point.

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.

Yes, go ahead, write the tut.