Skip to content

Commit d44fe07

Browse files
committed
updates
1 parent 9b92199 commit d44fe07

File tree

2 files changed

+7
-11
lines changed

2 files changed

+7
-11
lines changed

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

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ The End of Call Survey provides you with a tool to understand how your end users
2727
## Purpose of the End of Call Survey
2828
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.
2929

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.
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.quality and reliability.
3131

3232

3333
## Survey structure
@@ -90,9 +90,7 @@ you find most important. For example, you can choose to only ask
9090
customers about their overall call experience instead of asking them
9191
about their audio, video, and screen share experience. You can also
9292
customize input ranges to suit your needs. The default input range is 1
93-
to 5 for Overall Call, Audio, Video, and
94-
Screenshare. However, each API value can be customized from a minimum of
95-
0 to maximum of 100.
93+
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.
9694

9795
### Customization options
9896

@@ -110,17 +108,15 @@ Screenshare. However, each API value can be customized from a minimum of
110108
## Store and view survey data:
111109

112110
> [!IMPORTANT]
113-
> 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 follow our
114-
115-
<!-- guidance [here](../analytics/enable-logging.md) -->
111+
> 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).
116112
117113
You cannot access your survey and it will not be stored unless you have enabled a Diagnostic Setting to capture your survey data.
118114

119115
## Next Steps
120116

121117
- 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)
122118

123-
<!-- - Learn how to store and analyze your survey results in Azure, see: [End of Call Survey Logs]( ) NEED TO INSERT LINK HERE -->
119+
- Analyze your survey data, see: [End of Call Survey Logs](../analytics/logs/end-of-call-survey-logs.md)
124120

125121
- Learn how to use the Log Analytics workspace, see: [Log Analytics Tutorial](../../../azure-monitor/logs/log-analytics-tutorial.md)
126122

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ This tutorial shows you how to use the Azure Communication Services End of Call
3030
- [Node.js](https://nodejs.org/) active Long Term Support(LTS) versions are recommended.
3131

3232
- 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. [End of Call Survey Logs](../concepts/analytics/logs/end-of-call-survey-logs.md).
3434
- 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).
3535

3636

@@ -206,7 +206,7 @@ User responses that were sent using AppInsights will be available under your App
206206
- Finally merge these two queries by surveyId. Create new query (+Add -> Add query).
207207
- Make suer the `Data source` is Merge and select `Merge type` as needed
208208

209-
<!--
209+
210210
## Collect survey data
211211

212212
> [!IMPORTANT]
@@ -235,7 +235,7 @@ If a survey participant responded to Question 1 with a score at or below the cut
235235
- Suggested prompt: “What could have been better?”
236236
- API Question Values: Audio, Video, and Screenshare
237237

238-
Surveying Guidelines
238+
### Surveying Guidelines
239239
- Avoid survey burnout, don’t survey all call participants.
240240
- 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.
241241
- Consider using surveys for separate Azure Communication Services Resources in controlled experiments to identify release impacts.

0 commit comments

Comments
 (0)