Every tool below already sends email notifications. Point them at +1[phone]@sendemailtotext.com and the emails arrive as SMS. No plugin, no webhook, no developer.
Every one of these tools has an email recipient field somewhere in its alert or notification settings. Paste the TextBolt gateway address there. That’s the integration.
Outlook Mobile Service is retired and the carrier gateways (vtext.com, txt.att.net, tmomail.net) have shut down. TextBolt slots in on top of Outlook and turns any email into a 10DLC-compliant SMS. Six challenges IT admins, on-call engineers, sales reps, and dispatchers hit when they need SMS from Outlook.
Outlook used to convert emails to SMS through the legacy Outlook Mobile Service. Microsoft retired that feature, and Microsoft 365 Q&A threads like “Sending SMS messages through email no longer working” capture the resulting gap. Outlook desktop, Outlook on the web, and the Outlook mobile app handle email reliably, just without a built-in SMS sender. TextBolt slots in on top of any of those Outlook surfaces, so the email you already send becomes a 10DLC-compliant SMS.
AT&T retired txt.att.net in June 2025. T-Mobile took tmomail.net offline in December 2024. Verizon’s vtext.com shutdown completes by March 31, 2027. Any business that pasted [phone]@vtext.com into the Outlook To: field has broken alerts and notifications today. Carriers killed these free gateways to fight spam and meet 10DLC rules, leaving Outlook users with silent message failures and no replacement path back to recipients.
Even when gateways worked, Outlook users had to know each recipient’s carrier (different domain per carrier), accept a 140-160 character cap, and watch messages arrive from an unknown number recipients ignored. Batch sending was impractical because every recipient needed a different gateway address. Carriers aggressively filtered links and shortened URLs, and silent bounce-backs left senders unaware of failures.
The FCC requires US business SMS to be registered through The Campaign Registry. Carrier gateways from Outlook offer no sender authentication, no consent record, no timestamped delivery log, and no exportable audit trail aligned with Exchange retention policies. Compliance officers running eDiscovery, finance audit, or healthcare documentation lose SMS as a logged channel.
Microsoft Q&A threads like “i cannot send SMS or MMS messages from Outlook” highlight broken inbound replies. Carrier gateways routed replies inconsistently. Some carriers used do-not-reply addresses, some dropped replies silently, and some bounced unrelated. A lead replying to a sales rep, a customer replying to a finance analyst, or a technician replying “ETA 20” to a dispatcher had no reliable path back to the original sender’s Outlook inbox.
The Microsoft-recommended SMS path is a Power Automate flow that calls the Twilio connector. It requires Power Automate Premium licensing, a Twilio account with API keys, and a webhook setup for inbound replies (the Twilio connector has no listener trigger). Add Twilio per-seat licensing and audit logs scattered across Power Automate, Twilio, and individual Microsoft 365 mailboxes.
TextBolt connects Outlook to a registered 10DLC business number so any email you compose becomes an SMS. Microsoft 365 stays where it is; SMS capability gets added on top, with no Power Automate Premium and no Twilio account required.
Compose an email in Outlook desktop, Outlook on the web, or the Outlook mobile app. Address it to +1[phone]@sendemailtotext.com, hit send. The recipient’s phone gets an SMS in seconds from your toll-free business number. Same workflow on every Outlook surface.
TextBolt registers your sender identity with The Campaign Registry during onboarding. SMS routes through carrier-approved 10DLC infrastructure, not retired email gateways. Up to 98% delivery rate, professional toll-free number, no spam-folder filtering on the recipient side.
When the recipient texts back, the reply lands as an email in your Outlook inbox, threaded with the original message. The whole front desk, on-call rotation, dispatch team, or sales team sees the response and can reply by sending another email. No Power Automate webhook to maintain.
Standard plan ($49/month) and Professional plan ($99/month) include multi-user access for up to 10 team members on one shared account. IT admins, on-call engineers, sales reps, finance analysts, and dispatchers in your Microsoft 365 tenant all send SMS from Outlook using the same business number, with no per-seat fees.
Each SMS is logged with timestamp, sender, recipient phone, delivery status, and reply thread. Export logs for Exchange-aligned compliance documentation, eDiscovery, dispute resolution, or finance audit. Full history sits in your TextBolt account, ready for the legal or compliance team.
TextBolt is email-based. There is no Power Automate flow to build, no Twilio account to bill, no integration code to maintain, and no webhook endpoint to monitor. If your Microsoft 365 team can send an Outlook email, your team can send an SMS. Same for any system that already emails Outlook.
Up to 98%
SMS Delivery Rate
Two-Way
SMS Replies to Your Inbox
Carrier-Grade
Routes & Infrastructure
Up to 10
Team Members on Shared Account
Hands-on setup takes around 30 minutes. TextBolt handles 10DLC business verification with The Campaign Registry on your behalf in parallel. No Power Automate flow, no developer, no IT-admin training session
Create your TextBolt account using your Microsoft 365 work email. Account creation takes about 2 minutes. The account ties to your domain so you can add coworkers later.
Pick a dedicated toll-free number for outbound SMS. One-time $45/year setup fee. The number stays yours and is the sender ID on every SMS the team sends from Outlook.
Provide your legal business name, EIN, website, and SMS use case during onboarding. The FCC requires every US business sender to register with The Campaign Registry, and TextBolt files this on your behalf. Verification typically clears in 24-48 hours. Once approved, your toll-free number is enabled for compliant business SMS from Outlook.
Open Outlook desktop, web, or mobile. New email, address it to +15551234567@sendemailtotext.com with the recipient’s actual phone number, write your message, hit send. The SMS arrives in seconds.
If your Microsoft 365 environment already emails alerts, point those senders at the TextBolt gateway. Alerts from Azure Monitor, Datadog, Salesforce, Dynamics 365, ServiceNow, or any system that sends email become SMS automatically.
Add coworkers from your tenant to the shared TextBolt account. Each person sends from Outlook using the same business number. Replies arrive in the Outlook inbox of whoever sent the original SMS.


