> For the complete documentation index, see [llms.txt](https://developer.rategain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.rategain.com/our-products/channel-manager/rg-bridge-supply-push/integration-overview/monitoring-and-after-sales-support.md). # Monitoring and after sales support After successfully rolling out the integration to customers, managing them involves two key aspects: #### Monitoring * **Technical Oversight**: Ensure high customer satisfaction through SLA monitoring. * **Regular Reporting**: Conduct regular monitoring and reporting of various technical aspects of the integration. * **Integration with Ticketing Systems**: RG Bridge will be integrated with existing ticketing systems (IMS/OTRS). * **Report Formats**: The formats for Channel Availability Reports (CAR), Channel Health Reports (CHR), and other reports will be decided and published by RateGain. * **Service Levels**: Agreed service levels will be implemented by RateGain and monitored for third-party compliance. #### After Sales Support * **Personal Attention**: Provide dedicated attention and training to customers after RG Bridge implementation. * **Account Management**: Handled by RateGain’s account management team to ensure continuous support and satisfaction. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://developer.rategain.com/our-products/channel-manager/rg-bridge-supply-push/integration-overview/monitoring-and-after-sales-support.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.