7 ms·
Hi Greg - Why not disclose prior call patterns before selling the # rather than putting the burden on developers to flag spam to receive credits? Saving a cou
by WisNorCan 9y ago
Hi Greg -
Why not disclose prior call patterns before selling the # rather than putting the burden on developers to flag spam to receive credits?
Saving a couple of cents by getting reimbursed for the call doesn't actually solve the issue when your team is wasting their time picking up the phone only for it to be a misdial or spammer.
- Nexxxeh 9y agoIs it actually a problem though? I'm not a high volume consumer of numbers, but I've not had any spam on the handful of numbers I have. The same can't be said for my physical POTS/cellular numbers. Anecdote of one, and everything, but has anyone actually impactful levels of spam from an insufficiently cooled number that they wouldn't have had from any number in the area code?
- kevinburke 9y agoI think the idea is that all of the numbers to be sold meet an acceptably low bar of incoming text messages/calls before Twilio offers them.
- gregorymichael 9y agoGood question. Wholeheartedly agree that the burden is ours -- not the developer's -- to make sure a number is clean before you buy it. We monitor inbound activity for two months before making a number available for sale. <Reject> is not for spam that comes with a number when you buy it -- it's for all the stuff that happens after you put that number out in the wild. More than that though, we can't reveal historical patterns because we'd be violating the privacy of whoever previously owned the number.