--- title: Contact Center Premium Support & Process Guide slug: contact-center/contact-center-premium-support-and-process-guide docTags: createdAt: 2025-12-22T12:22:24.511Z --- # Overview At Exotel, our "Customer First" philosophy drives our support operations. We prioritize transparency, responsiveness, and knowledge sharing to ensure your contact center maintains seamless operations. This guide outlines the **Premium Support Package**, technical processes, and the shared responsibilities required to maintain system health # Contact Center Support packages Exotel offers various support packages to provide the pick-n-choose option to the clients as per their needs and comfort. | **AMC Plan** | **Premium** | | ----------------------------------------------------------------------------- | -------------------- | | Support Availability | 24X7 | | Phone Availability | Yes | | Patches / Updates (bug fixes,
security patches, minor
enhancements) | Yes | | Major Product
Upgrade | No | | First Response | 30 min | | Minor Issue | Next Release /Update | | Major Issue | (24 Hrs) | | Critical Issue | 3 ( Hrs) | :::hint{type="info"} **Note:** 24\*7 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. 1. **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. 2. **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. 3. **Minor** Any issue that does not fall within the purview of those defined above. # Remote Access Methods To troubleshoot effectively, our team requires secure remote access. We support the following methods: - 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 - VPN (Secured one- when access are allowed to trusted hosts only) :::hint{type="info"} **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 it’s own lead time and will not be a part of ticket SLA. ::: # Handling of Issue 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 Premium Package, RCA reports are provided for **both Major and Critical cases**. - **Application Issues:** The RCA is provided within **48 hours** after the issue is resolved (assuming no external dependencies). For issues that arise due to application or contact center services, with no dependency on network, hardware and other non-application factors. - **Others: **As per the analysis subject to below conditions: :::Paragraph{indent="1"} ** Dependencies:** ::: :::Paragraph{listStyleType="disc" indent="2"} 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. ::: :::Paragraph{listStyleType="disc" listStart="2" indent="2"} 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 - Share a daily setup checklist with the customer. - Share updates regarding new contact center releases. Request and execute release updates according to the schedule. ### 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.