Merge pull request #235740 from amagginetti/main

Updating TOC search criteria and Two survey documents

Author: v-regandowner

articles/communication-services/concepts/voice-video-calling/end-of-call-survey-concept.md

@@ -25,12 +25,16 @@ ms.subservice: calling
 > End of Call Survey is currently supported only for our JavaScript / Web SDK.
 
 
-The End of Call Survey provides you with a tool to understand how your end users perceive the overall quality and reliability of your JavaScript / Web SDK calling solution. 
+The End of Call Survey allows Azure Communication Services to improve the overall Calling SDK. 
 
+<!-- provides you with a tool to understand how your end users perceive the overall quality and reliability of your JavaScript / Web SDK calling solution.  -->
+<!-- 
 ## Purpose of the End of Call Survey
 It’s difficult to determine a customer’s perceived calling experience and determine how well your calling solution is performing without gathering subjective feedback from customers.
 
-You can use the End of Call Survey to collect and analyze customers **subjective** opinions on their calling experience as opposed to relying only on **objective** measurements such as audio and video bitrate, jitter, and latency, which may not indicate if a customer had a poor calling experience. After publishing survey data, you can view the survey results through Azure for analysis and improvements. Azure Communication Services uses these survey results to monitor and improve quality and reliability.
+You can use the End of Call Survey to collect and analyze customers **subjective** opinions on their calling experience as opposed to relying only on **objective** measurements such as audio and video bitrate, jitter, and latency, which may not indicate if a customer had a poor calling experience. 
+
+After publishing survey data, you can view the survey results through Azure for analysis and improvements. Azure Communication Services uses these survey results to monitor and improve quality and reliability. -->
 
 
 ## Survey structure
@@ -84,7 +88,7 @@ The API allows applications to gather data points that describe user perceived r
 
 
 ### End of Call Survey customization
-You can choose to collect each of the four API values or only the ones you find most important. For example, you can choose to only ask customers about their overall call experience instead of asking them about their audio, video, and screen share experience. You can also customize input ranges to suit your needs. The default input range is 1 to 5 for Overall Call, and 0 to 1 for Audio, Video, and Screenshare. However, each API value can be customized from a minimum of 0 to maximum of 100.
+
 
 You can choose to collect each of the four API values or only the ones
 you find most important. For example, you can choose to only ask
@@ -110,20 +114,14 @@ Screenshare. However, each API value can be customized from a minimum of
 
 <!-- ## Store and view survey data:
 
-// todo@amagginetti
-// testing adding a comment here.
-
-// TODO@amagginetti
-// testing comment here, need to remove comment on this and re-enable.
-
 > [!IMPORTANT]
 > You must enable a Diagnostic Setting in Azure Monitor to send the log data of your surveys to a Log Analytics workspace, Event Hubs, or an Azure storage account to receive and analyze your survey data. If you do not send survey data to one of these options your survey data will not be stored and will be lost. To enable these logs for your Communications Services, see: **[Enable logging in Diagnostic Settings](../analytics/enable-logging.md)**
 
-You can only view your survey data if you have enabled a Diagnostic Setting to capture your survey data. 
+You can only view your survey data if you have enabled a Diagnostic Setting to capture your survey data.  -->
 
 ## Next Steps
 
--	Learn how to use the Log Analytics workspace, see: [Log Analytics Tutorial](../../../../articles/azure-monitor/logs/log-analytics-tutorial.md)
-
--	Create your own queries in Log Analytics, see: [Get Started Queries](../../../../articles/azure-monitor/logs/get-started-queries.md) -->
+<!-- -	Learn how to use the Log Analytics workspace, see: [Log Analytics Tutorial](../../../azure-monitor/logs/log-analytics-tutorial.md)
 
+-	Create your own queries in Log Analytics, see: [Get Started Queries](../../../azure-monitor/logs/get-started-queries.md) -->
+Learn how to use the End of Call Survey, see our tutorial: [Use the End of Call Survey to collect user feedback](../../tutorials/end-of-call-survey-tutorial.md)

articles/communication-services/toc.yml

@@ -247,26 +247,34 @@ items:
       items:
       - name: Diagnose your network
         href: concepts/developer-tools/network-diagnostic.md 
+        displayName: diagnostics, diagnose, feedback, quality, reliability, users, call, quick, satisfaction, improve, issues
       - name: Diagnose client issues
         href: concepts/voice-video-calling/user-facing-diagnostics.md
+        displayName: diagnostics, diagnose, feedback, quality, reliability, users, call, quick, satisfaction, improve, issues
       - name: Diagnose media quality issues
         href: concepts/voice-video-calling/media-quality-sdk.md
+        displayName: diagnostics, diagnose, feedback, quality, reliability, users, call, quick, satisfaction, improve, issues
       - name: Ensure precall readiness
         href: concepts/voice-video-calling/pre-call-diagnostics.md
+        displayName: diagnostics, diagnose, feedback, quality, reliability, users, call, quick, satisfaction, improve, issues
       - name: Check if user is running supported browser
         href: how-tos/calling-sdk/browser-support.md
+        displayName: diagnostics, diagnose, feedback, quality, reliability, users, call, quick, satisfaction, improve, issues
       - name: Verify if an application is active in multiple tabs of a browser
         href: how-tos/calling-sdk/is-sdk-active-in-multiple-tabs.md
+        displayName: diagnostics, diagnose, feedback, quality, reliability, users, call, quick, satisfaction, improve, issues
       - name: Get users ready for their call with UI Library
         items:
         - name: Call readiness overview
           href: tutorials/call-readiness/call-readiness-overview.md
