Skip to content

Commit 5204da3

Browse files
authored
add 4 articles
1 parent 5814de1 commit 5204da3

5 files changed

Lines changed: 123 additions & 0 deletions

File tree

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
title: Can't Switch Between Different Teams Organizations Within the Dynamics 365 App
3+
description: Explains the design limitation and provides guidance on switching between different Teams organizations in the Dynamics 365 app.
4+
author: Yerragovula
5+
ms.author: srreddy
6+
ai-usage: ai-assisted
7+
ms.date: 03/24/2025
8+
ms.custom: sap:Voice channel, DFM
9+
---
10+
# Can't switch between different Teams organizations within the Dynamics 365 app
11+
12+
This article provides a workaourd for an issue where you can't switch between different Teams organizations within the Dynamics 365 app, a functionality that's available in the standalone Teams mobile and desktop applications.
13+
14+
## Symptoms
15+
16+
You can't find an option to switch to a different organization's Teams within the Dynamics 365 app. This functionality is available in the standalone mobile and desktop Teams applications but not within Dynamics 365.
17+
18+
## Cause
19+
20+
This behavior is by design. Currently, there is no workaround or quick option to switch organizations directly within the Dynamics 365 app. You must manually sign in to the desired organization separately.
21+
22+
## Mitigation steps
23+
24+
To access Teams functionality for a different organization within Dynamics 365, follow these steps:
25+
26+
1. Sign out of the current organization in Dynamics 365.
27+
1. Sign in to the desired organization separately.
28+
1. Ensure that Teams integration is enabled for the specific organization within Dynamics 365. For more information, see [Configure Microsoft Teams chat in Customer Service](/dynamics365/customer-service/administer/configure-teams-chat).
29+
1. Use the integrated Teams chat functionality associated with the newly signed-in organization.
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
title: Instagram Messages and Comments not Reaching Customer Service App
3+
description: Instagram is not currently supported as a social channel for chat in Customer Service applications. Alternatively, a custom channel could be created to use Instagram for messaging.
4+
author: Yerragovula
5+
ms.author: srreddy
6+
ai-usage: ai-assisted
7+
ms.date: 03/24/2025
8+
ms.custom: sap:Custom Channel, DFM
9+
---
10+
# Can't receive Instagram messages and comments in a customer service application
11+
12+
This article explains why Instagram messages and comments, along with Facebook comments, might not appear in a customer service application despite proper setup and permissions. It provides information on the current limitations of Dynamics 365 Customer Service applications and alternative solutions.
13+
14+
## Symptoms
15+
16+
You might encounter the following issues:
17+
18+
- Instagram messages and comments aren't displayed in the customer service application.
19+
- Facebook comments are also not visible despite proper account linking and permissions setup.
20+
21+
## Cause
22+
23+
Instagram isn't currently supported as a default social channel for chat in Dynamics 365 Customer Service applications.
24+
25+
Microsoft is aware of the demand for Instagram integration in Dynamics 365 Customer Service applications. An idea has been submitted to investigate this as a potential feature for future updates. For more details or to track progress, visit the [idea submission page](https://experience.dynamics.com/ideas/idea/?ideaid=9d2da859-15b3-eb11-89ee-0003ff45921e).
26+
27+
## Alternative solution: Configure a custom messaging channel
28+
29+
To enable Instagram as a social channel for customer service interactions, users can create a custom messaging channel. Follow the steps outlined in [Configure custom messaging channels](/dynamics365/customer-service/administer/configure-custom-channel) to set up a custom channel for Instagram messaging and comments.
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
title: Caller ID in Dynamics 365 shows Phone Numbers Not Custom Names
3+
description: It's not possible to configure a display name for outbound calls in Dynamics 365 Customer Service. Only a phone number can be set as the caller ID number.
4+
author: Yerragovula
5+
ms.author: srreddy
6+
ai-usage: ai-assisted
7+
ms.date: 03/24/2025
8+
ms.custom: sap:Voice channel, DFM
9+
---
10+
# Can't set display name for outbound calls in Dynamics 365 Customer Service
11+
12+
Microsoft Dynamics 365 Customer Service enables businesses to manage customer interactions efficiently. However, you might encounter limitations regarding how outbound caller IDs are displayed. This article explains the issue, its cause, and provides guidance on the current configurations available.
13+
14+
## Symptoms
15+
16+
When agents make outbound calls using Dynamics 365 Customer Service, the caller ID displayed to the recipient only shows a toll-free number. You would prefer your company name to be displayed instead.
17+
18+
## Cause
19+
20+
Dynamics 365 Customer Service currently doesn't support configuring a display name (such as a company name) as the caller ID for outbound calls. The **Number label** field associated with the outbound profile is used in the agent dialer interface only and doesn't appear to users who receive the call.
21+
22+
## More information
23+
24+
For more information on configuring outbound and inbound profiles, see [Configure outbound and inbound profiles](/dynamics365/customer-service/administer/configure-outbound-inbound-profiles).
Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
title: This Number Cannot be Upgraded Calling and SMS Capabilities Maxed Out error
3+
description: Solves an error that occurs when you upgrade the capabilities of a phone number in Azure Communication Services.
4+
author: Yerragovula
5+
ms.author: srreddy
6+
ai-usage: ai-assisted
7+
ms.date: 03/24/2025
8+
ms.custom: sap:Messaging capabilities, DFM
9+
---
10+
# "This number cannot be upgraded, Calling and SMS capabilities maxed out" error
11+
12+
This article provides a resolution for an issue where the Azure phone number doesn't work when you try to upgrade the capabilities of a phone number in Azure Communication Services.
13+
14+
## Symptoms
15+
16+
When you try to upgrade the capabilities of a phone number in Azure Communication Services, the following error message occurs:
17+
18+
> This number cannot be upgraded. Calling and SMS capabilities maxed out.
19+
20+
## Cause
21+
22+
This issue occurs because you're trying to upgrade the capabilities of a phone number in a trial environment. Trial environments have limitations, and phone numbers in such environments can't be upgraded. Additionally, the maximum allowed capabilities for calling and SMS is reached.
23+
24+
## Resolution
25+
26+
To resolve this issue,
27+
28+
1. Remove the default trial phone number.
29+
2. Use the purchased phone number instead of the default phone number.
30+
31+
For more information about trial phone numbers in Azure Communication Services, see [Frequently asked questions about trial phone numbers in Azure Communication Services](/azure/communication-services/concepts/telephony/trial-phone-numbers-faq).

support/dynamics-365/customer-service/toc.yml

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,8 @@
22
href: welcome-customer-service.yml
33
- name: Cases or Incidents
44
items:
5+
- name: Can't switch between different Teams organizations in the Dynamics 365 app
6+
href: cases-or-incidents/cannot-switch-teams-organizations-dynamics-365-app.md
57
- name: Sentiment analysis not reflecting positive sentiment or capitalization
68
href: cases-or-incidents/sentiment-analysis-not-reflecting-positive-sentiment-or-capitalization.md
79
- name: Customer Service Insights
@@ -142,6 +144,8 @@
142144
href: omnichannel-for-customer-service/preconversation-survey-mobile-number-field-restriction.md
143145
- name: Custom Channel
144146
items:
147+
- name: Can't receive Instagram messages and comments in a customer service application
148+
href: omnichannel-for-customer-service/cannot-receive-instagram-messages-and-comments.md
145149
- name: Conversations from custom channel not appearing in Inbox
146150
href: omnichannel-for-customer-service/custom-channel-conversations-not-show-in-inbox.md
147151
- name: Customer summary and Closed conversation form
@@ -180,6 +184,10 @@
180184
href: omnichannel-for-customer-service/instance-unavailable-provision-omnichannel.md
181185
- name: Omnichannel provisioning fails with an error
182186
href: omnichannel-for-customer-service/omnichannel-provision-fail-errors.md
187+
- name: Messaging capabilities
188+
items:
189+
- name: '"This number cannot be upgraded, Calling and SMS capabilities maxed out" error'
190+
href: omnichannel-for-customer-service/number-cannnot-upgraded-calling-sms-maxed-out-error.md
183191
- name: Copilot Studio agents
184192
items:
185193
- name: Copilot Studio agent conversations are active after a chat ends
@@ -206,6 +214,8 @@
206214
href: omnichannel-for-customer-service/social-data-sync.md
207215
- name: Voice channel
208216
items:
217+
- name: Can't set display name for outbound calls
218+
href: omnichannel-for-customer-service/cannot-set-display-name-for-outbound-calls.md
209219
- name: Incoming voice calls with long greeting messages cause connection delays
210220
href: omnichannel-for-customer-service/greeting-message-delay-agent-connection.md
211221
- name: Notification not functioning for incoming messages

0 commit comments

Comments
 (0)