Incident Submission. In order for Crossbeam to respond to email Support requests, Customer must provide information and cooperation to Crossbeam as reasonably required. This includes, without limitation, providing the following information to Crossbeam regarding the Incident:
Aspects of the Service that are unavailable or not functioning correctly, including relevant screenshots
Incident’s impact on users or business processes
Start time of Incident
List of steps to reproduce Incident
Relevant log files or data
Wording of any error message
Incident ID# (when specified by Crossbeam)
Crossbeam’s Support personnel will first attempt to verify the Incident using the Service.
Then, Crossbeam’s Support personnel will assign a priority level (“Priority Level”) to each Incident.
Working within the Support Hours specified above, Crossbeam will seek to provide a response to each Incident in accordance with the Target Response Times specified in the table below.
Target Response Times
Operation of the Service is critically affected (not responding to requests or serving content) for a large number of users; no workaround available.
4 Business Hours
Service is responding and functional but performance is degraded, and/or Incident has potentially severe impact on operation of the Service for multiple users.
6 Business Hours
Non-critical issue; no significant impact on performance of the Service but user experience may be affected.
2 Business Days
Exclusions. Crossbeam will have no obligation to provide Support to the extent an Incident arises from: (a) misuse or unauthorized modifications to the Service, (b) Third-Party Platforms or other third-party systems, (c) Trials and Betas or other free or evaluation use or (d) Technical Services deliverables.