Open Outlook desktop, Outlook on the web, or the Outlook mobile app. Click New Mail, address to +1[phone]@sendemailtotext.com, type your message, hit send. The body of the email becomes the SMS body. Subject line is optional and prepended if filled. Replies thread back to your Outlook inbox.

Tools that already email your Microsoft 365 inbox (Azure Monitor, Datadog, Grafana, Salesforce, Dynamics 365, ServiceNow, Stripe, Zendesk) can email the TextBolt gateway directly instead. Each notification email becomes an SMS automatically. No Power Automate flow, no Twilio webhook, no integration code.

For systems you cannot reconfigure, set up an Outlook rule or Exchange Online transport rule to auto-forward matching emails to +1[phone]@sendemailtotext.com. Critical alerts that already arrive in Outlook get converted to SMS without touching the source system. Useful for vendor-locked monitoring tools, locked-down ERPs, and legacy line-of-business apps.
Six common Microsoft 365 workflows where Outlook-to-SMS replaces a Power Automate flow, a per-seat Twilio license, or a dead carrier gateway. Each links an Outlook inbox to an SMS-receiving phone in seconds.
Configure Azure Monitor, Datadog, Grafana, Nagios, or ServiceNow to send alert emails directly to the TextBolt gateway address (alongside your Outlook inbox if you want a record). On-call SREs and infrastructure engineers get SMS the moment a server, deployment, or incident alert fires. No PagerDuty seat, no Power Automate flow.
Practices running Outlook for front-desk email send appointment reminders directly to patient phones. Or wire your scheduling tool (Acuity, Calendly, SimplePractice, Mindbody) at the TextBolt gateway. Patients confirm by reply text and the response lands in the shared Outlook inbox.
Configure Dynamics 365, Salesforce, HubSpot, or Pipedrive new-lead alerts to email the TextBolt gateway directly (in addition to your Outlook inbox). The sales rep gets SMS within seconds, replies before the lead cools, and the conversation logs back into the CRM email thread.
Configure Stripe, Chargebee, Dynamics 365 Finance, or Shopify to send payment failures, fraud flags, or order-status alerts directly to the TextBolt gateway (instead of, or alongside, your Outlook inbox). The finance or operations team gets SMS the moment something needs attention. No CPaaS subscription required.
Configure Zendesk, Freshdesk, Dynamics 365 Customer Service, or Jira Service Management to send high-priority ticket alerts directly to the TextBolt gateway. The on-call support lead gets SMS for SLA-breach risk, VIP customer escalations, or after-hours tickets, and the ticket alert still lands in Outlook for later review.
Dispatchers send job assignments from Outlook directly to technicians’ phones. Dynamics 365 Field Service, ServiceTitan, Housecall Pro, or Jobber email-based dispatch routes through TextBolt to SMS. Technicians reply by text to confirm arrival, and replies land in the dispatcher’s Outlook thread.

