Texting for Microsoft Teams (SMS) Implementation
Texting for Microsoft Teams (SMS) Implementation lets your staff send and receive business text messages from their Teams work number instead of a personal phone. IT Partner picks the route that fits your estate — native SMS in Teams, which Microsoft supports only on Microsoft Calling Plan numbers in the United States, Puerto Rico and Canada, or a third-party texting app for Operator Connect and Direct Routing numbers — prepares and submits the 10DLC Brand and Campaign registration with The Campaign Registry from the Teams admin center, enables SMS on the in-scope numbers with a per-user policy, writes the opt-in, opt-out and content rules Microsoft's SMS policy holds you to, records a retention and eDiscovery decision, validates a pilot group, and hands over a one-page user guide and the PSTN and SMS usage report. $10 per user plus a $2,450 tenant fee, an estimate confirmed in a written quote, for about 2 weeks of our work — the calendar is set by registry approval, which nobody can promise.
What this engagement is
Customers text. Sales, service, dispatch and front-desk staff answer them — usually from a personal phone, because the business number in Microsoft Teams could not text. That creates two problems at once: conversations the company cannot see or keep, and employees handing out personal numbers. Since Microsoft's native SMS rollout, a Teams user with an eligible number can send and receive text messages in the same chat list they already use, on Teams desktop, web and mobile. The catch is that eligibility is narrow, the registration step is mandatory, and the compliance rules are real — which is exactly the work this engagement does for you. The first decision is the route, and it is dictated by how your numbers reach the phone network. Native SMS in Teams is supported only on Microsoft Calling Plan numbers — Domestic, Domestic and International, or pay-as-you-go — in the United States (including Puerto Rico) and Canada, on 10-digit long codes. Operator Connect and Direct Routing numbers, toll-free numbers, short codes and alphanumeric sender IDs are not supported natively, and the feature is one-to-one plain text: no MMS, no attachments, no group texting, no shared inbox. If that fits, we register your organization and its messaging use case with The Campaign Registry — the 10DLC Brand and Campaign every application-to-person sender to US numbers needs — submitted from the Teams admin center under Voice > Service configuration > SMS, then enable SMS number by number. If your numbers come through Operator Connect or Direct Routing, or you need MMS, group texting or a shared inbox, the route is a third-party texting app that runs inside Teams: CT Text for Teams from CallTower, Clerk Chat, YakChat, Teams Plus and Falkon SMS are current examples, and some operators sell their own SMS add-on. We compare them against your requirements without a preferred vendor; you license the app, we deploy and configure it. Whichever route, the same discipline applies. We check the Teams Phone prerequisites — licences, number types, and for pay-as-you-go Calling Plans the billing mechanism Microsoft requires before SMS can be used — scope who is allowed to text through the per-user policy, and translate Microsoft's SMS messaging policy into wording your teams can follow: consent before the first message, STOP and HELP handled correctly, content categories that are prohibited or carry extra requirements, and sensible quiet hours. Because Microsoft 365 does not, as of this writing, capture native Teams SMS in Purview retention or eDiscovery, we put the retention question in front of you deliberately rather than leaving it to be discovered in a dispute: for regulated firms the answer is usually third-party capture or an app with built-in archiving, and we configure whichever you choose. A pilot group then texts real customers before anyone else is enabled, and you receive a one-page user guide plus a walkthrough of the PSTN and SMS usage report in the Teams admin center. Who this is for: organizations already on Microsoft Teams Phone — or moving to it — whose staff need to text customers from the business number, from a 25-user department to multi-department rollouts across a mid-size or enterprise tenant (500 users and more are quoted per estate). Who it is not for: if Teams Phone is not deployed yet, start with Microsoft Teams Phone System Setup; if you are leaving RingCentral, 8x8 or Zoom Phone, see RingCentral, 8x8, or Zoom Phone to Teams Phone Migration; if you need texts routed through agent queues with reporting, that is a Microsoft Teams Contact Center Implementation; and day-to-day administration after go-live is the Managed Microsoft Teams Phone Service.
Success criteria
What you receive
How the work unfolds
Kickoff call to confirm who needs to text, why, and to whom. IT Partner inventories numbers by connectivity, country and type, checks licences and cloud environment, and delivers the route-selection document together with the compliance and retention questions for your decision.
Fix what the prerequisite check found (licences, pay-as-you-go billing, number types). Native route: collect the company data and submit the 10DLC Brand from the Teams admin center. Third-party route: confirm the app choice and your licence order.
Draft the Campaign (use case, samples, opt-in and opt-out) and submit it as soon as the Brand shows Approved; build the scoped per-user SMS policy; write the compliance kit; record the retention decision and configure the chosen capture option; deploy the third-party app to the pilot where selected.
Enable SMS on the pilot numbers (Microsoft says activation can take up to two hours), assign them, and run the pilot: two-way texts on desktop and mobile, the new-contact prompt, STOP and HELP, policy blocking for out-of-scope users, and a capture check where archiving was configured. Fix what the pilot finds.
Enable the remaining approved users and numbers, deliver the user guide, walk your administrators through the PSTN and SMS usage report and the as-configured settings, and close on your approval. Our work fits in about 2 weeks; if the registry takes longer, the pilot and rollout milestones move with it.
Prerequisites
Who does what
IT Partner
- Run the kickoff, inventory numbers and licences, and produce the route-selection document and the prerequisite check.
- Prepare and submit the 10DLC Brand and Campaign from the Teams admin center, track both to Approved, and resubmit with corrections if the registry rejects either.
- Enable SMS on the in-scope Calling Plan numbers, assign them, and apply the scoped per-user SMS policy.
- Write the compliance kit and the retention and eDiscovery decision record, and configure the capture option you choose within scope.
- Deploy and configure the third-party texting app for the pilot where that route is selected.
- Run the pilot against the success criteria, fix configuration issues within scope, and roll out to the remaining approved users.
- Deliver the user guide, the usage-report walkthrough and the administrator handover.
Your team
- Supply the company legal data for the Brand, and own the registrations: they are made in your name, describe your use case, and the registry's decisions and any registration or carrier charges are yours.
- Describe the texting use case, provide sample messages and confirm how consent is collected; have your counsel review the compliance kit.
- Decide the retention route and, where a third-party archiving or texting product is chosen, purchase its licence.
- Buy the Microsoft Calling Plan and Teams Phone licences, and set up the billing mechanism for pay-as-you-go plans; Microsoft's per-message and overage charges are billed to you by Microsoft.
- Grant administrator access, nominate the pilot users and test handsets, and make them available for validation.
- Enforce the texting rules after handover: staff conduct, opt-out handling and message content are yours to police, and Microsoft's policy lets it suspend SMS for a pattern of non-compliance.
- Review the deliverables and approve delivery, or report defects, within the schedule.
What's not included
Limitations & technical notes
Frequently asked questions
Can we send text messages from Microsoft Teams?
Yes, under conditions. Microsoft's native SMS in Teams works for users whose phone number is a Microsoft Calling Plan number in the United States, Puerto Rico or Canada, once your organization has an approved 10DLC Brand and Campaign and the number has been SMS-enabled in the Teams admin center. Texts then appear in the user's Teams chat list on desktop, web and mobile. If your numbers reach the phone network through Operator Connect or Direct Routing, native SMS does not apply and a third-party texting app connected to Teams is the route — this engagement covers either.
What does the implementation include?
A requirements and route-selection document; a Teams Phone prerequisite check; the 10DLC Brand and Campaign registrations prepared and submitted from the Teams admin center and tracked to approval; SMS enabled on the in-scope numbers with a scoped per-user policy; a compliance kit built from Microsoft's SMS policy; a written retention and eDiscovery decision with the chosen capture option configured; deployment of a third-party texting app where that route is chosen; a pilot; rollout; a one-page user guide; and a walkthrough of the PSTN and SMS usage report at handover.
How much does it cost?
$10 per user plus a $2,450 tenant fee — an estimate for typical scope, confirmed as a written quote before work begins; you pay after you approve delivery. Fifty texting users, for example, come to $2,950. Estates of 500 users and more are quoted per estate. Microsoft Calling Plan and Teams Phone licences, Microsoft's per-message and overage charges, third-party app or archiving licences, and any registry or carrier fees are billed by those vendors, not by IT Partner.
How long does it take?
About 2 weeks of IT Partner work: inventory, route decision, registrations submitted, policies and compliance kit built while the registry reviews, then enablement, pilot and rollout. The elapsed time depends on The Campaign Registry and the carrier reviewers — Microsoft's guidance at the time of writing is a few business days for each of the Brand and the Campaign, and rejected applications can take weeks to reprocess. We prepare clean submissions and track them, and we do not promise an approval date, for the same reason we do not promise number-port dates.
Our numbers are on Operator Connect or Direct Routing. Can we still text from Teams?
Not natively — Microsoft supports SMS only on Calling Plan numbers. The route is a third-party texting app that runs inside Teams and brings its own carrier connection: CT Text for Teams from CallTower, Clerk Chat, YakChat, Teams Plus and Falkon SMS are current examples, and some Operator Connect providers sell an SMS add-on for their numbers. These apps typically add MMS, group texting, shared inboxes and archiving that native SMS lacks. We compare candidates against your requirements without a preferred vendor, you license the one you choose, and we deploy and configure it. Moving the affected numbers to a Microsoft Calling Plan is also possible and is quoted separately.
What is 10DLC registration and why is it required?
10DLC is the US carriers' framework for business texting from ordinary 10-digit numbers. Every SMS from Teams is treated as application-to-person traffic, so before Microsoft will enable a number your organization needs an approved Brand (your verified legal identity: name, tax ID, address, website) and an approved Campaign (what you will text, sample messages, how people opt in and out) registered with The Campaign Registry. Both are submitted from the Teams admin center. We prepare and submit them and chase them to approval; the registrations are in your name, describe your business, and the registry's decisions and any fees are yours.
Which Teams apps can text — desktop, web or mobile?
All three, per Microsoft's documentation: text conversations appear in the chat list of the Teams desktop app, Teams on the web and the Teams mobile app, using the SMS-enabled number in the user's profile. The first inbound text from an unknown number asks the user to allow or decline it, which the user guide explains.
Can we send pictures, or text a group?
Not with native Teams SMS. It is one-to-one plain text: no MMS, attachments, emoji, stickers or GIFs, and no group messages or shared inboxes. If your use case needs any of those, the route-selection step will say so and point at a third-party app — we would rather tell you in week one than after registration.
Are our texts kept for eDiscovery or our regulator?
As of this writing, not natively. Purview retention and eDiscovery cover Teams chats and channel messages, but Microsoft 365 does not capture native Teams SMS, and the Teams admin center reports usage rather than content. For a broker-dealer, adviser or any firm with a books-and-records duty, that means choosing a capture option deliberately: a third-party archiving product that ingests the texts, or a texting app with built-in compliance archiving. We put the decision in writing, configure the option you choose, and prove it in the pilot. Broader regulated retention across Microsoft 365 is our FINRA and SEC 17a-4 Compliance service.
Does Microsoft charge per text?
It depends on the Calling Plan. Microsoft's Calling Plans include an SMS allotment pooled across the tenant and counted in message segments; beyond it, and for every message on a pay-as-you-go plan, Microsoft bills per segment plus carrier fees — which is why pay-as-you-go tenants must have Communications Credits or postpaid billing in place first. Those are Microsoft's charges and terms and can change; we point you to the current allotment for your plan during the prerequisite check, and none of it flows through IT Partner.
What are we allowed to text, and can Microsoft switch it off?
Microsoft's SMS messaging policy for Teams requires consent before you message someone, stops further traffic automatically when a recipient opts out, prohibits certain content outright, places extra requirements on categories such as alcohol, firearms, gambling and sweepstakes, and reserves Microsoft's right to suspend SMS for a customer showing a pattern of non-compliance. Add the TCPA and CTIA norms — honor any reasonable opt-out, respect quiet hours — and you have the compliance kit we hand you. Your counsel reviews it; your managers enforce it.
Can our main company number or an auto attendant text?
Native SMS in Teams is enabled on a number assigned to a user and lands in that user's chat, so the practical pattern is each staff member texting from their own work number. A shared texting number that several people answer, or texts routed into a queue with reporting, is a third-party-app or contact-center capability; if that is the real requirement we say so at the route-selection step rather than registering a number that will not do the job.
What happens after handover?
Your administrators hold the as-configured settings, the compliance kit, the retention decision and the user guide, and can enable more users with the scoped policy. Ongoing moves, adds and changes, policy updates and monthly usage-report reviews are the Managed Microsoft Teams Phone Service. Customers who buy their Microsoft licensing through IT Partner get unlimited break-fix support during business hours at no extra charge; 24/7 coverage is a separate paid agreement.
Who owns this service at IT Partner?
Roman Sotnik is the service owner. IT Partner has been a Microsoft partner since 2006 and delivers this alongside its Teams Phone setup, migration and managed-service work, so the SMS rollout is scoped by the people who run the voice estate it sits on.