G2

Pratik S.

Senior QA Engineer

Information Technology and Services

Small-Business (50 or fewer emp.)

11/1/2026

"Reliable for SMS and OTP testing, console takes getting used to"

4/5

What do you like best about Twilio?

As a QA I mostly use Twilio when testing SMS and OTP flows in the apps we build. The message logs in the console are the best part for me. I can see straight away whether an OTP was sent, delivered or failed, and the error codes usually point to the cause, like an unverified or badly formatted number. The test credentials are also handy for checking a flow without sending real messages every time. Review collected by and hosted on G2.com.

What do you dislike about Twilio?

The console has so many products and settings that finding the right log or phone number can take a while, especially for someone new. Delivery to some countries is less predictable than others, and trial accounts can only send to verified numbers, which is a hassle when several testers need codes. The per-message cost also adds up once you're testing at volume. Review collected by and hosted on G2.com.

What problems is Twilio solving and how is that benefiting you?

It gives our apps a dependable way to send OTPs and SMS notifications, and for me it gives a clear record of every message. When a tester or client says they never got a code, I can check the log, see exactly what happened and raise a bug with the real error instead of guessing. That has cut down a lot of back and forth with the developers, and the API was easy for them to plug in. Review collected by and hosted on G2.com.