World Class Support from zenphi
zenphi Support Policy
This Support Policy (“Support Policy”) describes the policies and procedures under which Zenphi (“Zenphi”) provides technical support and maintenance services (“Support”) for its process platform and associated product(s) (collectively, the “Service”) to its customers (each, a “Customer”).
Support is provided for the Service pursuant to the separate Subscription Agreement and Order Form under which the Customer has purchased Support and is subject to the terms and conditions of that Agreement, Order Form, and the terms of this Support Policy. Support is provided for the term specified in the Subscription Agreement and will automatically renew with the renewal of the Subscription Agreement or the applicable Order Form.
Support is available through Zenphi’s online, web-based, in product chat, email enquiries (email@example.com) and via mutually agreed online meetings (Google Meet), as indicated on Annex A and Annex B to this Support Policy (each, an “Annex” and collectively, the “Annexes”).
This Support Policy sets forth expectations for Support between the Customer and Zenphi’s Support organization, including:
Who is authorized to submit issues;
How to submit issues;
What types of issues are supported; and
How and when Zenphi resolves and closes reported issues.
Contact: means qualified individuals knowledgeable in the internal systems, tools, policies, and practices in use by Customer and proficient users of the Service. Customers are expected to make every effort to ensure that the individuals that are designated as Contacts are qualified to support the Customer teams internally.
Documentation: means Zenphi’s online user guides, documentation, and help and training materials, as updated from time to time, accessible via https://www.zenphi.com, https://discuss.zenphi.com, or login to the applicable Service.
Incident: means each individual issue with the Service reported to Zenphi.
Product Releases: are specific versions of the core Service.
Releases: are updates to the Service that provide:
New features, modifications, or enhancements to the Service;
Updates to features, code corrections, patches, and other general updates of the Service or:
Fixes to the Service. Releases do not include separate or different products or bundles marketed by Zenphi under a different name
III. Scope of Support
What Support Includes.
If the Customer is current on payment for Support and the Service, Zenphi shall provide the Customer with Support consisting of the following:
Chat and email based submissions of Incidents, as specified in the applicable Annex;
Product Releases and Releases;
Documentation, including an online knowledge base of information and solutions that provides up-to-date information on the Service and a Forum where Customers, Partners, and other users of the Service can share information and ideas about how to use the Service;
Guidance and troubleshooting in connection with questions and issues arising from the following:
Customer activities with respect to the Service;
Basic Configuration Issues: Zenphi will troubleshoot the Customer’s configuration settings for existing installations of Supported Products (as defined below in Section III.6 Supported Products) to ensure proper operation and connectivity.
Usage Issues: Zenphi will respond to the Customer’s “how to” questions related to standard and intended Service usage.
Efforts to Correct the Service: Zenphi will make commercially reasonable efforts to correct bugs or other errors in the Service. The Customer acknowledges that Zenphi is not required to correct every bug, error, or problem with the Service that it reports to Zenphi or of which Zenphi is otherwise made aware and that Zenphi does not guarantee resolution times.
What Support Excludes.
The Customer acknowledges that if a non-supported Incident is submitted, they may be referred to their Partner of record or another authorized Zenphi Partner. If the Customer decides to engage their Partner or another authorized Zenphi Partner, the costs of those services, if any, will be the Customer’s responsibility. The following are excluded from Support:
Service that has been altered or modified, unless altered or modified by Zenphi;
Service that has not been installed, operated, or maintained in accordance with the Documentation;
Troubleshooting of Google, other third party, or open standards based technologies, such as XML, HTML/CSS, SharePoint, BizTalk, Active Directory, middleware, SQL queries, database connectivity, or Java scripts; and
Custom solutions or actions.
End-User training in the Service.
Business process consultation and design.
Supported Products: Zenphi will provide Support only as specified in this Support Policy. Zenphi supports use of the Service only as specified in the Documentation. Zenphi’s Support obligations do not cover hardware, operating systems, networks, or third-party software. The Customer understands that Zenphi may need additional information as to the Customer’s use of the Services during the term of this Support Policy.
Zenphi accepts late subscription renewal payments for up to 90 days from the subscription expiration date upon payment of:
1. The fee for the Renewal Term, and;
2. A 20% reinstatement fee.
Note: Any lapse greater than 90 days will require the purchase of a new subscription.
IV. Incident Submission and Resolution
Customers shall obtain Support by reporting Incidents. Incidents shall be tracked from initial report through final resolution.
Who May Submit Incidents?
Support is intended to provide assistance for issues and questions beyond what is covered in associated Documentation. At the time of purchase, the Customer may designate as many authorized Contacts as required. However, anyone employed and authorized by the Customer may be added at any time.
The Customer will ensure that when an authorized Customer Contact submits an Incident, that individual will have full access and permissions required to troubleshoot the Incident and is authorized to make recommended changes to the Customer’s network and/or applicable Products to help troubleshoot or resolve the issue.
The Customer will give Zenphi reasonable access to the Product and systems where the Service is deployed as necessary for Zenphi to determine the cause of the problem and find a resolution. Customer is solely responsible for Customer’s data, information, and software, including making back-up copies and security. Zenphi recommends Customers create backup copies of configuration files before any work is performed.
How to Submit Incidents.
Unless otherwise specified in a supplemental support plan purchased by the Customer, Incidents are to be submitted to Zenphi by an authorized Contact through via the community forum, in product chat, or email based on the level of Support purchased by Customer, as specified in the applicable Annex.
How to Report an Incident.
In order to expedite the resolution of Incidents, Zenphi expects that Customer will make every attempt possible to:
Verify that the Incident is reproducible (as applicable);
Provide information necessary to help Zenphi track, prioritize, reproduce, or investigate the Incident;
Provide a full description of the issue and expected results;
Categorize issues (technical question, defect, enhancement request, etc.);
List steps to reproduce the issue and relevant data;
Provide any applicable log files (de-identified of sensitive data if appropriate);
Provide exact wording of all issue-related error messages;
Describe any special circumstances surrounding the discovery of the issue, e.g. first occurrence or occurrence after a specific event, frequency of occurrence, business impact of the problem on the Customer, and suggested urgency and;
Identify any existing Incident number in ongoing communications with Zenphi.
Support Response and Incident Resolution.
Zenphi Incident Response.
For each Incident reported by the Customer in accordance with these procedures, Zenphi shall:
Confirm receipt of the reported Incident within the Initial Response time specified in the applicable Annex;
Set a Severity Level for the Incident in accordance with the terms below;
Use commercially reasonable efforts to respond to the Incident within the time specified the applicable Annex;
Analyze the Incident and, as applicable, verify the existence of the problem(s) resulting in the Incident, which may include requesting that the Customer provide additional information, logs, and re-execution of commands to help identify the root cause and dependencies of the reported issue;
Give the Customer direction and assistance in resolving the Incident;
Keep a record of ongoing communications with the Customer;
Use commercially reasonable efforts to respond to the Incident in accordance with the Initial Response times set forth in the applicable Annex and;
Upon request of the Customer, discuss Severity Level and ongoing communication time frame. Note: Zenphi may modify the Incident’s Severity Level at its sole discretion.
Zenphi will prioritize Incidents according to the following criteria:
Severity 1 (“S1”): is the highest priority and receives first attention. S1 Cases are to be submitted when the Customer cannot access the Service.
Severity 2 (“S2”): indicates a reported Incident where the issue has severely impacted the performance of the Service’s intended use and is causing a material and adverse impact to the majority of the Customer’s users; or the Service is not operating in a material respect within the documented functionality and it is impacting the majority of the Customer’s users or deployed workflows.
Severity 3 (“S3”): indicates a reported Incident where the issue has an impact on the performance and/or functionality of the Service that is impacting the minority of the Customer’s users or deployed workflows.
Severity 4 (“S4”): indicates a reported Incident requesting assistance and may include questions of how to use the Service. It may also include a reported Incident where the Service is operating within the documented functionality and the Customer would like to record an idea for inclusion in future releases. Zenphi will not provide feedback on such enhancement requests, and these Support Cases are closed once the information has been recorded in our Product Request tool.
Resolution and Closure of Incidents.
Incidents shall be closed in the following manner:
For solvable issues: Depending on the nature of the issue, the resolution may take the form of an explanation, recommendation, usage instructions, workaround instructions, or advising the Customer of an available release that addresses the issue.
In the event that custom or unsupported plug-ins, modules, or custom code is used, Zenphi may ask, in the course of attempting to resolve the issue, that the Customer remove any unsupported plug-ins, modules, or custom code. If the problem disappears upon removal of an unsupported plug-in or module, then Zenphi may consider the issue to be resolved. Supported plug-ins or modules are defined as those listed and defined as supported in the Documentation.
For issues outside of scope as outlined in this document, Zenphi may close issues by identifying the Incident as outside the scope of Support.
Dropped Issues. Zenphi may close an Incident if the Contact has not responded after two (2) weeks from the date that Zenphi requested additional information required to solve the case. The Customer may request Incidents be reopened. At Zenphi’s sole discretion, Incidents will be re-opened for further investigation if the Incident is deemed to be solvable.