10DLC Compliant
Carrier Approved
Complete Audit Trail
Three common paths for adding SMS to Outlook, three different mental models. Carrier gateways are dead or dying. Power Automate plus Twilio is a developer integration. TextBolt is a gateway your existing Microsoft 365 stack already knows how to email.
Free, but ending
The historical workaround: address an Outlook email to [phone]@vtext.com or @txt.att.net. AT&T and T-Mobile are gone, Verizon ends in 2027. No compliance, unreliable replies, silent bounces.
Recommended
$49/month (Standard plan)
Email-to-SMS gateway built for Outlook and Microsoft 365 teams. Send from any Outlook surface to +1[phone]@sendemailtotext.com and the email becomes an SMS from your business number. Replies thread back into Outlook.
Premium licensing plus per-message billing
Build a Power Automate flow that calls the Twilio connector on Outlook email triggers. Powerful, but requires Power Automate Premium licensing, a Twilio account with API keys, and a separate webhook for inbound replies.
Three ways customers route SMS through Outlook with TextBolt: replacing the retired Outlook Mobile Service, skipping Power Automate flows, and giving Microsoft 365 teams a compliant SMS path.
The numbers that matter when adding SMS to an Outlook or Microsoft 365 workflow.
Up to 98%
SMS Delivery Rate
30 min
End-to-End Setup
$49/mo
Standard Plan, 10 Users
4.4★
Workspace Marketplace (493 reviews)
No. Microsoft retired Outlook Mobile Service, the legacy feature that converted Outlook emails to SMS. Modern Outlook desktop, Outlook on the web, and the Outlook mobile app have no built-in SMS sender. To send SMS from Outlook, the inbox needs a connection to an email-to-SMS gateway like TextBolt. Address an email to +1[phone]@sendemailtotext.com and the message arrives as an SMS from your business number.
After Microsoft retired Outlook Mobile Service, businesses used carrier email-to-SMS gateways (vtext.com, txt.att.net, tmomail.net) as a workaround. Those gateways have now shut down too: AT&T’s txt.att.net retired June 2025, T-Mobile’s tmomail.net went offline December 2024, and Verizon’s vtext.com shutdown completes by March 2027. TextBolt is the direct replacement: same email-driven mental model, but messages route through a registered 10DLC business number with up to 98% delivery rate and complete audit trails.
Sign up for TextBolt and complete onboarding (TextBolt handles 10DLC business verification with The Campaign Registry on your behalf). Once your number is approved, address any Outlook message to +1[phone]@sendemailtotext.com. The email becomes an SMS. There is no Power Automate flow to build, no Twilio account to bill, no integration code to maintain, and no webhook endpoint to monitor. If your team can send an Outlook email, your team can send an SMS.
Yes. TextBolt registers your sender identity with The Campaign Registry as part of onboarding so SMS sent from Outlook through TextBolt routes through carrier-approved 10DLC infrastructure. This satisfies FCC business SMS requirements and avoids the spam-folder filtering that hit unregistered carrier-gateway traffic. TextBolt is not HIPAA compliant; healthcare prospects with PHI requirements should contact sales for Enterprise options.
Yes. When the recipient replies to a TextBolt-sent SMS, the reply arrives as an email in the Outlook inbox of whoever sent the original message, threaded with the outgoing message when possible. Replies route reliably regardless of carrier, unlike the old gateway flows where some carriers used do-not-reply addresses or dropped replies entirely. No Power Automate webhook required.
Yes. Standard plan ($49/month) and Professional plan ($99/month) include multi-user access for up to 10 team members on a shared TextBolt account. IT admins, on-call engineers, sales reps, finance analysts, and dispatchers in your Microsoft 365 tenant all send SMS from their own Outlook using the same business number. There are no per-user fees inside the 10-seat cap. Enterprise plans support custom team sizes for larger organizations.
Yes. The TextBolt gateway address works from any Outlook surface: Outlook desktop (Windows or Mac), Outlook on the web, and the Outlook mobile app. The same applies to Outlook accounts inside Microsoft 365 commercial, education, and government tenants, as well as Outlook.com personal accounts. The recipient phone gets the same SMS regardless of which Outlook surface sent it.
Power Automate plus Twilio is a build-it-yourself integration. You need Power Automate Premium licensing, a Twilio account with API keys, a separate webhook flow for inbound replies (the Twilio connector has no listener trigger), and per-seat Twilio licensing for the team. TextBolt is a gateway, not a developer platform. Your Microsoft 365 stack emails the gateway and the email becomes an SMS. Replies come back to Outlook automatically. No flow to maintain, no integration code, no licensing stack to assemble.
Basic plan starts at $29/month for 500 SMS credits and a single user. Standard plan is $49/month for 1,000 credits with multi-user access for up to 10 team members on a shared account. Professional plan is $99/month for 2,500 credits with the same 10-user shared access. Enterprise plans cover 5,000+ credits with custom team sizes. There is a one-time $20 setup fee for the toll-free business number. Annual plans include a 20% discount.
About 30 minutes of hands-on configuration: account creation and toll-free business number selection, plus 24-48 hours for 10DLC business verification before your number goes live. You provide your legal business name, EIN, website, and SMS use case during onboarding, and TextBolt files the registration with The Campaign Registry on your behalf, since the FCC requires every US business SMS sender to be registered. Once carriers approve your number, your team can send their first SMS from Outlook in seconds. No Power Automate flow to author, no IT-admin training session.
Add SMS to Outlook Without Leaving Microsoft 365
Send compliant business SMS from any Outlook surface in about 30 minutes. Multi-user access, two-way replies in Outlook, audit-ready logs.