curious 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 you don't do any of this based on the video though, I'm unable to test as I'm in the UK.
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.
I personally would be quite worried about it being used for prank calls. At the click of a couple buttons anyone can create a very awkward conversation between AT&T and a random stranger (or a friend).
my thoughts exactly. pre-mature optimization is the root of all evil. When I first heard of this idea I ran through a list of ways to abuse it and make you guys go bankrupt :), but I've found there are far fewer crooks out there than there are honest people.
I love how you solved a problem for me without me having to jump through hoops.
True to the spirit of a hacker. This just screams of awesome execution, it's very refreshing to see in these days of startups.
Excellent idea!