As part of our commitment to our SLA and our ISO certification, Code Enigma operates a strict ticketing procedure. So we maintain transparency with you, our customers, that process is detailed here in this FAQ. We also invite you to review our FAQ on the make up of a good ticket.
This section refers to tickets raised due to issues with hosting, server management, service availability, and so on. In general we aim to respond to service issues as quickly as possible. However, our SLA is based on service availability rather than ticket response time, so there is no specified response time for service tickets. 24/7/365 customers may phone us on the support and hosting line to expedite issues, however it is worth noting that calling while issues are under investigation generally slows the resolution time.
Some customers will have custom SLAs for service ticket response times and target resolution times. If that is the case, you will find details of your SLA on your project page in Redmine.
When you make a new ticket, please either do not assign it at all, or assign it to sysadmins. Assigning tickets to named individuals, unless otherwise instructed, is a bad idea, because if someone is away sick or on holiday your ticket may not be responded to. If it is assigned to nobody (or sysadmins) then the next available person will take it up.
Drupal Support Tickets
When you create a new ticket, please either do not assign it at all, or assign it to ceSupport. As with service tickets, assigning tickets to named individuals, unless otherwise instructed, is a bad idea, because if someone is away sick or on holiday your ticket may not be responded to. If it is assigned to nobody (or ceSupport) then the next available person will take it up.
Every day one member of the support and hosting team is on front-line support. This means they are responsible for answering the phone and organising the tickets for that day. If you are a Business Support customer or a 24/7/365 SLA hosting customer, you may raise tickets by telephone on +44 (0)20 3588 2200, but please remember other levels of SLA may not use telephone support.
Every morning the entire team has a checkpoint call, where tickets are assigned for working and the front-line person for the day is selected. You may expect a response to your ticket within a working day of raising it, and you may also expect continuing communication from us, at least daily, even if the issue is still in progress.
When a task is created, it follows the following workflow:
- New - An issue created but yet not actioned
- In progress -Work has started
- Blocked - Progress blocked for a given reason
- Approved, waiting to go live - The solution has passed UAT and is now pending release
- Resolved - On live, pending ticket being closed (usually by client)
- Closed - The issue is closed
- Closed (due to inactivity) - After 7 days has passed on a ticket in resolved state, the ticket will close automatically
If you are a customer hosted externally and you have staged changes that are not approved, we may need to revert those changes in order to honour your security updates SLA, so it is particularly important customers on other 3rd party platforms do not leave review tickets open.