some changes

Author: lucciz01

support/dynamics-365/customer-service/cases-or-incidents/add-or-manage-bots-issues.md

@@ -1,9 +1,11 @@
 ---
 title: Copilot Studio Bots Affect Workstreams And Agent Transfers
 description: Helps resolve issues related to bot management and prevent disruptions in chat queues and agent transfers in Microsoft Dynamics 365 Customer Service.
-ms.reviewer: Soham
+ms.reviewer: ghoshsoham
+author: Yerragovula
+ms.author: srreddy
 ai-usage: ai-assisted
-ms.date: 04/10/2025
+ms.date: 04/14/2025
 ms.custom: sap:Cases or Incidents, DFM
 ---
 # Workstreams and agents are affected by changes made to other Copilot Studio bots
@@ -20,7 +22,7 @@ You might encounter the following issues when working with [Copilot Studio bots]
 
 ## Cause
 
-The issue occurs because the `iscustomizable` flag is enabled for the bot skill. When this flag is enabled, any changes made to one bot or workstream can inadvertently affect other bots or workstreams.
+The issue can occur if the `iscustomizable` flag is enabled for the bot skill. When this flag is enabled, any changes made to one bot or workstream can inadvertently affect other bots or workstreams.
 
 ## Resolution
 
@@ -30,8 +32,6 @@ To prevent a bot from affecting other workstreams, follow these steps to disable
 
 2. Verify that the `iscustomizable` flag isn't enabled for the skill in question.
 
-3. If the flag is enabled, proceed to manually edit the solution's XML file.
-
 For more information, see [Use managed properties](/power-platform/alm/use-managed-properties).
 
 If the issue persists, you can manually edit the XML file of the solution to disable the `iscustomizable` flag:

support/dynamics-365/customer-service/cases-or-incidents/dismiss-all-not-working-in-notifications.md

@@ -2,8 +2,10 @@
 title: Dismiss All Doesn't Work in Notifications
 description: Helps resolve an issue where notifications are cleared temporarily but reappear after a short time in Microsoft Dynamics 365 Customer Service.
 ms.reviewer: srreddy
+author: Yerragovula
+ms.author: srreddy
 ai-usage: ai-assisted
-ms.date: 04/10/2025
+ms.date: 04/14/2025
 ms.custom: sap:Cases or Incidents, DFM
 ---
 # The Dismiss All button doesn't work in the notifications in Dynamics 365 Customer Service
@@ -16,7 +18,7 @@ When you select the **Dismiss All** button in the notifications area of Dynamics
 
 ## Cause
 
-This issue occurs due to insufficient user privileges on specific entities related to the notification system. Non-system administrators might lack the necessary permissions on the following entities:
+This issue can occur due to insufficient user privileges on specific entities related to the notification system. Non-system administrators might lack the necessary permissions on the following entities:
 
 - Model-driven app user setting
 - Setting definition

support/dynamics-365/customer-service/cases-or-incidents/user-location-not-captured-displayed-to-agent.md

@@ -1,7 +1,9 @@
 ---
 title: Chatbot Workstream Fails To Detect User's Location
 description: Helps resolve an issue where the chatbot workstream fails to detect the user's location even after proper configuration in Microsoft Dynamics 365 Customer Service.
-ms.reviewer: Courtney
+ms.reviewer: courtser
+author: Yerragovula
+ms.author: srreddy
 ai-usage: ai-assisted
 ms.date: 04/10/2025
 ms.custom: sap:Cases or Incidents, DFM
@@ -16,7 +18,7 @@ After you [set up visitor location detection](/dynamics365/customer-service/admi
 
 ## Cause
 
-This issue occurs because the Bing Map API key used for location detection is created in a different tenant than the one used by the Dynamics 365 Customer Service application. As a result, the chatbot fail to detect the user's location.
+This issue can occur if the Bing Map API key used for location detection was created in a different tenant than the one used by the Dynamics 365 Customer Service application. As a result, the chatbot fails to detect the user's location.
 
 ## Resolution
 

support/dynamics-365/customer-service/cases-or-incidents/you-dont-have-access-to-data-for-case-summaries-error.md

@@ -1,9 +1,11 @@
 ---
 title: You Don't Have Access To The Data Used For Case Summaries Error
 description: Resolves the issues related to the Copilot case summary feature in Microsoft Dynamics 365 Customer Service.
-ms.reviewer: Soham
+ms.reviewer: ghoshsoham
+author: Yerragovula
+ms.author: srreddy
 ai-usage: ai-assisted
-ms.date: 04/10/2025
+ms.date: 04/14/2025
 ms.custom: sap:Cases or Incidents, DFM
 ---
 # "It looks like you don't have access to the data that's used for case summaries" error
@@ -16,11 +18,11 @@ When you try to use the [Copilot case summary](/dynamics365/contact-center/admin
 
 > It looks like you don't have access to the data that's used for case summaries.
 
-Additionally, the feature fails to display properly for non-administrators who try to use a custom product table instead of the OOB product table.
+Additionally, the feature fails to display properly for non-administrators who try to use a custom product table instead of the out-of-box (OOB) product table.
 
 ## Cause
 
-The issue occurs because Copilot case summaries rely on a relationship between the custom table and the OOB "case" table.
+Copilot case summaries rely on a relationship between the custom table and the OOB "case" table.
 
 - Copilot uses data from tables related to the "case" table to generate summaries.
 - Custom tables that lack a relationship with the "case" table are ineligible for use in generating case summaries.