Why don't you just use Twilio or something? It doesn't deliver to all mobile phones on US carriers?
Re:Prove: Phone verification for developers
by niftylettuce on Tuesday May 28, 2013 @03:56PM
(#5782323)
we're powered by Twilio right now
Re:Prove: Phone verification for developers
by subsystem on Tuesday May 28, 2013 @04:08PM
(#5782404)
This is pretty basic, but helped me somewhat: http://www.scribd.com/doc/97294264/Nexmo-SMS-Deliverability-...
Nexmo also provides deliverability statistics: https://dashboard.nexmo.com/ratios/public
Disclaimer: I do a bit of part time dev evang for Nexmo.
Nexmo should be pretty good across the board as it pertains to what delivers best (direct to carrier model: http://blog.nexmo.com/post/4690069179/directsms). In that way, Nexmo is trying to solve the issue you're having.
Have you had any issues with deliverability and Nexmo (where another provider delivered better)? Nexmo actually provides some tools to automatically optimize traffic based on client conversion ratios.
I haven't had very good luck with Nexmo and deliverability. I wanted to migrate all my traffic there, but had to stop after a few %-tests resulted in increased failure rate. I do still use them for some areas/networks they seem to do better with. I also appreciate their good customer service.
Re:Prove: Phone verification for developers
by teljamou on Wednesday May 29, 2013 @03:09PM
(#5788394)
Sorry to hear that. I am part of Nexmo helpdesk and we are here to help you address any issue you are seeing. Can you share with us more info on the issues? message IDs? phone numbers? account? best is that you drop us a ticket at nexmo.zendesk.com and we would love to assist!
Re:Prove: Phone verification for developers
by tjlytle on Wednesday May 29, 2013 @10:49AM
(#5786552)
I'm sure the team would appreciate the feedback as to where the deliverability was less than another provider. Also, might want to ask about the recently added tools to use your conversion stats to help route traffic.
Most of my time is spent trying to figure out which mobile networks which SMS gateways will deliver best to, and then directing the correct verification traffic through those gateways accordingly. Which is a nightmare, in part because the successful delivery rates for different areas and networks constantly changes.
If this is the problem that Prove is solving, I think emphasizing that (or at least mentioning it somewhere) on the website is important. I would be an eager customer.