Skip to content

Commit 7bfcd89

Browse files
PR Comments
1 parent 532c3ae commit 7bfcd89

File tree

3 files changed

+46
-8
lines changed

3 files changed

+46
-8
lines changed

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

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -17,12 +17,7 @@ ms.subservice: calling
1717

1818
# End of Call Survey overview
1919

20-
21-
> [!NOTE]
22-
> End of Call Survey is currently supported only for our JavaScript / Web SDK.
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.
25-
20+
The End of Call Survey provides you with a tool to understand how your end users perceive the overall quality and reliability of your Calling SDK solution.
2621

2722
## Purpose of the End of Call Survey
2823
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.

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

Lines changed: 44 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,4 +38,47 @@ This tutorial shows you how to use the Azure Communication Services End of Call
3838

3939
::: zone pivot="platform-windows"
4040
[!INCLUDE [End of Call Survey for Windows](./includes/end-of-call-survey-windows.md)]
41-
::: zone-end
41+
::: zone-end
42+
43+
## Collect survey data
44+
45+
> [!IMPORTANT]
46+
> 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)
47+
48+
### View survey data with a Log Analytics workspace
49+
50+
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).
51+
52+
- 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).
53+
54+
## Best practices
55+
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.
56+
57+
**Question 1:** How did the users perceive their overall call quality experience?
58+
We recommend you start the survey by only asking about the participants’ overall quality. If you separate the first and second questions, it helps to only collect responses to Audio, Video, and Screen Share issues if a survey participant indicates they experienced call quality issues.
59+
60+
61+
- Suggested prompt: “How was the call quality?”
62+
- API Question Values: Overall Call
63+
64+
**Question 2:** Did the user perceive any Audio, Video, or Screen Sharing issues in the call?
65+
If a survey participant responded to Question 1 with a score at or below the cutoff value for the overall call, then present the second question.
66+
67+
- Suggested prompt: “What could have been better?”
68+
- API Question Values: Audio, Video, and Screenshare
69+
70+
### Surveying Guidelines
71+
- Avoid survey burnout, don’t survey all call participants.
72+
- 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.
73+
- Consider using surveys for separate Azure Communication Services Resources in controlled experiments to identify release impacts.
74+
75+
76+
## Next steps
77+
78+
- Analyze your survey data, see: [End of Call Survey Logs](../concepts/analytics/logs/end-of-call-survey-logs.md)
79+
80+
- Learn more about the End of Call Survey, see: [End of Call Survey overview](../concepts/voice-video-calling/end-of-call-survey-concept.md)
81+
82+
- Learn how to use the Log Analytics workspace, see: [Log Analytics Tutorial](../../../articles/azure-monitor/logs/log-analytics-tutorial.md)
83+
84+
- Create your own queries in Log Analytics, see: [Get Started Queries](../../../articles/azure-monitor/logs/get-started-queries.md)

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -190,4 +190,4 @@ User responses that were sent using AppInsights are available under your App Ins
190190
```
191191
- You can rename the query (Advanced Settings -> Step name [example: custom-call-survey])
192192
- Finally merge these two queries by surveyId. Create new query (+Add -> Add query).
193-
- Make suer the `Data source` is Merge and select `Merge type` as needed
193+
- Make sure the `Data source` is Merge and select `Merge type` as needed

0 commit comments

Comments
 (0)