Skip to content

Commit 759c78d

Browse files
committed
more boosted
1 parent c252ed9 commit 759c78d

File tree

2 files changed

+10
-6
lines changed

2 files changed

+10
-6
lines changed

articles/communication-services/tutorials/collecting-user-feedback/includes/ios.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: azure-communication-services
88

99
### iOS Support Overview
1010

11-
To integrate user feedback collection within iOS applications using the Azure Communication Services (ACS) UI Library, developers need to follow a structured approach. This process involves capturing user feedback, including error logs and user information. Once complete, this information is submitted to a server for processing. In this section we detail the steps necessary to accomplish this.
11+
To integrate user feedback collection within iOS applications using the Azure Communication Services (ACS) UI Library, developers need to follow a structured approach. This process involves capturing user feedback, including error logs and user information. Once complete, this information is submitted to a server for processing. In this section, we detail the steps necessary to accomplish this task.
1212

1313
In this example, we're using the [Alamofire](https://github.com/Alamofire/Alamofire) library to handle sending a multi-part form, including log files, to the server.
1414

@@ -22,7 +22,7 @@ In this example, we're using the [Alamofire](https://github.com/Alamofire/Alamof
2222

2323
1. **Event Emission on User Action**: When a user reports an issue through the support form, the event handler captures this action. The information such as the user's description of the problem, error logs, and any call IDs should be prepared to send to the server.
2424

25-
2. **Data Structuring for Submission**: Organize the captured information into a structured format suitable for transmission. Prepare the data in a way that aligns with the expected format of the server endpoint that will receive and process the support request.
25+
2. **Data Structuring for Submission**: Organize the captured information into a structured format suitable for transmission. Prepare the data in a way that aligns with the expected format of the server endpoint that receives and processes the support request.
2626

2727
#### Submitting Data to the Server
2828

@@ -34,11 +34,11 @@ In this example, we're using the [Alamofire](https://github.com/Alamofire/Alamof
3434

3535
1. **Immediate Acknowledgment**: Immediately acknowledge the submission of a support request within the application, providing users with confirmation that their report was received.
3636

37-
2. **Notification Strategy**: Implement a strategy for delivering notifications to users, especially on devices running iOS versions that support specific notification frameworks. You can leverage the use of local notifications to inform users about the status of their report or providing updates as their issue is addressed.
37+
2. **Notification Strategy**: Implement a strategy for delivering notifications to users, especially on devices running iOS versions that support specific notification frameworks. You can use local notifications to inform users about the status of their report or providing updates as their issue is addressed.
3838

3939
### iOS Code Sample
4040

41-
The Swift code sample below outlines a basic implementation for capturing user-reported issues and submitting them to a server for processing. This example shows how to construct a support event handler, including user feedback and application diagnostic information and delivery to the server. The code also includes error handling and user notification strategies to ensure a smooth user experience.
41+
This Swift code sample outlines a basic implementation for capturing user-reported issues and submitting them to a server for processing. This example shows how to construct a support event handler, including user feedback and application diagnostic information and delivery to the server. The code also includes error handling and user notification strategies to ensure a smooth user experience.
4242

4343
The following example is designed to be a hook to be installed within your Event Handler.
4444

articles/communication-services/tutorials/log-file-retrieval-tutorial.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,10 +38,14 @@ In this tutorial, you learn how to access the Log Files stored on the device wit
3838

3939
## Next steps
4040

41-
Refer to the [integrating support document](../concepts/voice-video-calling/retrieve-support-files.md) for more in depth look at how to structure an end to end support flow. This document will help direct you to the tools available to you in order to create an effective support flow in your Applications.
41+
Refer to the [integrating support document](../concepts/voice-video-calling/retrieve-support-files.md) for more in depth look at how to structure an end to end support flow. This document helps direct you to the tools available to you in order to create an effective support flow in your Applications.
4242

4343
## You may also like
4444

45-
- [Provide Support to the end user](../concepts/voice-video-calling/retrieve-support-files.md)
45+
## Tutorials
4646
- [End of call Survey](./end-of-call-survey-tutorial.md)
47+
- [Support form integration with the ACS UI Library](./collecting-user-feedback/collecting-user-feedback.md)
48+
49+
## Concept Docs
50+
- [User feedback in native calling scenarios](../concepts/voice-video-calling/retrieve-support-files.md)
4751
- [User Facing Diagnostics](../concepts/voice-video-calling/user-facing-diagnostics.md)

0 commit comments

Comments
 (0)