Send Email to Phone Number: What Still Works and What Broke
Yes, you can still send an email to a phone number, but only through a carrier gateway address, and only on carriers that still run one: AT&T shut its own down on June 17, 2025. The gateway is a translation layer, not a channel. Understand which carrier still speaks it and the rest of the decision makes itself.
Most guides treat the gateway as a permanent fixture. It is closer to a deprecated API that nobody announced a sunset date for. That single framing change is the difference between a workflow that survives the next carrier policy shift and one that dies on a Tuesday morning with no warning email.
What the Email-to-Text Gateway Actually Sends
An email-to-text gateway is a carrier-hosted address that converts an inbound email into a text message on the recipient’s phone. The address is the carrier’s, not the recipient’s, which is why the same person has a different gateway address on every network they have ever used. Verizon documents the shape of it plainly: you send a text or image via email to a mobile number address such as 5555555555@vtext.com or 5555555555@vzpix.com (Verizon).
The reader-visible behavior is almost identical to a normal SMS, which is exactly what makes the gateway seductive. You type in Gmail, the recipient gets a text. No app, no opt-in record, no platform fee.
What the address does not do is anything a business needs at volume. There is no delivery receipt that means anything, no conversation history tied to a customer record, and no way to know whether a given number is on a carrier that still honors the address. Sending text through a carrier gateway is a convenience for a person, not infrastructure for a team.
Carrier Behavior You Can and Cannot Count On
Not every carrier treats the gateway the same, and the differences are the whole story. Verizon still operates one; AT&T retired its own outright. That split is not a temporary operational hiccup. It is the shape of the category.
- Still supported (as of 2026): Verizon’s email-to-text and text-to-email addresses, including the vtext.com and vzpix.com domains.
- Retired: AT&T’s email-to-text and text-to-email service, shut down on June 17, 2025 (AT&T).
- Unclear: plenty of regional carriers and MVNOs that never published a policy either way.
The mistake is treating “still supported” as “supported for you.” Verizon is direct about scope: legacy email-to-text is intended for low-volume consumer use only and is not intended for commercial or emergency purposes. Read that sentence twice. It rules out the two use cases a business is most likely to reach for it: reaching customers at scale, and reaching anyone when something has gone wrong.
If you are trying to reach a list rather than a single person, reaching a list without a group thread is a different problem with a different toolset. The gateway was never built for it.
| Carrier | Gateway address style | Status | Published scope |
|---|---|---|---|
| Verizon | number@vtext.com, number@vzpix.com | Active | Low-volume consumer use only |
| AT&T | (was number@txt.att.net) | Retired June 17, 2025 | No longer available |
Sending One by Hand, Step by Step
If you need to push a single message to a single phone today and the number is on a carrier that still runs a gateway, the mechanics are short. The order matters more than people expect.
- Confirm the recipient’s carrier. Ask them. There is no reliable public lookup, and guessing produces a message that vanishes silently.
- Look up that carrier’s gateway domain. Verizon’s is vtext.com for SMS and vzpix.com for MMS, both documented on the carrier’s own help pages.
- Compose the message in your email client, addressing it to the ten-digit number followed by @ and the gateway domain.
- Keep the total at 160 characters or fewer. That count includes the subject line and the recipient’s email address itself.
- Send it, then confirm with the recipient that it arrived. The gateway gives you nothing back.
That last step is not paranoia. It is the only delivery signal you will get.
There are threading quirks on an iPhone when you try to move the reply back into Messages, and they show up on the receiving end where you cannot see them. If the recipient replies to your gateway message, the reply lands in their carrier’s SMS interface, not your inbox, unless they know to text your email.
How the Gateway Converts Your Message
Underneath, the gateway is a mail server bolted to an SMS submission path. Your email arrives at a carrier-controlled SMTP endpoint, the carrier parses out the plain-text body, and it hands the remainder to the same system that processes a normal text.
The parsing is where messages die. HTML gets stripped. Attachments cannot ride along as attachments, so a photo becomes a link the recipient has to tap, and a business signature with a link in it usually eats the entire character budget before your actual sentence starts. Verizon’s rule is explicit: a text sent from email to a Verizon mobile number must be 160 characters or less, including the subject line and the recipient’s email address (Verizon Support). Do the arithmetic on your own signature block and you will see the problem immediately.
There is also a long-running oddity in the other direction. Moving a text into an email account means routing replies back to an inbox through a path nobody controls, which is why sending text from a phone and receiving it in email rarely produces a clean thread. The conversion runs one way at a time, with no session state.
The carriers themselves have shown how little they owe this path. AT&T repeats that on June 17, 2025 its email-to-text and text-to-email service was shut down. Any workflow built on a gateway address is running on a host’s goodwill.
Where Hand-Sent Messages Break Down
Hunting for a gateway domain you never verified is the first place people lose time. They find an old forum post, guess the suffix, send the message, and get silence back. The failure mode is indistinguishable from a message that simply has not arrived yet, which means people keep waiting instead of fixing it.
Reaching for the gateway when the number belongs to a business is the second. Gateway addresses route to a mobile handset, not a company switchboard. If the phone is a landline or a VoIP line, the message is gone, and you will not get a bounce that says so.
Treating the character limit as a guideline rather than a hard truncation is the third. Verizon’s 160-character ceiling is enforced before the message is built, not after, so everything past the limit simply does not exist on the receiving end. A confirmation number, a time, or an address is exactly the kind of content that gets cut. If your message has to be cut, it is the wrong channel for the content.
Finally, the gateway is a dead end for anything that needs a record. There is no log you own, no way to prove what was sent, and no way to route a reply back into a system that can act on it. For one-off personal messages, that is fine. For customer communication, it means the conversation exists only on someone else’s phone, and routing replies back to an inbox is the only version of this that scales.
When a carrier retires an endpoint, every workflow pointed at it stops at the same moment, and there is no migration path except a new channel. That is not a reason to panic if you send the occasional text by hand. It is a reason to stop building anything durable on the gateway.
If customer messages need to land in a shared place your team can see, search, and answer, texting through a platform built for it beats a gateway address that may or may not exist next quarter. That means carrier connections we maintain directly through Twilio and Telnyx, with MMS support, plus a shared inbox where every reply stays attached to the conversation it belongs to. We keep a free plan and a free trial open, and you can see what fits at our contact page.
Frequently Asked Questions
Can you send an email to a cell phone number?
Yes, on carriers that still run an email-to-text gateway. You address the message to the ten-digit mobile number plus that carrier’s gateway domain, and the carrier converts it to an SMS. Verizon publishes vtext.com and vzpix.com as its gateway domains. AT&T’s equivalent stopped working on June 17, 2025, so a message sent to an AT&T number that way will not arrive. Always confirm the recipient’s carrier and message length before sending.
How can I send an email to a phone number?
Confirm the recipient’s carrier first, because the gateway address depends entirely on it. Then compose the message in any email client, address it to the number followed by @ and that carrier’s gateway domain, and keep the whole thing under 160 characters. Send it and follow up with the recipient, since the gateway returns no delivery confirmation. If you cannot establish the carrier, the message has no reliable destination.
How do I forward an email to a phone number?
Forwarding adds a layer that frequently breaks the character budget. The forwarded content includes the original subject line and often a quoted message, and all of that counts against the same 160-character cap. Strip the forwarded headers, delete the quoted thread, and reduce the body to the one or two sentences that matter, or the carrier will truncate it before the recipient reads it. When the content matters, convert it to a direct text message instead.
How do I Gmail to a phone number?
There is no phone-number field in Gmail. You send the message to the gateway address, which looks like an ordinary email address: the recipient’s ten-digit number, an at sign, and the carrier’s gateway domain. Gmail treats it like any other address and delivers it to the carrier. Everything else is dependent on the carrier still honoring that domain, which is exactly the part you cannot verify from inside Gmail.