Hi,
This is a follow-up to these two previous questions:
https://dori-uw-1.kuma-moon.com/en-us/answers/questions/5642172/teams-sms-different-name-display-between-calls-his
From those answers and the related documentation, we understand that:
Native Teams SMS chats (with Microsoft Calling Plan numbers / A2P 10DLC) are plain-text only and do not support apps, bots, or message extensions.
SMS conversations are not exposed in Microsoft Graph as standard /chats and /messages resources.
There is currently no app / bot / message extension entry point into SMS chats, and this is by design.
We are now investigating a narrower scenario and would like to confirm our understanding.
Scenario
We have an internal line-of-business web application that displays contact details, including a North American mobile phone number.
The desired user experience is:
User opens the web app’s “Person” page.
Next to a North American mobile number, there is a “Message via Teams (SMS)” button.
When the user clicks that button, the web app launches Microsoft Teams (desktop or web) via a URL / deep link.
Teams opens a native SMS chat to that phone number, so the user can immediately type and send an SMS message.
Important constraints:
We do not need to read or modify SMS content programmatically.
We only want to invoke the Teams UI in “SMS chat” mode targeting a given phone number.
Questions
Question 1: Is there any supported and documented URI scheme or deep link (for example, an https://teams.microsoft.com/... or msteams: URL) that can open a Teams SMS chat for a given phone number, similar to how https://teams.microsoft.com/l/chat/0/0?... opens a normal Teams chat with users (UPNs)?
For example, the URL https://teams.microsoft.com/l/call/0/0?users=4:<E.164> is documented to start a PSTN call.
Question 2: If the answer is no, is there any recommended workaround, for example a way to deep link into the “new SMS chat” experience with the phone number pre-filled in the “To:” field, or is this also not supported?
Question 3: From a design and roadmap perspective, can we safely assume that opening a native Teams SMS chat programmatically (via deep link or URL) is not supported, and that there is currently no documented workaround to achieve this behavior, so that we can close our investigation on this scenario?
Based on the previous answers, we are expecting that this cannot be implemented with native Teams SMS today, but we wanted to double-check explicitly in case there is a specific deep link or pattern we have missed, or any officially recommended alternative.
Thank you in advance for your clarification.