VMware Zimbra, is committed to providing a support program that offers high-value and cost-effective options for our customers. The goal of our technical support program is to respond quickly to customer issues and to continually improve our handling of your technical support needs. This document describes the support services, methods, process, and response targets for customer support requests.
See what customers are saying about Zimbra Support.
We provide robust web-based access to self-help facilities. Among the on-line resources are:
The Zimbra GSS Technical Support Team is available by telephone for customers who have Premium Support. Telephone support is available at the following numbers:
Normal business hours are Monday-Friday 6:00 am - 6:00 pm U.S. Pacific time (-8 GMT), excluding VMware holdays. 24x7 support is available for Premium Support Level customers.
Support Packages are determined by your Network Edition contract type. Please see the pricing page for more information on these options. The table below shows the different Packages: Premium and Advantage, as well as "Trials" (Support for those using the 60-day Network Edition trial).
| Advantage | Premium | Trials | |
|---|---|---|---|
| Forums, Wiki, Documents, Product Portal | Yes | Yes | Yes |
| Updates, Upgrades | Yes | Yes | For first 60 days |
| Support Portal | Yes | Yes | For first 60 days |
| Phone Support (business hours) | No | Yes | No |
| Phone Support (24x7) for Severity-1 issues* | No | Yes | No |
| Support Incidents | 10 per year | Unlimited | 2 in first 60 days |
* Available for Severity-1 system-down incidents only
Each Support Package comes with limited Support Incidents (except for Premium, which has unlimited). An incident is the ability to contact Zimbra directly for help. Your Support Package determines the method (e.g. Support Portal or phone) and how many times a year.
Zimbra is committed to resolving customer problems quickly and professionally; when you contact Zimbra:
Note: Enhancement and bug requests also funnel in through the same ticketing process. Typical resolution for enhancements will be bugs filed with Engineering who will work with the Support team to provide target release dates. You can always check enhancement and bug status at http://bugzilla.zimbra.com/ or the Product Portal.
The Severity Definitions available are the following:
| Severity Level | Definition |
|---|---|
| Severity 1 (Sev-1) |
Critical Service Outage A production service is down and no workaround is immediately available.
Severity 1 support requires you to have dedicated resources available to work on the issue on an ongoing basis during your contractual hours. In the case that the customer cannot continue to work on the issue with Zimbra, the case Severity Level may be reduced to a Sev-2. A service outage does not include the loss of connectivity or access for a single or relatively small subset of users, and a service outage should only be filed on cases thought to be problems with the server or service. Sev-1s cannot be filed on a case thought to be a problem in a messaging user agent or client such as Zimbra Desktop, Microsoft® Outlook®, Apple® iPhone®, etc. |
| Severity 2 (Sev-2) |
Major Functionality Major functionality is severely impaired.
|
| Severity 3 (Sev-3) |
Minor Functionality Minor functionality not working – workaround available. Partial, non-critical loss of functionality of the software.
|
| Severity 4 (Sev-4) |
General Usage Questions
Cases initially opened via email will be assigned a Severity Level of Sev-4. |
| Priority Level | Premium Support | Advantage Support | 60-Day Trial |
|---|---|---|---|
| Critical Service Outage (Sev-1) |
1 Hour (24x7) |
4 Business Hours (12x5) |
Not Available |
| Major Functionality (Sev-2) |
4 Business Hours (12x5) |
8 Business Hours (12x5) |
Not Available |
| Minor Functionality (Sev-3) |
8 Business Hours (12x5) |
12 Business Hours (12x5) |
Not Available |
| General Usage Questions (Sev-4) |
12 Business Hours (12x5) |
12 Business Hours (12x5) |
12 Business Hours (12x5) |
Please note: the target "Response" time included here should not be confused with a "Resolution" time. Resolution for a complex technical problem may require significantly more time than the targets set for Response. The Response targets are measured on the initial response after the case has been submitted as a case.