Deploying passwordless security to your users should be a fast and easy experience. Download the visual asset library to customize your communications strategy and convey the positive impact of HYPR to your users.
HYPR Success & Support Services
HYPR Customer Success Services (“Support Services”) terms are subject to the terms of the HYPR Master Subscription Agreement (“Agreement”), and capitalized terms not defined here will have the meaning specified (if applicable) in the Agreement.
|Standard||Premium Support||Premium Plus Support||Technical Account Manager|
|Support Coverage||Business hours||Enterprise-grade (24×7)||Enterprise-grade (24×7)||Enterprise-grade (24×7)|
|Support Contact||Email service||Priority web & phone||Priority web & phone||Dedicated Support Line|
|HYPR Knowledge Hub Access|
|Training videos/ Getting Started webinars|
|Technical Account Management|
|Engagement Manager||—||—||Named Customer Success Manager||Named Technical Account Manager (optional on-site)|
|Access to training specialists||—||—||(remote)||(optional on-site)|
|Periodic Health Checks||—||—|
|Beta Feature Invitation||—||—|
|Welcome Content & End User Guides|
|Deployment Advisor||—||10 Hours||10 Hours||25 Hours|
HYPR will establish the priority level of each reported support request that Customer refers to HYPR for assistance. The priority level of each reported support request shall be classified as follows (each, a “Priority Level”):
|Level 1||Critical Impact (Software Down in Production). An Error that cannot be reasonably circumvented and affects all users. Restricts Customer’s ability to use the Software to perform necessary business functions.||Service is down and not accessible by all Users in production; Data centers are not responding and all users are not able to register, authenticate or de-register.|
|Level 2||Major Impact (Software Crashing/Hanging in Production). An Error that significantly restricts Customer’s ability to use the Software to perform one or more necessary business functions; Affects more than half the user population.||Production servers in a data center are not responding or responding consistently with failures; Users cannot register, authenticate or de-register; Failure impacts more than 50% of users.|
|Level 3||Moderate Impact (Performance/Operational Impact in Production). An Error that restricts the Customer’s ability to use one or more portions or features of the Software to perform a necessary function, but which can be reasonably circumvented. Issue affects more than half the user population||Production servers in a data center are not responding or responding consistently with failures; Users cannot register, authenticate or de-register without a workaround applied; Failure impacts more than 50% of users. Performance of any above functions is degraded by 50%|
|Level 4||Minor Impact of functionality or performance in either Production or non-production environment. Issues affects a portion or unspecified amount of user population.
QA and Testing environment issues will automatically be classified as priority 4 or lower.
|Non-critical features are not behaving as expected leading to inability to complete an attempted action. Occasional failure is reported with the product and retry attempts are unsuccessful at success.|
|Level 5||No impact. A request for general information, or to address a minor, non-material issue.||Service feature enhancement requests or information used by an administration or end user to complete a necessary action.|
Premium Plus Support & TAM Response Time for the Service during 24×7 Support hours
|Priority Level||Issue Acknowledgement||Subsequent Updates|
|Level 1||1 hour||2 Hours|
|Level 2||3 Hours||6 Hours|
|Level 3||12 Hours||12 Hours|
|Level 4||24 business Hours||48 business Hours|
Standard Support Response Time for the Service during Business Hour support
|Priority Level||Issue Acknowledgement||Subsequent Updates|
|Level 1||4 Hours||12 Hours|
|Level 2||12 Hours||24 Hours|
|Level 3||24 Hours||72 Hours|
|Level 4||24 Hours||72 Hours|
Acknowledgement by HYPR
HYPR will respond to all requests for Support reported by Customer. If a request is determined to be a Priority 1 through Priority 3, it shall be deemed an Error. If a support request is deemed an Error, Customer’s report of the Error to HYPR will include, if available from the Customer after due inquiry by Customer, any and all job listings, program dumps, system log, traces and other output, reports or information that HYPR may reasonably request associated with the Error. HYPR will acknowledge receipt of all Errors within the response times (depending on the Priority Level) set forth below (“Response Times“) by contacting Customer’s Designated Support Contact by e-mail or telephone, provided that a response is required.
Resolution by HYPR
Within the specified Response Times, HYPR will use reasonable efforts to provide a resolution to each Error based on an action plan agreed to between the parties, within the Resolution Target established for the applicable Priority Level. Customer Designated Support Contact shall have performed all necessary Triage Support, and will use additional reasonable efforts to assist HYPR to resolve the Error if the determination of the Error is unclear and impacts the Resolution Target time frames noted below. If an Error cannot be resolved within the applicable Resolution Target, HYPR will contact Customer as soon as a resolution or workaround is discovered by HYPR. Subject to Section 9 below, both parties will use their reasonable efforts to assist each other in resolving any Errors.
With respect to any support request deemed to be an Error, HYPR will respond to Customer with an acknowledgement and action plan and commence efforts to provide a resolution in accordance with the following, based on the applicable Priority Level, after Customer notifies HYPR of the Error. For purposes of the table below, a “business day” shall mean any weekday which is not a HYPR holiday and a “business hour” shall mean any hour between 9:00 AM and 5:00 PM (US Eastern Time) during any such business day.