3 ms·
I've been working on http://parrot.dev http://parrot.dev, it uses an Android phone to enable sending messages from an API, while it's still new it's currently i
by vertis 5y ago
I've been working on http://parrot.dev http://parrot.dev, it uses an Android phone to enable sending messages from an API, while it's still new it's currently in use with a collection of customers.
At 250k it might not meet your needs because whatever phone provider you're using might have a problem. It is possible to pair it to multiple phones as well.
My existing customers are using it to send ~200 messages a day to their subscribers. It supports SMS replies, so you can implement stop codes, depending on your needs.
If you want to discuss it more, feel free to reach out (contact on profile).
- countvonbalzac 5y agoThis is brilliant. Do you know what sort of limits mobile service providers impose on phones?
- vertis 5y agoI think it varies heavily, most of my customers are in Australia (where Twilio is even more expensive) and it seems to be working fine for them currently. But they're not sending huge volumes, they're also not sending anything mission critical (there is a sweet spot).
- jqpabc123 5y agoCarriers won't give you an exact limit, most just specify "personal use". And they may not catch on right away but once they do, they will likely ban your number. Personal opinion, you're going to have all kinds of issues with this in the USA.
- vertis 5y agoIt's an important consideration, and one that I've thought about but really lack any ability to gather data on. I built this originally to meet the needs of my brother's business and his customers. It has proved useful for him and his customers, and has expanded beyond that, but I don't really know how much to pursue building it further based off risks like this.