Microsoft Teams
Yep. We built you an SMS integration for Microsoft Teams.
Send and receive SMS or MMS from your Teams chats. touchSMS for Teams is a great way to stay on top of support, marketing or customer service, since inbound SMS and replies route to the team or chat of your choice. Once installed, Send SMS shows up in your message extensions.
ON THIS PAGE
About the Microsoft Teams integration
touchSMS for Teams
You can send and receive SMS or MMS from your Teams chats with the touchSMS for Teams app. It is a great way to stay on top of support, marketing or customer service queries, as inbound SMS and SMS replies are routed to the team or chat of your choice. Once touchSMS for Teams is added to your Microsoft Teams profile, the option to send SMS will appear in your Message Extensions.
Why use SMS in Teams?
Teams is where the internal conversation happens. Adding SMS routes the external conversation into the same place, so support, sales or ops teams stop juggling apps and start working the whole customer thread from one place. Every SMS is threaded, searchable and visible to whoever the channel is shared with.
- One-touch connection
- Send and receive SMS from collaborative Teams chats
- Send and receive SMS privately from the touchSMS app in Teams
- Send and receive MMS with a virtual number
- Schedule SMS for later delivery
- SMS conversation threading in Teams chats
- Create contacts and groups
- Save templates for quick sending
- Notifications for inbound SMS
Virtual number for the full experience
A virtual number is required for the optimal experience in Teams, since it gives you a persistent inbound address for replies and unlocks MMS. Attach one to your touchSMS account before you install the Teams app and everything is wired up on first use.
Need a shared inbox? Meet emu.chat
touchSMS for Teams is built for one-way and one-person sending: alerts, notifications, 2FA and verification codes, reminders, or a single user who sends the occasional text. If more than one person needs to see the conversation, emu.chat is the one you want. It is built by the same Australian team behind touchSMS, on the same carrier-grade infrastructure, and adds the shared-inbox layer a customer-facing team actually needs. Pin a shared inbox to any Teams chat, channel or team and the conversation lives where the work does: inbound messages land in context, replies happen in the thread, and every message stays in one history your whole team can see.
- Shared inboxes: assign, hand off, add internal notes and archive
- AI in every thread: summarise, draft, shorten or rewrite a reply
- Azure AD / Entra ID and Outlook contacts synced in
- Microsoft SSO: sign in with your existing 365 account
- AU virtual number included, or port your existing 04xx mobile
- Pin inboxes to channels, or skip Teams and use the web app
- Compliance built in: Spam Act, DNCR, automatic opt-outs and an audit log
Which one do you need?
The short version: if more than one person ever needs to see a reply, choose emu.chat. Sales desks, support queues, bookings, dispatch and accounts teams all fit here. If you only need alerts, 2FA codes or a single sender, touchSMS for Teams is the pay-as-you-go option with no seat subscription. You can start on touchSMS for Teams and move to emu.chat later, keeping your number. Compare both options.
- emu.chat: from $15 per user per month (ex GST), minimum 3 users, with 100 SMS per user pooled across your organisation and one AU virtual number per 3 seats
- emu.chat: 14-day free trial with 25 SMS credits and an Australian test number, no credit card
- touchSMS for Teams: pre-paid credits from 5c per SMS (ex GST), no seat subscription
- touchSMS for Teams: a virtual number is required to send and receive, at $15 per month (ex GST) on top of credits
- touchSMS for Teams: fully self-serve, with scheduling and templates, but no shared inbox, AI, SSO or directory sync
Built and supported in Australia
Both products are built and supported in Australia by the same team. touchSMS is an ACMA-certified telco with direct local carrier routes. Australian customer data is stored in AWS Sydney and never leaves the country, and support is Sydney-based on a real phone number. One standard SMS contains up to 160 GSM basic characters; SMS beyond an included pool is billed per message.
Bigger rollouts
For teams sending tens of thousands of messages a month, or running multiple brands on different sender IDs, we offer volume pricing, SAML SSO, SCIM provisioning, an audit log API, a security documentation pack and a dedicated Australian customer success manager. Talk to us about your rollout.
Microsoft Teams + touchSMS, feature by feature
One-touch connection
Add the app to your Teams profile and Send SMS shows up in the message extensions.
Team or private
Send and receive SMS in collaborative Teams chats, or privately from the touchSMS app in Teams.
SMS + MMS
Send and receive MMS from a virtual number.
Schedule and template
Schedule SMS for later, save templates for quick sending, and thread conversations in Teams.
Contacts and groups
Create contacts and groups so your team can share the same address book.
Where teams put it to work
Customer support
Route inbound SMS into the support channel and let the whole team pitch in.
Sales chase
Follow up hot leads over SMS from the sales channel.
Internal broadcasts
Text on-call, roster, or ops updates from Teams to the crew's phones.
Connect Microsoft Teams in minutes
The setup is quick: create your touchSMS account, grab an API key, and follow the prompts in the Microsoft Teams app. Most teams are sending inside a lunch break.
- 01Create a touchSMS account and add credits.
- 02Download and install the touchSMS for Teams app.
- 03Connect it in about two minutes.
- 04Start sending SMS straight from Teams.
Microsoft Teams integration, common questions
Do I need a virtual number?+
A virtual number is required for the best experience in Teams, especially for inbound and MMS.
Can multiple channels use touchSMS?+
Yes. Route inbound and outbound to specific channels or keep them private to a user.
Do we need a Microsoft Teams licence for emu.chat?+
No. emu.chat ships as both a Teams app and a standalone web app, so use whichever your team prefers. Microsoft SSO is included either way, so people sign in with their existing 365 account.
Can we keep our existing business number?+
Yes, as long as it is an Australian mobile. We port 04xx mobiles in 5 to 15 business days with no service interruption. 13, 1300 and 1800 service numbers are not supported yet.
What about the Spam Act and opt-outs?+
Built in. We are a registered Australian telco and fully ACMA compliant. Every send is checked against your do-not-contact list and global suppression, and STOP, UNSUBSCRIBE, OPT OUT and their variants are honoured automatically, with a full audit log per number, per send.
Is it for sales or support?+
Both. Many customers run a sales inbox and a support inbox on separate numbers with different routing rules, and you can set per-team office hours and out-of-hours auto-replies.
Where does our data live?+
Australian customer data is stored in AWS Sydney (ap-southeast-2) and never leaves the country. We use direct carrier connections in Australia, plus tier-1 routes for international SMS.
What if we start on touchSMS for Teams and outgrow it?+
Move to emu.chat whenever you like and keep your number. It is the same company, infrastructure and Sydney support team; you are just adding the shared-inbox layer on top.
Ready to bring SMS into Microsoft Teams?
10 free credits · no card · cancel anytime