Contact Center Standard Support & Process Guide

exotel provides comprehensive support for its contact center solution ameyo , through structured packages, processes, and slas designed to minimize downtime and ensure quick resolutions overview welcome to the exotel contact center (ameyo) support guide this resource is designed to help our customers (both existing and prospective) understand how we handle support inquiries, maintain service quality, and collaborate with your it teams to ensure smooth operations this guide covers our support philosophy, the classification of technical issues, and the shared responsibilities required for effective resolution customer first philosophy we are committed to a "customer first" approach with transparency, responsiveness, and knowledge sharing as the key focus, this support offering enables contact center customers to access a wide range of actions such as issue submission, tracking, retrieval and knowledge resource base sharing in order to ensure seamless operations contact center support packages we offer tailored support packages to meet different business requirements please refer to the detailed breakdown to understand the service levels applicable to your specific package amc plan standard support availability 24x5 phone availability yes patches / updates (bug fixes, security patches, minor enhancements) yes major product upgrade no first response 90 min minor issue next release /update major issue (48 hrs) critical issue (6 hrs) note 24 5 refers to the business working days of the concern geography all the sla’s defined above are applicable for incident tickets only whereas the availability and execution time window for “change management” activities will be agreed separately and mutually (by exotel team and customer), on case to case basis the support process when you report an issue, it moves through a structured workflow to ensure the right level of expertise is applied level 1 handles incoming requests, customer management, and basic troubleshooting to ensure all details are captured level 2 specialists in specific technical areas who handle detailed troubleshooting and problem resolution level 3 experts with years of in depth technical knowledge for complex cases apart from remote support, onsite engineer visits are arranged as per the specifics of each case classification of issue the reported issue is classified as minor, major, or critical depending on the priority of the issue critical a critical issue is defined as one which leads to serious disruption of one of the major functional components of the system such as acd, ivr, dialer or voice logger impacting production and leading to a production loss of 20% or higher for example if the issue causes any of the below, it will be categorized as critical 1\ in a 100 seat setup, more than 20 agents cannot take calls 2\ in a 100 seat setup, only 80 agents or less can login 3\ in a setup with 400 calls, more than 80 calls are getting rejected by the system major a major issue is defined as one that causes failure of one of the major functional components of the system such as acd, ivr, reports, dialer or voice logger impacting production, and leading a production loss between 2 to 20% for example if the issue causes any of the below, it will be categorized as major 1\ in a 100 seat setup, more than 2, but less than 20 agents cannot take calls 2\ in a 100 seat setup, more than 2, but less than 20 agents cannot login 3\ in a setup with 400 calls, more than 8, but less than 80 calls are getting rejected by the system minor any issue that does not fall within the purview of those defined above remote support access we utilize secure access mechanisms to provide remote assistance and troubleshooting for your deployment team viewer direct access over ssh/https (secured one when access are allowed to trusted hosts only) vnc (secured one when access are allowed to trusted hosts only) cisco webex (secured customer needs to be the presenter) microsoft lync (secured customer needs to be the presenter) anydesk note any other access granting mechanisms will have to be separately approved on the basis of merits of case provisioning of such mechanisms/tools will have its own lead time and will not be a part of ticket sla issue handling the issues are analyzed by experts and resolved within specified time as per the managed support system the issues are auto escalated internally to the developers or expert technicians if required the turnaround time for the request, provided the error is traced to the contact center and is not specific to client’s hardware or connectivity, is based on the following classification in next section root cause analysis (rca) for the standard package, rca reports are provided for critical cases only application issues the rca is provided within 72 hours after the issue is resolved (assuming no external dependencies) for issues that arise due to application or ameyo services, with no dependency on network, hardware and other non application factors others as per the analysis subject to below conditions dependencies in case the incident reported needs additional debug data for root cause analysis, the rca will be shared once the data is available in such cases we might need to enable the debug logs and wait for the issue to recreate in case reported incident is of intermittent nature and cannot be recreated easily, rca sharing can depend upon availability of data for that instance and the overall span of rca may spread up to several days till the issue is recreated and logs and data required for the same is collected shared responsibilities maintaining a healthy contact center environment is a partnership the responsibilities are divided as follows exotel team responsibilities 1\ exotel team to share daily setup checklist with the customer (normally it is shared at the time of the setup) 2\ exotel team to share the update for any new release of contact center solution 3\ exotel team to request for release update and update the release as per the schedule and plan client it team responsibilities the client is responsible for the surrounding infrastructure and maintenance daily maintenance running the daily setup checklist database hygiene perform monthly database cleanup maintain only the last 90 days of data on ameyodb and 180 days on reportsdb for optimal performance schedule automatic cleanup via the acp module to remove data older than 91 days infrastructure managing agent desktop os/hardware, network issues, and environmental stability (power/ups) backups managing file archives (e g , monthly voice log backups) third party apps managing any non ameyo applications or services