Purpose
This document defines the Standard Operating Procedure (SOP) and Service Level Agreement (SLA) governing technical support services provided by Ascent for Managed Applications and Cloud / IT Infrastructure.
The objective is to establish a structured support process, define service expectations and ensure timely restoration and resolution of operational issues.
Scope of Services
This SOP and SLA applies to systems actively managed by Ascent under a valid Support & Maintenance Agreement.
Managed Applications
Including but not limited to:
- Bespoke ERP Systems
- CRM Systems
- Inventory Management Systems
- Document Management Systems
- Websites
- eCommerce Platforms
- Portals
- Mobile Applications
- APIs and Integrations
- Workflow Automation Systems
- Other applications developed or maintained by Ascent
Cloud & IT Infrastructure
Including but not limited to:
- Cloud Servers
- Virtual Machines
- Web Hosting
- Databases
- Email Infrastructure
- SSL Certificates
- Domain-related Technical Support
- Infrastructure Monitoring
- Backup Monitoring
- Performance Monitoring
Definitions
| Term | Definition |
|---|---|
| Business Hours | Monday to Friday, 10:00 AM to 7:00 PM IST and Saturday, 10:00 AM to 4:00 PM IST excluding notified public holidays. |
| Incident | An unplanned interruption or reduction in the quality of a supported service. |
| Service Request | A request for information, guidance, or routine operational assistance that does not arise from a system fault. |
| Workaround | A temporary solution that restores service until a permanent resolution is implemented. |
| Service Restoration | Restoration of normal business operations, either through a permanent fix or an approved workaround. |
| Change Request (CR) | Any request involving new functionality, enhancements, workflow modifications, or configuration changes outside the scope of standard support. |
| Business Day | Any day during which standard support services are available. |
Support Channels
All support requests shall be logged through one of the following official channels:
| Support Portal | |
|---|---|
| https://support.ascentcts.com | tech@ascentcts.com |
Each request automatically generates a unique ticket number which shall be quoted in all future correspondence.
Support requests received through phone calls, WhatsApp or personal email addresses may be redirected to the official support system to ensure proper tracking and SLA compliance.
Business Hours
| Day | Support Hours |
|---|---|
| Monday to Friday | 10:00 AM – 7:00 PM IST |
| Saturday | 10:00 AM – 4:00 PM IST |
| Sunday & Public Holidays | Closed |
Support requests may be submitted at any time.
Tickets received outside business hours shall be acknowledged and attended during the next applicable business window unless covered under a separately agreed Emergency Support arrangement.
Support Levels
| Level | Description | Typical Activities |
|---|---|---|
| L1 – Service Desk | First point of contact | Ticket acknowledgement, issue logging, basic troubleshooting, user guidance, password resets, categorisation and escalation. |
| L2 – Technical Support | Functional & Technical Specialists | Configuration issues, application troubleshooting, integrations, database verification, server configuration and performance investigation. |
| L3 – Engineering | Product & Infrastructure Engineering | Software defects, code fixes, architecture issues, infrastructure recovery, database repair, security investigations and engineering changes. |
Priority Classification & SLA
| Priority | Business Impact | Initial Response | Target Service Restoration | Escalation |
|---|---|---|---|---|
| P1 – Critical | Complete outage, business operations halted, production data corruption or major security incident. | Within 1 Business Hour | Continuous effort until service is restored | L1 → L2 → L3 |
| P2 – High | Major functionality unavailable, multiple users affected or critical integrations unavailable. | Within 4 Business Hours | Within 2 Business Days | L1 → L2 |
| P3 – Medium | Individual user issues, intermittent errors or non-critical functionality affected. | Within 8 Business Hours | Within 5 Business Days | L1 / L2 |
| P4 – Low | Information requests, cosmetic defects, configuration guidance or minor enhancements. | Within 1 Business Day | As mutually scheduled | L1 |
Response and restoration timelines apply only during Business Hours.
Ticket Lifecycle
- Customer raises a support ticket.
- Ticket acknowledgement is generated automatically.
- L1 performs initial diagnosis.
- Issues beyond L1 capability are escalated to L2.
- Engineering issues are escalated to L3.
- Resolution or workaround is implemented.
- Customer is notified.
- Ticket is closed in accordance with the Ticket Closure Policy.
Customer Responsibilities
Customers are expected to:
- Raise support requests only through authorised channels.
- Provide a clear description of the issue.
- Attach screenshots, videos or error logs wherever available.
- Provide steps to reproduce the issue.
- Nominate authorised users for raising tickets.
- Provide timely remote access where required.
- Respond promptly to requests for additional information.
Delays in receiving the required information or access shall pause the applicable SLA timelines.
Scope of Standard Support
Included:
- Incident Management
- Technical Troubleshooting
- Bug Investigation
- User Assistance
- Configuration Guidance
- Performance Investigation
- Application Monitoring
- Infrastructure Monitoring
- Backup Verification (where applicable)
- SSL & Hosting Support (where managed by Ascent)
Excluded:
- New Feature Development
- Change Requests
- Business Process Consulting
- Data Migration
- Bulk Data Corrections
- User Training
- Third-party Software Defects
- Hardware Maintenance
- ISP or Telecom Issues
- Systems not managed by Ascent
- Unauthorised third-party modifications
- Onsite Support unless specifically agreed
Planned Maintenance
Planned maintenance may be scheduled periodically.
Where reasonably practicable, advance notice shall be provided for maintenance activities that may impact service availability.
Emergency maintenance may be undertaken without prior notice where necessary to preserve system stability, security or data integrity.
Remote Access
Where necessary, customers shall provide secure remote access to facilitate investigation and resolution.
Applicable SLA timelines shall remain suspended until such access is made available.
Ticket Closure Policy
A support ticket shall be considered closed when:
- The reported issue has been resolved.
- A mutually accepted workaround has been implemented.
- The customer confirms closure.
- No customer response is received within five (5) consecutive Business Days following notification of resolution or a request for additional information.
Closed tickets may be reopened within a reasonable period if the same issue recurs.
Fair Usage Policy
Standard support is intended for operational incidents and maintenance of covered systems.
Requests relating to consultancy, training, business process redesign, enhancements or software development may be scheduled separately and may attract additional commercial charges.
Service Exclusions
Ascent shall not be responsible for delays arising from:
- Cloud provider outages
- Internet or telecom failures
- Power failures
- Customer infrastructure issues
- Third-party software failures
- Customer-initiated configuration changes
- Delayed customer responses
- Delayed approvals
- Delayed remote access
- Force majeure events
Limitation of Liability
The timelines specified in this document are service targets and not guarantees.
While Ascent shall make every reasonable effort to restore services within the stated timelines, certain incidents may depend upon third-party vendors, cloud providers or other external agencies beyond Ascent’s reasonable control.
SLA Applicability
This SOP and SLA applies only to systems covered under an active Support & Maintenance Agreement with Ascent.
Support commitments commence only after execution of the applicable agreement and fulfilment of all commercial obligations.
Responsibility Matrix (RACI)
| Activity | Customer | L1 | L2 | L3 |
|---|---|---|---|---|
| Raise Support Ticket | R | |||
| Ticket Acknowledgement | R | |||
| Initial Diagnosis | R | |||
| Functional Troubleshooting | C | R | ||
| Engineering Investigation | C | R | ||
| Code Fixes / Product Defects | R | |||
| Customer Communication | C | R | C | C |
| Resolution Deployment | C | R | R | |
| Ticket Closure | C | R |
R = Responsible
A = Accountable (implicitly Ascent for service delivery)
C = Consulted
I = Informed
Revision & Amendments
Ascent reserves the right to amend this SOP and SLA from time to time.
The latest published version shall supersede all previous versions and shall become effective from the date of publication.