Joseph Johnson

I run a small business. Like a lot of people, I ended up on Twilio because it was the obvious answer to "I need a business number that my team can share," and then spent considerably longer than expected discovering that Twilio is an API, not a product.

I can code well enough, so I built myself a shared inbox instead of paying for one. Other people started asking if they could use it. Most of them were not developers, which is the whole reason TelBuddy exists as a product rather than a private tool.

Everything on this site is built directly against the Twilio and Telnyx APIs. Not a wrapper around somebody else's wrapper, and not a reseller arrangement. Customers connect their own carrier account and pay the carrier directly.

Most articles about A2P 10DLC are written by people who have never submitted a registration. Mine was rejected the first time. The second attempt was approved, and the only thing that changed was the wording on two pages of my own website. That is why that guide contains the actual policy language rather than a summary of the rules.

The same goes for the rest of it. The Twilio and Telnyx comparison exists because I implemented both and found the two places they genuinely differ. The piece on time zones and business hours exists because TelBuddy had that bug, and every customer outside Eastern time was affected until I fixed it.

When something here is a limitation, I say so. When it is our fault, I say that too. That is not a marketing position, it is just cheaper than the alternative.