+          displayName: diagnostics, diagnose, feedback, quality, reliability, users, call, quick, satisfaction, improve, issues
         - name: 1. Ensure user is on a supported browser
           href: tutorials/call-readiness/call-readiness-tutorial-part-1-browser-support.md
         - name: 2. Request camera and microphone permissions
           href: tutorials/call-readiness/call-readiness-tutorial-part-2-requesting-device-access.md
         - name: 3. Microphone and camera setup before a call
           href: tutorials/call-readiness/call-readiness-tutorial-part-3-camera-microphone-setup.md
+          displayName: diagnostics, diagnose, feedback, quality, reliability, users, call, quick, satisfaction, improve, issues
     - name: Mobile integrations
       items:
       - name: Integrate with CallKit in iOS
@@ -299,10 +307,12 @@ items:
         href: concepts/analytics/enable-logging.md
       - name: Voice and Video insights
         href: concepts/analytics/insights/voice-and-video-insights.md
+        displayName: diagnostics, diagnose, feedback, quality, reliability, users, call, quick, satisfaction, improve, issues
       - name: Call Recording insights
         href: concepts/analytics/insights/call-recording-insights.md
       - name: Query call logs
         href: concepts/analytics/query-call-logs.md
+        displayName: diagnostics, diagnose, feedback, quality, reliability, users, call, quick, satisfaction, improve, issues
       - name: Export SDK telemetry to Application Insights
         href: quickstarts/telemetry-application-insights.md
   - name: Chat
@@ -561,8 +571,10 @@ items:
       href: concepts/voice-video-calling/media-access.md
     - name: Video constraints
       href: concepts/voice-video-calling/video-constraints.md
+      displayName: diagnostics, diagnose, feedback, quality, reliability, users, call, quick, satisfaction, improve, issues
     - name: Simulcast
       href: concepts/voice-video-calling/simulcast.md
+      displayName: diagnostics, diagnose, feedback, quality, reliability, users, call, quick, satisfaction, improve, issues
     - name: Events
       items:
       - name: Overview
@@ -573,8 +585,10 @@ items:
       items:
       - name: Network recommendations
         href: concepts/voice-video-calling/network-requirements.md
+        displayName: best, practices, before, you, start, diagnostics, diagnose, feedback, quality, reliability, users, call, quick, satisfaction, improve, issues
       - name: Web best practices
         href: concepts/best-practices.md
+        displayName: best, practices, before, you, start, diagnostics, diagnose, feedback, quality, reliability, users, call, quick, satisfaction, improve, issues
       - name: Call networking internals
         href: concepts/call-flows.md
       - name: Call flow topologies
@@ -584,6 +598,7 @@ items:
       items:
       - name: End of Call Survey
         href: concepts/voice-video-calling/end-of-call-survey-concept.md
+        displayName: diagnostics, Survey, feedback, quality, reliability, users, end, call, quick
     - name: Analytics
       items:
       - name: Call logs

articles/communication-services/tutorials/end-of-call-survey-tutorial.md

@@ -15,7 +15,7 @@ ms.subservice: calling
 
 
 
-# Tutorial: Use End of Call Survey to collect user feedback
+# Use the End of Call Survey to collect user feedback
 
 
 [!INCLUDE [Public Preview](../includes/public-preview-include-document.md)]
@@ -35,9 +35,11 @@ This tutorial shows you how to use the Azure Communication Services End of Call
 -	[Node.js](https://nodejs.org/) active Long Term Support(LTS) versions are recommended.
 
 -	An active Communication Services resource. [Create a Communication Services resource](../quickstarts/create-communication-resource.md). Survey results are tied to single Communication Services resources.
--	An active Log Analytics Workspace, also known as Azure Monitor Logs, to ensure you don't lose your survey results. [Enable logging in Diagnostic Settings](../concepts/analytics/enable-logging.md).
+-	An active Log Analytics Workspace, also known as Azure Monitor Logs. [Enable logging in Diagnostic Settings](../concepts/analytics/enable-logging.md).
 
 
+<!-- -	An active Log Analytics Workspace, also known as Azure Monitor Logs, to ensure you don't lose your survey results. [Enable logging in Diagnostic Settings](../concepts/analytics/enable-logging.md). -->
+
 > [!IMPORTANT]
 > End of Call Survey is available starting on the version [1.13.0-beta.4](https://www.npmjs.com/package/@azure/communication-calling/v/1.13.0-beta.4) of the Calling SDK. Make sure to use that version or later when trying the instructions.
 
@@ -196,12 +198,14 @@ If a survey participant responded to Question 1 with a score at or below the cut
 Surveying Guidelines
 -	Avoid survey burnout, don’t survey all call participants.
 -	The order of your questions matters. We recommend you randomize the sequence of optional tags in Question 2 in case respondents focus most of their feedback on the first prompt they visually see.
--	Consider using surveys for separate Azure Communication Services Resources in controlled experiments to identify release impacts.  
+<!-- -	Consider using surveys for separate Azure Communication Services Resources in controlled experiments to identify release impacts.   -->
 
 
 ## Next steps
 
--	Learn how to use the Log Analytics workspace, see: [Log Analytics Tutorial](../../../articles/azure-monitor/logs/log-analytics-tutorial.md)
+- Learn more about the End of Call Survey, see: [End of Call Survey overview](../concepts/voice-video-calling/end-of-call-survey-concept.md)
+
+<!-- -	Learn how to use the Log Analytics workspace, see: [Log Analytics Tutorial](../../../articles/azure-monitor/logs/log-analytics-tutorial.md)
 
--	Create your own queries in Log Analytics, see: [Get Started Queries](../../../articles/azure-monitor/logs/get-started-queries.md)
+-	Create your own queries in Log Analytics, see: [Get Started Queries](../../../articles/azure-monitor/logs/get-started-queries.md) -->