
Twilio Trial Only Texts Verified Numbers: How to Test SMS While You Build
The Twilio trial gives 100 SMS, texts only verified numbers and sends only template messages. What that means for a new app, and how to test real SMS today.
You build an app in Lovable, Bolt, v0, Replit or Cursor. It needs a text message: a login code, a booking confirmation, an alert. You sign up for Twilio, paste the keys, and the first send fails. The cause is usually not your code. It is the trial. This post explains what the Twilio trial allows today, what changes after you upgrade, and how to test real SMS while you build.
TL;DR
- The trial gives free units, not dollars. 100 SMS, 100 WhatsApp messages, 75 voice minutes and 40 Verify verifications. It expires after 30 days. No card is needed (Twilio docs, checked October 2026).
- You cannot write your own message. During the trial, the SMS body must be a template ID such as
sms_2fa. Twilio says: "Custom message bodies are not supported." - You can only text verified numbers. Up to 5 per account, in your sign-up country, from a shared trial number.
- Upgrading adds steps. Error 21608 now also blocks upgraded accounts without an approved primary compliance profile. You also pay per message, rent a number, and register your sender in some countries.
- To test today: textbee sends from your own Android phone to any number, with your own text. The free plan gives 300 messages a month and 50 a day, with no card. One HTTP call sends a message.
What does the Twilio trial allow in October 2026?
Twilio changed its trial model. The trial docs (modified 2026-10-20) say the trial gives "product-specific free units ... instead of a dollar-based balance." Source: twilio.com/docs/usage/trials, checked October 2026.
| Trial rule | What it means for your app |
|---|---|
| 100 free SMS | Enough for a demo, not for a beta with real users |
| 100 WhatsApp, 75 voice minutes, 40 Verify | Separate pools. Unused SMS units do not move to voice |
| Expires after 30 days | A slow build can outlast the trial |
| No credit card | Easy to start |
| Body must be a template ID | You cannot send your own text |
| Verified numbers only, up to 5 | You cannot text a tester you have not verified |
| Sign-up country only | No international test sends |
| Shared trial number | The sender is not a number you keep |
One conflict exists. Twilio's signup credits page still says "$15 free credits preloaded." The trial docs are newer and describe free units. Treat the docs as current. The same signup page also says trial texts begin with "Sent from a Twilio trial account." The new trial docs do not mention that prefix.
Why can't I send my own message text on a Twilio trial?
During the trial, the body field takes a template ID, not free text. Twilio lists templates such as sms_2fa, sms_appointment_reminders and sms_order_confirmation. The docs state: "Custom message bodies are not supported." Source: twilio.com/docs/usage/trials/try-out-sms, checked October 2026.
This matters for AI-built apps. An AI app builder writes code that sends a message like "Hi Sam, your table is ready." On a trial account, that body is not a valid template. So the generated code looks correct and still fails. You test Twilio's template, not your product's message.
Why does Twilio only text verified numbers?
Trial accounts can only send to numbers you verify first. The limit is 5 verified numbers per account. SMS and calls only go to your sign-up country, and the SMS trial page says "verified US numbers." Messages leave from a shared trial number. Sources: the two trial pages above, checked October 2026.
So you can text yourself and a few teammates. You cannot send a code to a beta tester, a client or a friend who signs up through your app. Each new person needs a manual verification step in the Twilio console first.
What is Twilio error 21608?
Error 21608 reads: "Upgrade and create an approved primary compliance profile to reach unverified numbers." Source: twilio.com/docs/api/errors/21608, modified 2026-08-17, checked October 2026.
Many people expect the error to stop after they add a card. It does not always stop. The error now also applies to upgraded accounts that do not have an approved primary compliance profile. An upgrade alone does not unlock unverified numbers. You also need that profile approved.
What changes after you upgrade Twilio?
An upgraded account removes the template rule and the 5-number limit. It adds costs and setup:
- Per-message pricing. Each message segment has a price, and carrier fees can apply on top.
- Number rental. You rent a phone number every month.
- Compliance profile. You need an approved primary compliance profile to reach unverified numbers (error 21608 above).
- Sender registration. Some countries require you to register your brand and use case before carriers deliver your traffic. Registration needs a paid account and can take days.
For the full cost math, read the Twilio pricing breakdown. For a side by side with current prices, see textbee vs Twilio.
How do you test SMS today without these limits?
textbee sends SMS from your own Android phone. You install the app on a phone with a SIM, pair it with your account, and call the API. The message leaves from your SIM's number. So you can text any number your phone plan can reach, with any message text.
What you need:
- A textbee account. The free plan has no card step.
- The textbee Android app on a phone with a SIM. See setting up textbee.
- An API key from the dashboard. See API keys.
Then send with one HTTP call:
curl -X POST https://api.textbee.dev/api/v1/gateway/send-sms \
-H "x-api-key: $TEXTBEE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"recipients": ["+12015550123"], "message": "Hi Sam, your table is ready."}'The same call from a server function in JavaScript:
const res = await fetch('https://api.textbee.dev/api/v1/gateway/send-sms', {
method: 'POST',
headers: {
'x-api-key': process.env.TEXTBEE_API_KEY,
'Content-Type': 'application/json',
},
body: JSON.stringify({
recipients: ['+12015550123'],
message: 'Your login code is 482913',
}),
})
if (!res.ok) throw new Error(`textbee returned ${res.status}`)Keep the API key on the server. Never put it in browser code. Replies come back to your phone, and your app reads them through a webhook or GET /gateway/messages. The sending SMS docs cover the full request.
Twilio trial vs Twilio upgraded vs textbee
| Twilio trial | Twilio upgraded | textbee | |
|---|---|---|---|
| Who you can text | Up to 5 verified numbers, sign-up country only | Any number, after compliance profile approval | Any number your SIM plan can reach |
| Message text | Template ID only | Your own text | Your own text |
| Setup before first send | Sign up, verify each recipient | Card, compliance profile, number rental, sender registration in some countries | Sign up, install the app, pair the phone, create a key |
| Cost | 100 free SMS, 30 days | Per-segment price plus carrier fees plus number rental | Free: $0, 300 a month, 50 a day. Pro: $14.99 a month for 5,000 |
| Sender recipients see | A shared trial number | A number you rent | Your own phone number |
| Replies | Not covered in the trial docs | To your rented number, through a webhook | To your phone, through a webhook or the messages endpoint |
textbee prices are from the pricing page, checked October 2026. textbee charges no per-message fee. Each text uses your phone plan, which on an unlimited plan costs nothing extra.
When should you use Twilio instead?
Use Twilio for high volume. A textbee phone sends roughly 10 to 15 messages a minute. That covers login codes, confirmations, reminders and alerts for most new apps. It does not cover a blast to 50,000 contacts in an hour.
Use Twilio when you need carrier-grade throughput, a short code, or a rented sender in many countries at once. Twilio is built for that scale.
Use textbee while you build, and for production when your traffic is transactional and your volume fits a phone. Many apps stay there. When an app outgrows one phone, add more devices on Pro (up to 5), or move the send function to a cloud provider. The change is one function in your code.
How do you add SMS to an app you build with AI?
The build with AI page shows the full flow. Each guide gives a prompt to paste into the builder, where to store the key, and how to receive replies:
Each builder writes a server function that calls the send endpoint above. You save the textbee key as a secret, and the builder never puts it in the browser.
Frequently asked questions
Does the Twilio trial still give $15 in credit?
Twilio's signup credits page still says "$15 free credits preloaded." The trial docs, modified 2026-10-20, describe free units instead: 100 SMS, 100 WhatsApp, 75 voice minutes and 40 Verify. The docs are the current source.
Can I send a custom message on a Twilio trial?
No. During the trial, the message body must be a template ID such as sms_2fa, sms_appointment_reminders or sms_order_confirmation. Twilio states that custom message bodies are not supported.
How many numbers can I verify on a Twilio trial?
Up to 5 per account. They must be in your sign-up country.
Does upgrading Twilio fix error 21608?
Not alone. The error now also applies to upgraded accounts without an approved primary compliance profile. You need the upgrade and the approved profile.
Is textbee free for testing?
Yes. The free plan gives 300 messages a month and 50 a day on 1 device, with no card. Pro costs $14.99 a month for 5,000 messages and up to 5 devices.
Can my textbee test code move to production?
Yes. The same endpoint and key work in production. Your app keeps sending from your own number, and recipients reply to the same thread.
Do I need a Twilio account to use textbee?
No. textbee is a separate service. You need a textbee account, an Android phone with a SIM, and an API key.
Get more textbee in Google Search
Add textbee.dev as a preferred source. Our posts show up more often in your Google results.
You may also like

9 Cheaper Twilio Alternatives for SMS, With Real US Prices (2026)
Nine cheaper Twilio alternatives for SMS with real US prices: Telnyx, Plivo, Bird, Bandwidth, Vonage, Sinch, AWS SNS, ClickSend and textbee.

Twilio SMS Pricing 2026: The Real Monthly Cost (With Hidden Fees)
Twilio US SMS pricing, checked October 2026: $0.0083 a segment plus $0.0035 to $0.005 carrier fees, number and 10DLC costs, and real monthly totals.

Best Free SMS Gateway in 2026 (No Monthly Fee, No Credit Card Trap)
Honest comparison of free SMS gateway options in 2026: textbee, Twilio trial, Vonage demo mode, AWS SNS, TextBelt, and more. What's actually free vs what's a trial disguised as free.