3 ms·
Great idea: I assume app + backend + twillio API? The only think that might confuse people is if you start to recycle numbers (because you don't want to keep p
by PanMan 14y ago
Great idea: I assume app + backend + twillio API?
The only think that might confuse people is if you start to recycle numbers (because you don't want to keep paying for them), and the call gets connected somewhere totally unrelated.
- gregcohn 14y agoDefinitely an issue we've been mindful of and designed for.
- mmahemoff 14y agoHow did you design for this? I thought you might be using caller ID, so the number is only relevant to people with a specified phone number. (Similar to how Rebtel works.) But it doesn't seem to be the case here, as I think numbers can be shown publicly.
- gregcohn 14y agoAll phone numbers have some ambient activity -- wrong numbers alone account for at least some randomness, though some obviously have more than others, and even very established carriers sometimes distribute numbers with a "legacy". So it's sort of a known problem. For Burner, each number goes through a quarantine and is monitored for activity before we use it. EDIT: Also worth noting that SMS seems to be more popular than voice calls, at least initially. "Wrong number SMS" doesn't seem like an actual problem as of yet.