You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/voice-video-calling/end-of-call-survey-concept.md
+18-20Lines changed: 18 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,17 +21,13 @@ ms.subservice: calling
21
21
> [!NOTE]
22
22
> End of Call Survey is currently supported only for our JavaScript / Web SDK.
23
23
24
+
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.
24
25
25
-
The End of Call Survey allows Azure Communication Services to improve the overall Calling SDK.
26
26
27
-
<!-- provides you with a tool to understand how your end users perceive the overall quality and reliability of your JavaScript / Web SDK calling solution. -->
28
-
<!--
29
27
## Purpose of the End of Call Survey
30
-
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.
28
+
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.
31
29
32
-
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.
33
-
34
-
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. -->
30
+
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.
35
31
36
32
37
33
## Survey structure
@@ -44,6 +40,8 @@ The survey is designed to answer two questions from a user’s point of view.
44
40
45
41
The API allows applications to gather data points that describe user perceived ratings of their Overall Call, Audio, Video, and Screen Share experiences. Microsoft analyzes survey API results according to the following goals.
46
42
43
+
44
+
47
45
### End of Call Survey API goals
48
46
49
47
@@ -87,14 +85,9 @@ The API allows applications to gather data points that describe user perceived r
87
85
### End of Call Survey customization
88
86
89
87
90
-
You can choose to collect each of the four API values or only the ones
91
-
you find most important. For example, you can choose to only ask
92
-
customers about their overall call experience instead of asking them
93
-
about their audio, video, and screen share experience. You can also
88
+
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
94
89
customize input ranges to suit your needs. The default input range is 1
95
-
to 5 for Overall Call, Audio, Video, and
96
-
Screenshare. However, each API value can be customized from a minimum of
97
-
0 to maximum of 100.
90
+
to 5 for Overall Call, Audio, Video, and Screenshare. However, each API value can be customized from a minimum of 0 to maximum of 100.
98
91
99
92
### Customization options
100
93
@@ -109,16 +102,21 @@ Screenshare. However, each API value can be customized from a minimum of
109
102
> [!NOTE]
110
103
> A question’s indicated cutoff value in the API is the threshold that Microsoft uses when analyzing your survey data. When you customize the cutoff value or Input Range, Microsoft analyzes your survey data according to your customization.
111
104
112
-
<!--## Store and view survey data:
105
+
## Store and view survey data:
113
106
114
107
> [!IMPORTANT]
115
-
> 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)**
108
+
> 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 our guidance: [End of Call Survey Logs](../analytics/logs/end-of-call-survey-logs.md).
116
109
117
-
You can only view your survey data if you have enabled a Diagnostic Setting to capture your survey data.-->
110
+
You cannot access your survey and it will not be stored unless you have enabled a Diagnostic Setting to capture your survey data.
118
111
119
112
## Next Steps
120
113
121
-
<!-- - Learn how to use the Log Analytics workspace, see: [Log Analytics Tutorial](../../../azure-monitor/logs/log-analytics-tutorial.md)
114
+
- 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)
115
+
116
+
- Analyze your survey data, see: [End of Call Survey Logs](../analytics/logs/end-of-call-survey-logs.md)
117
+
118
+
- Learn how to use the Log Analytics workspace, see: [Log Analytics Tutorial](../../../azure-monitor/logs/log-analytics-tutorial.md)
119
+
120
+
- Create your own queries in Log Analytics, see: [Get Started Queries](../../../azure-monitor/logs/get-started-queries.md)
121
+
122
122
123
-
- Create your own queries in Log Analytics, see: [Get Started Queries](../../../azure-monitor/logs/get-started-queries.md) -->
124
-
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)
Copy file name to clipboardExpand all lines: articles/communication-services/tutorials/end-of-call-survey-tutorial.md
+12-14Lines changed: 12 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,12 +30,10 @@ This tutorial shows you how to use the Azure Communication Services End of Call
30
30
-[Node.js](https://nodejs.org/) active Long Term Support(LTS) versions are recommended.
31
31
32
32
- An active Communication Services resource. [Create a Communication Services resource](../quickstarts/create-communication-resource.md). Survey results are tied to single Communication Services resources.
33
-
- An active Log Analytics Workspace, also known as Azure Monitor Logs. [Enable logging in Diagnostic Settings](../concepts/analytics/enable-logging.md).
33
+
- An active Log Analytics Workspace, also known as Azure Monitor Logs. See [End of Call Survey Logs](../concepts/analytics/logs/end-of-call-survey-logs.md).
34
34
- To conduct a survey with custom questions using free form text, you will need an [App Insight resource](../../azure-monitor/app/create-workspace-resource.md#create-a-workspace-based-resource).
35
35
36
36
37
-
<!-- - 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). -->
38
-
39
37
> [!IMPORTANT]
40
38
> End of Call Survey is available starting on the version [1.13.1](https://www.npmjs.com/package/@azure/communication-calling/v/1.13.1) of the Calling SDK. Make sure to use that version or later when trying the instructions.
41
39
@@ -165,7 +163,7 @@ Screenshare. However, each API value can be customized from a minimum of
165
163
In addition to using the End of Call Survey API you can create your own survey questions and incorporate them with the End of Call Survey results. Below you'll find steps to incorporate your own customer questions into a survey and query the results of the End of Call Survey API and your own survey questions.
- Embed Azure AppInsights into your application [Click here to know more about App Insight initialization using plain JavaScript](../../azure-monitor/app/javascript-sdk.md). Alternatively, you can use NPM to get the App Insights dependences. [Click here to know more about App Insight initialization using NPM](../../azure-monitor/app/javascript-sdk-advanced.md).
168
-
- Build an UI in your application that will serve custom questions to the user and gather their input, lets assume that your application gathered responses as a string in the `improvementSuggestion` variable
166
+
- Build a UI in your application that will serve custom questions to the user and gather their input, lets assume that your application gathered responses as a string in the `improvementSuggestion` variable
169
167
170
168
- Submit survey results to ACS and send user response using App Insights:
171
169
``` javascript
@@ -208,19 +206,18 @@ User responses that were sent using AppInsights will be available under your App
208
206
- Finally merge these two queries by surveyId. Create new query (+Add -> Add query).
209
207
- Make suer the `Data source` is Merge and select `Merge type` as needed
210
208
211
-
<!--
209
+
212
210
## Collect survey data
213
211
214
212
> [!IMPORTANT]
215
-
> 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](../concepts/analytics/enable-logging.md)
213
+
> 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: [End of Call Survey Logs](../concepts/analytics/logs/end-of-call-survey-logs.md)
216
214
217
215
218
216
### View survey data with a Log Analytics workspace
219
217
220
-
You need to enable a Log Analytics Workspace to both store the log data of your surveys and access survey results. To enable these logs for your Communications Services, see: [Enable logging in Diagnostic Settings](../concepts/analytics/enable-logging.md). Follow the steps to add a diagnostic setting. Select the “ACSCallSurvey” data source when choosing category details. Also, choose “Send to Log Analytics workspace” as your destination detail.
218
+
You need to enable a Log Analytics Workspace to both store the log data of your surveys and access survey results. To enable these logs for your Communications Service, see: [End of Call Survey Logs](../concepts/analytics/logs/end-of-call-survey-logs.md).
221
219
222
-
- You can also integrate your Log Analytics workspace with Power BI, see: [Integrate Log Analytics with Power BI](../../../articles/azure-monitor/logs/log-powerbi.md)
223
-
-->
220
+
- You can also integrate your Log Analytics workspace with Power BI, see: [Integrate Log Analytics with Power BI](../../../articles/azure-monitor/logs/log-powerbi.md).
224
221
225
222
## Best practices
226
223
Here are our recommended survey flows and suggested question prompts for consideration. Your development can use our recommendation or use customized question prompts and flows for your visual interface.
@@ -238,17 +235,18 @@ If a survey participant responded to Question 1 with a score at or below the cut
238
235
- Suggested prompt: “What could have been better?”
239
236
- API Question Values: Audio, Video, and Screenshare
240
237
241
-
Surveying Guidelines
238
+
### Surveying Guidelines
242
239
- Avoid survey burnout, don’t survey all call participants.
243
240
- 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.
244
-
<!-- - Consider using surveys for separate Azure Communication Services Resources in controlled experiments to identify release impacts.-->
241
+
- Consider using surveys for separate Azure Communication Services Resources in controlled experiments to identify release impacts.
245
242
246
243
247
244
## Next steps
248
245
249
-
-Learn more about the End of Call Survey, see: [End of Call Survey overview](../concepts/voice-video-calling/end-of-call-survey-concept.md)
246
+
-Analyze your survey data, see: [End of Call Survey Logs](../concepts/analytics/logs/end-of-call-survey-logs.md)
250
247
251
-
<!-- - Learn how to use the Log Analytics workspace, see: [Log Analytics Tutorial](../../../articles/azure-monitor/logs/log-analytics-tutorial.md)
248
+
-Learn more about the End of Call Survey, see: [End of Call Survey overview](../concepts/voice-video-calling/end-of-call-survey-concept.md)
252
249
253
-
- Create your own queries in Log Analytics, see: [Get Started Queries](../../../articles/azure-monitor/logs/get-started-queries.md)-->
250
+
-Learn how to use the Log Analytics workspace, see: [Log Analytics Tutorial](../../../articles/azure-monitor/logs/log-analytics-tutorial.md)
254
251
252
+
- Create your own queries in Log Analytics, see: [Get Started Queries](../../../articles/azure-monitor/logs/get-started-queries.md)
0 commit comments