...
How to get in touch with OX
| Table of Contents |
|---|
Introduction
This document describes roles, responsibilities and communication rules between Open Xchange and Customer's departments responsible for operations and customer service.
...
- All issues need to be opened as ticket within the support ticket system.
- All formal communication needs to be in English to allow 24/7 coverage.
- A central email address is required per announcement type, the distribution list will be maintained by Customer.
- A central phone number is required per announcement type if applicable.
Contact Data
Open-Xchange
Open Xchange Support will act as a central and single point of contact. All communication will be handled via our Ticket System. Further details for the ticket communication can be found in the chapter "Ticket Handling".
Customer
All non personal communication will be sent via our distribution list. Customers can subscribe to the distribution list using multiple E-Mail addresses.
Informational announcements:
EU platform: oxcloud-us@open-xchange.com
US platform: oxcloud-us@open-xchange.com
Incident communication:
EU platform: oxcloud-us-incidents@open-xchange.com
US platform: oxcloud-us-incidents@open-xchange.com
Personal communication will be sent to the default E-Mail address defined in our Ticket System.
Announcements / Communication
...
All issues experienced by Customer will be escalated to OX via the ticket process as defined in the SLA.
Severities
| Severity 1 | Shall mean Incidents that are defined as a complete outage and do not allow the Customer to further conduct his business. Customer’s system or application is completely not available, and no workaround exists. The Incident affects all users deployed on the Joint Solution Environment and is caused by disruption of one or more Supported Component(s). Also means a security or general threat causing potential risk to the Customers’ or End Users’ data integrity or privacy. |
| Severity 2 | The Customer’s operation is severely disrupted. A business critical component of the Joint Solution Environment cannot be used by a majority of the users. |
| Severity 3 | Shall mean Incidents, which involve partial loss of non-critical functionality, one that impairs many operations, but allows the Customer to continue to operate. Also means issues happening in a test- or preproduction environment that would normally cause adverse impact to a production network. |
| Severity 4 | Shall mean general usage questions, recommendations for product enhancements or modifications, and calls that are passed to the Parties for informational purposes. This includes but is not limited to documentation and translation errors. |
The standard way to open a ticket with OX Support is via email. For this purpose Customer gets a dedicated support key from Open-Xchange. When filing a ticket, the key has to be entered into the E-Mail to OX. This License Key controls the SLA in OX's ticket system.
The following article describes the information required by OX and provides a template for the email:
http://knowledgebase.open-xchange.com/support/contact-support-bug-reporting/contact-support/english.html
...
OX will inform Customer via email when the outage of a service is detected including the user impact and the expected Time to Restoration if already known.
As long as the outage persists OX will keep Customer up to date on the progress on an hourly basis via email if not otherwise jointly agreed during the resolution process.
OX will then also inform Customer via email when the service is restored.
The following situations are defined as Outage:
Web-Mail / HTTP | > 30s response for a period of 15min or more |
SMTP | > 30s response for a period of 15min or more |
IMAP | > 30s response for a period of 15min or more |
POP3 | > 30s response for a period 15min or more |
Capacity Management
Capacity Management within the borders of normal organic growth is in the responsibility of Open-Xchange.
Every expected capacity requirement outside this normal growth needs to be aligned between Customer and SDM. This includes expected changes in capacity for a short term (e.g. mailings which will motivate users to use the platform to an unusual high level) as well as expected larger growth than normal (e.g. marketing campaigns driving more new users to the platform than usual).
Planned activities like that are to be discussed with SDM at least 15 business days before the event is triggered by Customer.