Live chat solves the problem it was built for. A customer arrives, an agent answers, and the issue closes inside the same session. During staffed hours it is the fastest channel a support team has.
Then the shift ends. The widget switches to offline mode, messages fall into a queue, and the customer waits until morning. Most teams accept that gap because the alternative used to cost money.
It did not always. Until 2025, there was a free way to reach a customer after hours, and a lot of support teams used it without thinking of it as a tool. This article covers what it was, why it stopped working, and what teams use now.
What happens after the chat widget goes dark?
The coverage gap is not a failure of chat. It is a limit of any staffed channel.
The hours nobody is watching
A customer who starts a chat at 8pm sees an offline form. They type the question anyway, and it lands in a queue that opens at nine the next morning. By then the urgency has usually passed, one way or the other.
For most questions that is fine. For a failed payment or a cancelled booking, thirteen hours is long enough for the customer to give up and contact someone else.
How teams used to bridge it
The workaround was simple. An agent or an automated rule sent an email to a specially formatted address, and the customer received a text on their phone. No app, no subscription, no procurement request.
Teams used it for the small number of after-hours messages that genuinely could not wait until morning. It was never a channel strategy. It was a stopgap that happened to work.
The gateway that closed without an announcement
Every major US carrier ran an email address format tied to mobile numbers. Because anyone could send through them without registering, spammers used them at scale, and carriers closed them in response. Support teams looking for alternatives to VText and the equivalent AT&T and T-Mobile addresses are usually doing so because a workflow broke, not because they went shopping for a new tool.
What broke and when
- T-Mobile: The @tmomail.net gateway began failing in December 2024 and has not been restored.
- AT&T: Closed @txt.att.net and @mms.att.net on 17 June 2025.
- Verizon: Started phasing out @vtext.com in late 2024, with full shutdown scheduled for March 2027. Delivery is already close to zero.
Why nobody noticed straight away
A rejected email produces a bounce. A closed carrier gateway produces nothing at all. The message shows as sent, sits in the sent folder, and never arrives.
For a support team, that failure mode is the worst possible one. The ticket looks handled. The customer heard nothing. Nobody finds out until a complaint arrives days later, and by then the connection to a broken channel is easy to miss.
Which after-hours messages actually need a text?
Text is a narrow channel, and it works because it is narrow. Sending everything through it destroys the thing that makes it useful.
Messages that cannot wait until morning
A short list covers most of it. A payment that failed and will retry overnight. A booking cancelled by the business rather than the customer. A delivery arriving in a window the customer needs to know about now.
These share one trait. The information expires. Read tomorrow; it is no longer useful, and the customer has already been affected by not having it.
What should stay in the queue
Anything that needs detail, formatting, or an attachment belongs in email or the ticket. Refund explanations, troubleshooting steps, and account documentation all read badly on a phone screen and lose context when compressed.
The general rule is straightforward. If it is short and expires overnight, text it. If it needs reading properly, leave it for the morning queue.
Most teams find the after-hours list is shorter than expected. Once you separate what genuinely expires from what merely feels urgent, the volume drops to a handful of messages a month rather than a nightly routine.
What support teams are using now
Three replacements have taken over, and they suit different team sizes.
On-call and paging tools
Tools built for incident response handle escalation well. They rota, they retry, and they log everything. They are designed to reach staff rather than customers, which limits them for support use.
If the after-hours message is going to an on-call colleague, these fit. If it is going to the customer waiting on an answer, they are the wrong shape.
SMS platforms built for campaigns
Platforms including SimpleTexting and EZ Texting provide dashboards, contact lists, and scheduling. They are strong products for teams sending promotional messaging at volume.
A support team sending nine after-hours messages a month uses almost none of that. The monthly cost buys campaign features to send a sentence that reads, 'Your delivery is arriving between two and three.'
Registered email-to-text services
This category works the way the old gateways did. An email goes out, a text arrives, and the reply comes back to the inbox rather than stranding on someone's phone.
That return path matters more for support than for most teams. According to Statista, text messages carry open rates above 95%, so a reply is likely, and it needs somewhere the whole team can see it.
This is not SMS marketing. There are no campaigns, no subscriber lists, and no automation sequences. It handles one message to one customer about one issue.
What to check before you switch
Three things separate a replacement that keeps working from one that fails the same way.
10DLC registration
This is the US standard for business texting, and it requires the business to register before sending. Without it, carriers filter the messages, which is the same filtering that closed the free gateways. Registration usually completes in one to two business days and needs details the business already holds.
Delivery confirmation
The service should report whether each message was delivered or failed. Silent failure was the original problem. A replacement that repeats it leaves the team no better off.
Shared team access
Support runs in shifts, so no channel should depend on one person's device. Replies need to reach a place the next shift can pick up without asking anyone.
Chat for the session, text for the gap
Nothing here replaces live chat. Chat handles the conversation while the customer is present and engaged, which is the bulk of support work and the part that closes issues fastest.
Text covers the hours when nobody is there. It is a handful of messages a month for most teams, and it exists so a customer with an expiring problem is not left waiting until nine.
If your team still sends to a carrier address, the check takes two minutes. Search your sent folder for txt.att.net, vtext.com, and tmomail.net. Anything recent did not arrive.
Worth checking your automation rules too. Helpdesk triggers and escalation workflows often hold those addresses from years back, and they fail as quietly as anything an agent sends by hand.
