BEYONDTRUST SUBSCRIPTION SERVICE SUPPORT GUIDE
This BeyondTrust Subscription Service Support Guide (the “Support Guide”) governs the support that BeyondTrust will provide for the Subscription Service. This Support Guide may be updated from time to time.
I. SCOPE
The purpose of Customer Support is to resolve defects that cause the Subscription Service to perform not in substantial conformance to the Product Overview. A resolution to a defect may consist of a fix, workaround or other relief BeyondTrust deems reasonable.
II. SUPPORT AVAILABILITY
A. Hours
BeyondTrust offers support in English during BeyondTrust’s normal business hours
- Severity 1 - 24 hours a day, 365 days a year
- Severity 2 and 3 - Sunday, 7pm US Central Time – Friday, 7pm US Central Time
Case Submission Information Required When submitting a case to BeyondTrust Technical Support, please have the following information available:
- Company name
- Contact name, phone number, and email address
- Desired Severity level
- Unique case number if this is a continuation of an existing case
- BeyondTrust product name and version number
- Detailed problem statement, including how long the problem has been occurring, any steps to reproduce the problem, and screenshots illustrating the problem
- Description of any troubleshooting done so far if any
- Relevant logs or support package
- Versions and roles of any operating systems associated with or used by the BeyondTrust product.
B. Severity Level 1 After Hours Support
BeyondTrust provides 24/7 access to a Self-Diagnostic Tool for troubleshooting Severity Level 1 Incidents and, for customers with an active Support contract, a Self-Service Center and Knowledge Base available at BeyondTrust’s Support Portal (beyondtrust.com/myportal)). BeyondTrust additionally offers 24/7 support for Severity Level 1 incidents for BeyondTrust Subscription Service customers. Severity Level 1 incidents reported by email should be followed up by phone call to a published Support Contact number. Calls received outside of normal business hours will be triaged for appropriate Severity Level and escalated to an On-Call Support Engineer based on the determined Severity Level. Once an On-Call Support Engineer is engaged the focus of the engagement is to downgrade the severity of the Incident to Severity Level 2 either through a full resolution or by providing an agreed upon workaround.
III. CONTACTING CUSTOMER SUPPORT
Customer can report incidents to BeyondTrust via the following options:
A. How to Submit a Support Request
Request Submission Channels
Customers with a BeyondTrust product that has a valid maintenance contract have access to our Technical Support services through multiple channels. Regardless of how a support request is initiated, all cases will be triaged on submission to ensure you receive assistance from the appropriate product specialist.
Online Via Customer Portal
beyondtrust.com/myportal
Securely submit and review support cases as well as search our knowledge base and links to technical documentation.
Email
mysupport@beyondtrust.com
All cases submitted via email will be assigned a Severity Level 3.
Phone
USA (866) 652-3177
UK +44 (0) 1628 480 210
Additional local support numbers outside the USA / UK can be found on the Support Portal. Calls may be routed to an answering service for triage and case creation.
Chat
beyondtrust.com/myportal
BeyondTrust Technical Support engineers are available from 2am-7pm Monday-Friday US Central time to provide support through a BeyondTrust chat session. Chat sessions may be started from the Customer Portal.
IV. CLASSIFICATION OF SUPPORT INCIDENTS
The content of an Incident as supplied initially is used to identify the incident Severity Level using Table 1 below as a guide. Severity Levels range from Severity Level 1 (Critical) to Severity Level 3 (Low Priority). In collaboration with the Customer, BeyondTrust will make a reasonable determination of the Severity Level of Customer’s incident and make commercially reasonable efforts to respond accordingly. The Severity Level may also be adjusted as the incident progresses towards resolution.
| Severity Levels |
Basic Description of Incident Severity |
Reporting Methods and Response Times (Start of Resolution) |
Roles and Resp. for Incident Solving |
|
Production system down and inoperable. The issue cannot be solved by a restart or a bypass or a workaround.
|
Incident must be documented via email and followed up with telephone call. Maximum target time for First Response (start of resolution) is 30 minutes. Maximum target time for Customer Response Time is 30 minutes.
|
Both parties will make all commercially reasonable attempts to focus support resources on Severity Level 1 issues.
|
|
Production system is operational but impacted due to issue with documented product functionality. Workaround exists for core product functionality.
|
Incident must be reported via email to document the issue and may be followed up via telephone. Maximum target time for First Response (start of resolution) is 8 hours. Maximum target time for Customer Response Time is 8 hours.
|
Both parties will make all commercially reasonable attempts to focus support resources on Severity Level 2 issues during BeyondTrust Technical Support’s normal support hours.
|
|
Cosmetic impairment. Limited impact to use of system. No immediate resolution required. Request for enhancements and general information.
|
Incident must be reported via email. Maximum target time for First Response (start of resolution) is 24 hours.
|
Solutions provided for cosmetic, enhancements, or other incidents are possibly in future versions, depending on the product roadmap.
|
|
|
|
|
Additional Notes:
- Response time for a Severity Level 1 incident is one hour outside of normal business hours.
- Response times are applicable within normal business hours unless noted otherwise.
- First Response identifies the time within normal business hours that BeyondTrust is to respond to the reported incident. Valid responses include, but are not limited to, providing a solution or a work-around.
- Customer Response identifies the time within which a customer is to respond to BeyondTrust after a request for additional information.
- Failure to respond according to the Customer Response Time will result in a lowered priority.
V. INCIDENT RESOLUTION PROCESS
A. When Customer experiences an incident or requires additional information about BeyondTrust products that Customer is not able to resolve with BeyondTrust’s online resources, BeyondTrust Customer Support is available to assist. Incidents reported outside BeyondTrust normal support hours are considered to be received at the beginning of the next business day.
B. When submitting an incident, the following information is required:
(1) Name and the name of company or organization; and
(2) A detailed description of Customer’s incident.
As a general rule, the more specific details Customer can provide the better BeyondTrust is able to provide a resolution quickly and accurately.
Details to include are:
- The BeyondTrust product version related to Customer’s incident or information request;
- Specific error messages Customer received, whether the incident is reproducible and any actions Customer took immediately prior to the incident occurring;
- Any changes made to Customer’s BeyondTrust product, the network environment or the workstations/servers involved prior to the incident;
- How long Customer has been experiencing the reported behavior; and
- If the incident involves a software client, what operating system(s) were involved and if this was a server, what roles were assigned at the time.
(3) Supporting Documents. Whenever possible, please provide screenshots and log files.
(4) Support Incident Number. If there is an open support request with BeyondTrust, please provide the incident number. BeyondTrust recommends responding to emails from BeyondTrust Customer Support with “Incident #” in the subject line.
C. When Customer submits an incident or a request:
(a) It will be logged and receive an incident number and a severity rating.
(b) BeyondTrust Customer Support will verify that Customer has a current Support agreement with BeyondTrust and that the person contacting BeyondTrust is an authorized representative of Customer.
If either of these cannot be validated, BeyondTrust will be unable to provide any further support.
If Customer submit multiple items at once, individual incidents may be opened for each item.
BEYONDTRUSTSUPPORT GUIDE - SUBSCRIPTION
D. Support’s Response:
(1) Customer will receive a response to Customer’s incident within the response times designated for the incident’s severity level.
(2) The response Customer receive may include any of the following:
- the information Customer requested or an immediate resolution;
- an indication that the incident Customer reported is a known issue, when a product fix is expected to be available
- and any available workaround;
- a request for additional information;
- an explanation of a feature or design decision;
- or a link to a published User Guide;
- a software patch or upgrade with instructions;
- multiple resolution options that Customer can decide between; and/or
- confirmation that Customer’s comments or requests are logged as product enhancements or feature requests
(3) Logged Incidents will be set to a status of ‘Closed’ unless further action is required.
VI. CUSTOMER RESPONSIBILITIES
A. Communication. Customer agrees to receive from BeyondTrust communications via email, phone or through BeyondTrust’s Support Portal regarding the Subscription Service.
B. Authorized Contacts. Customer shall appoint no more than five (5) contacts (“Customer Authorized Contacts”) to engage Customer Support for questions and/or technical issues. Only Customer Authorized Contacts are authorized to contact Customer Support.
C. Maintain Awareness of BeyondTrust Product Updates. Review the Support Portal, the change log and various marketing materials for any available software updates.
D. Backup Procedures. Keep full and current backups of Customer’s BeyondTrust data using the tools
provided. It is extremely important to perform backups prior to the any upgrades or updates.
E. Documentation. Customer is responsible for utilizing the latest documentation we provide via BeyondTrust’s Support Portal, corporate website and/or email for handling and operating the Subscription Service.
F. Compliance with Instructions. Customer will make all commercially reasonable efforts to both comprehend the material and execute any instructions provided.
G. Fault Documentation. Before submitting an incident report, Customer shall document any changes that may have been made, as well as to have made a reasonable attempt to reproduce the reported incident, if appropriate.
H. Access to Qualified Staff. Customer shall make any such staff available at times mutually agreed upon that are required to achieve an efficient resolution.
VII. SERVICES AND LIMITATIONS
BeyondTrust Customer Support does not include services that include or result from:
- Uses of or changes made BeyondTrust Software that were not explicitly authorized by BeyondTrust or were in violation of the Agreement in place including the BeyondTrust Subscription Service Agreement (“EULA”)
- Network, systems, operation or other environmental factors not within the direct control of BeyondTrust.
- Failure to install product updates according to the provided instructions.
- Consultative advice and assistance, including:
- Configuration/reconfiguration of new or existing network equipment
- Customization of BeyondTrust products including cosmetic modification
- Programming code, writing scripts, or developing custom integrations
- Services related to non-BeyondTrust products including any updates required for compatibility with BeyondTrust products
- Professional Services; BeyondTrust Support may refer you to your account manager to discuss guided upgraded assist.
- Third party integrations.
For services not covered, BeyondTrust and Customer may agree to applicable scopes of works and fees.
VIII. UPGRADES
A. “Upgrades” are BeyondTrust’s releases of the Subscription Service for repairs, enhancements or new features applied by BeyondTrust to Customer’s instances of the Subscription Service at no additional fee during the Subscription Term. BeyondTrust determines whether and when to develop, release and apply any Upgrade to Customer’s instances of the Subscription Service.
B. Notice; Maintenance Downtime
BeyondTrust shall use reasonable efforts to give Customer five (5) days prior notice of any Upgrade to the Subscription Service. BeyondTrust shall use reasonable efforts to give Customer two (2) days prior notice of any Upgrade to the Subscription infrastructure network, hardware, or software used by BeyondTrust to operate and deliver the Subscription Service if BeyondTrust in its reasonable judgment believes that the infrastructure Upgrade will impact Customer’s use of its production instances of the Subscription Service. BeyondTrust will use commercially reasonable efforts to limit the period of time during which the Subscription Service is unavailable due to the application of Upgrades to no more than two (2) hours per month. Notwithstanding the foregoing, BeyondTrust may provide Customer with a shorter or no notice period of an Upgrade, if necessary, in the reasonable judgment of BeyondTrust, to maintain the availability, security or performance of the Subscription Service or the ability of BeyondTrust to efficiently provide the Subscription Service. The automated Upgrade schedule will vary in accordance with each Cloud product’s software release cadence. For select Cloud products, Customer may install BeyondTrust software Upgrades when new releases are made available. Alternately, BeyondTrust will periodically apply automated Upgrades to Customer’s instances of the Cloud Service when an available BeyondTrust Software release of equal or newer version has not been installed by Customer before the scheduled Upgrade time, to ensure they remain on current, supported versions.
Customer may submit a support request for “no Upgrade” not fewer than three (3) days’ prior to a pending Upgrade of the Subscription Service. Customer’s “no Upgrade” request shall be granted, and the Upgrade shall not be applied to Customer’s instances of the Subscription Service. If Customer has requested “no Upgrade” it may nevertheless be required to Upgrade if in the reasonable judgment of BeyondTrust the Upgrade is necessary to maintain the availability, security or performance of the Subscription Service or the ability of BeyondTrust to efficiently provide the Subscription Service.
C. Naming
BeyondTrust uses the combined values of X and Y numerals in X.Y.z to denote a major version (e.g., 17.1). A maintenance version is denoted by Z in x.y.Z (17.1.1). Maintenance versions are subsumed under their corresponding major versions for the purposes of support.
D. Supported Releases
BeyondTrust provides support for any major version of BeyondTrust’s products for a minimum of two years from the generally available (GA) release date. During the life of two years there may be several maintenance versions associated with the active major version. A GA release and all associated maintenance releases will usually be retired after two years.
Customer acknowledges that the current release is the most current feature, availability, performance and security version of the Subscription Service. A Customer that has submitted a “no Upgrade” request may experience defects, for which Customer hereby agrees that BeyondTrust is not responsible, including without limitation those that affect the features, availability, performance and security of the Subscription Service, that are fixed in the most current version of the Subscription Service.
E. Definitions.
The following list of terms and definitions are used throughout this Customer Support Guide.
- Logged Incident: A record of an incident report communicated to BeyondTrust Customer Support that is used for tracking resolution progress and organizing related communication.
- Incident: A record of communication with BeyondTrust Customer Support indicating an interruption of service or unexpected behavior in the Software.
- Maintenance Version: An updated release of the software including any modification, error correction, or other improvement that may or may not add new capability or functionality to the software, but which is not separately marketed by BeyondTrust.
- Major Version: A release of the software that is separately marketed by BeyondTrust and that incorporates additional capability or functionality.
BeyondTrust may, from time to time and in its sole discretion, make changes to this document set forth herein, provided however, in no event shall BeyondTrust make any changes that will adversely impact or degrade the requirements undertaken by BeyondTrust without notifying the Customer. When BeyondTrust makes changes hereto which do not degrade the requirements undertaken by BeyondTrust, BeyondTrust will provide prominent notice as appropriate under the circumstances, e.g., by displaying a prominent notice within the applicable BeyondTrust products or services or by sending Customer an email.
