Clear commitments with consistent, reliable, and timely service.
1. Purpose and Scope
This Service Level Agreement (SLA) defines the service standards the Eventscribe Operations team commits to for support requests submitted through our Boomerang ticketing system. It outlines coverage hours, scope, response, and resolution targets.
The targets in this document are intended to be meaningful to Customers and attainable for the team. They reflect realistic performance during standard business hours.
In Scope
Service requests submitted to the Boomerang system by authorized Admin contacts during the contracted support period are considered in scope. Contracted support periods typically cover the timeframe between an executed contract to the end of an event.
- Standard requests include questions or any requests for configuration assistance, troubleshooting, guidance on next steps, etc.
- Meeting requests include any scheduled, facilitated, or organized video call between Cadmium team member(s) and Customer.
- Question boomerangs (designated with Question as boomerang type) are short inquiries or troubleshooting requests.
Out of Scope
The below listed services may be requested of the team, but delivery timeline falls outside the scope of this SLA.
- Incidents: Infrastructure, server responsiveness, and security concerns are considered critical incidents and are addressed with the highest urgency. They are handled outside this team and are therefore considered out of scope for this SLA. Note, servers and supporting infrastructure components are monitored at all times, with tools and team members in place to identify and rectify incidents rapidly. All declared incidents and associated updates are posted to Cadmium's status site, status.gocadmium.com. Customers are encouraged to subscribe to Cadmium's status site for the most current status information.
- Requests originating from outside of the Boomerang ticketing system
- Product development requests
- Services quoted separately (e.g., Professional Services, Submission Imports, Custom reports, etc.)
- Service tickets where the designated Owner is not a member of Cadmium's team
- Subsequent requests embedded within comments of a previously submitted ticket
- Specialized services that have their own published delivery turnarounds, which apply in place of the standard resolution targets (see Appendix A)
- Services requested outside the support period, which typically ends on the last day of an event
2. Definitions
| Term | Definition |
|---|---|
| Boomerang | Eventscribe's proprietary ticketing system, accessible to any admin user from the footer of the myCadmium platform. |
| Business hours | Monday–Friday, 9:00 a.m.–5:00 p.m. ET, excluding company-observed holidays. All response and resolution clocks count business hours only. |
| Incident | A system-wide outage or occurrence with widespread impact. |
| Initial response | The first non-automated reply to the requester, oftentimes acknowledging receipt of the ticket. |
| Resolution | The point at which a service request is resolved, either by providing an answer to a question, configuration guidance, scheduling a meeting, or delivering a solution (or workaround solution, when necessary) so the Customer can proceed. Boomerangs in status 'Closed' or 'Ready to Close' are considered resolved, but Customers may reopen boomerangs if further questions/challenges remain. |
| SLA clock | Elapsed business hours between ticket submission and its resolution. |
| Priority | The severity assigned to a ticket (P1, P2, or Ongoing) based on business impact and urgency, per Section 4. |
| Update Cadence | The frequency which updates are provided for an open service request. Acknowledgement that the service is outstanding and in the works is considered an update. Urgent matters are updated more frequently than standard, routine requests. |
3. Support Coverage
Support is delivered during business hours as defined above. Tickets may be submitted to Boomerang 24/7; SLA clocks for tickets submitted outside business hours begin at the start of the next business day.
| Channel | Availability | Notes |
|---|---|---|
| Boomerang tickets | 24/7 submission | Triaged and worked during business hours. |
| After-hours / weekends / holidays | Not covered | Available for purchase as an optional premium add-on. |
4. Priority Levels and Targets
Every request is assigned a priority based on its business impact and urgency, which sets the response and resolution targets below. Tickets for events beginning within 4 days are automatically marked Urgent; other requests may be marked Urgent when circumstances warrant. All targets are measured in business hours and days.
| Priority | Description | Initial Response | Resolution Target | Update Cadence |
|---|---|---|---|---|
| P1 – Urgent | An issue affecting an event that is live or begins within 4 days, for example, attendees unable to log in, the mobile app not loading, or published content missing. | 4 business hours | 2 business days | Every 4 business hours |
| P2 – Standard | Routine requests such as configuration changes, how-to questions, troubleshooting, and meeting or training requests. | 8 business hours | 5 business days | Every 2 business days |
| Ongoing | Requests kept open by mutual agreement (for example, recurring work or items to revisit later) where the resolution timeline sits outside the standard cycle. | 8 business hours | n/a | As updates are available |
Note: Resolution includes delivery of an accepted workaround. Time spent awaiting a Customer's response or required information is treated as an exclusion (see Section 6).
5. Escalation
The list below identifies the Cadmium contacts from the Eventscribe Operations team who may be involved in resolving a ticket and the recommended way to reach each. It gives Customers an escalation path to follow when a resolution is delayed, beginning as a target becomes imminent and moving up if a target is missed or a contact is unresponsive.
| Cadmium Contact | When It's Appropriate to Escalate | Preferred Contact Method |
|---|---|---|
| Worker (assigned specialist) The Cadmium team member handling your ticket; your primary point of contact. | N/A | Boomerang messages |
| Project Manager (ticket owner) Oversees your ticket's resolution and keeps communication on track. | Your in-scope request has not received a response or update and the resolution target is approaching. (See Section 1 for scope and Section 4 for targets.) | Boomerang messages |
| Team Supervisor | Targets for response and/or resolution were missed. | Boomerang messages or email |
| Director of Operations | A response or resolution target was missed, and the matter remains unresolved after the earlier contacts. | Rhonda Fleischmann rhonda.fleischmann@gocadmium.com |
6. Exclusions
Targets do not apply in the following situations:
- The Customer has assigned a due date that falls beyond the targets outlined in this SLA.
- Scheduled maintenance windows posted on status.gocadmium.com.
- Outages or delays caused by third-party providers or factors outside the team's control.
- Force majeure events (e.g., natural disasters, major infrastructure failures).
- Requests that fall outside the scope defined in Section 1.
Appendix A: Service Delivery Turnarounds
The delivery turnarounds listed below are drawn from published Eventscribe Service Listings found here and are noted because they have specific turnarounds, without regard to the urgency assigned to a service ticket. Each Service Listing includes a list of services provided, which remains the authoritative source for scope and responsibilities.
| Service | Committed Delivery Turnaround |
|---|---|
| Quality Checks | 3–4 business days, depending on the module |
| Data Imports | 2 business days |
| Post-Event Configuration Reviews | 5 business days |
| Registration Form Revisions | 5 business days |
| Abstract Management System – Data Migrations | 5 business days |
| Exhibitor Floor Plan Mapping | 5 business days |
| Website Embedded Page Whitelisting | 5 business days |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article