Send email. Receive text.
Turn emails into , , and alerts.
SMS & MMS: U.S. and Canadian numbers.
iMessage: All iPhones worldwide.
- Device monitoring
- Server & uptime alerts
- Security notifications
- Backup failures
- On-call paging
- Community meeting notices
Live Email-to-Text Demo
SMS supports 10-digit U.S. and Canadian numbers. iMessage supports iPhones worldwide. Free testing is limited to prevent abuse.
| Received | To | Message | From | Status |
|---|---|---|---|---|
| Loading… | ||||
Powerful email-to-text features, built right in
text.email does more than forward an email to a phone. It helps you route, schedule, protect, clean up, and respond to the alerts your team depends on.
Real-world ways people use text.email
Built for alerts, not marketing. Here are a few ways teams and individuals turn email into text notifications.
Why text.email exists
For years, the “easy” way to send a text from an alerting system was to email your phone through a carrier gateway: number@carrier-domain. That era of email-to-text is over.
5551234567@txt.att.net
5551234567@vtext.com
5551234567@tmomail.net
General FAQ
One account works well if you manage texting for all of the organizations and want a single point of billing with one credit card. This is a good fit when the same account settings apply to every organization and you are happy to manage their activity and reports together.
Create a separate account for each organization if they need to operate independently. Separate accounts let each organization use its own credit card, manage its own settings, and log in to see only its own messages and reports. Each account has its own billing and usage, so this is also the better choice when organizations need to pay their own bills or keep their activity private from one another.
Yes. The text.email API lets you send SMS, MMS, and iMessage alerts from your own apps and scripts. For most users, using the API isn't necessary. You can simply send an email to your text.email address to deliver a message to your phone, with no code or API integration required.
If you want to integrate the API, create an API key in Settings → API keys and see the API documentation for instructions and examples.
That counts as 5 messages, assuming one message is sent to each recipient. Usage is counted per recipient, even when your software sends the same notification to everyone in one email.
If a longer notification is split into multiple SMS messages, each part counts separately for each recipient. For example, a notification split into 2 SMS messages and sent to 5 recipients counts as 10 messages.
SMS and MMS use a sending number chosen for your delivery route, such as a toll-free number or a 10-digit long code (10DLC). That number can change if your routing changes.
iMessages come from the iMessage sender configured for your account or selected by the iMessage address you use.
Replies to iMessages sent through text.email are matched to the original message and forwarded by email.
For SMS and MMS, text replies are forwarded by email when you use our reply-enabled 888-number route. Other sending routes and anonymous SMS tests may not support replies.
+country-code-and-number@your-subdomain.i.text.email, using your account’s subdomain.
Or save the recipient in Settings → iMessage Numbers to keep using your existing email addresses.
The recipient’s phone number must have iMessage enabled. Explore email to iMessage.
Real feedback, straight from our users
From emails sent to our team and reviews posted on Trustpilot. Lightly edited for clarity.
