BookingLive Support Offerings
Get the Most Out of BookingLive’s Support
Read our guide on how to get the most out of your BookingLive online booking system support.
Booking System Support Levels
Enterprise |
Business |
Pro |
Lite |
|
| Community Support |  |
|
|
|
| User Manual | |
|
|
|
| Webinars and Videos | |
|
|
|
| Technical Support | |
|
|
N |
| Phone Support | |
N | N | N |
| SLA | |
N | N | N |
| Support Includes | Support Does Not Include |
|
|
Support Response SLA’s
While BookingLive attempts to respond to all issues in a timely manner, issues that are Level 1, Level 2 take priority. The following response and resolution times are based on business hours and working days.
Condition and Example |
Response Time |
Resolution Time |
Level 1 A critical issue where the system does not function or is preventing business operations. A large number of users are prevented from working with no procedural workaround.
|
1 hour | 1 day |
Level 2 An issue that is creating a significant operational impact. A large number of users are impacted by issue but they are still able to work in a limited capacity.
|
4 hours | 2 days |
Level 3 A non-critical issue where there is moderate operational impact or non-critical loss of functionality on production system. A small number of users are affected.
|
1 day | 5 days |
Level 4 Questions that pertain to usage questions or clarification of documentation or other non-impacting issue.
|
2 days | 10 days |
Level 5 Customer offers suggestions or requests for new product features and enhancements or other non-impacting issue.
|
5 days | 30 days |
Fixing Bugs
- BookingLive Support will help with workarounds
- Critical issues* will generally be fixed in the next maintenance release
- Non critical bugs will be scheduled according to a variety of considerations
*Critical issues are defined as: “application down or issues causing revenue loss or bookings unable to process.”
Support Policy
Administering BookingLive requires a baseline technical skill set, including but not limited to:
- Understanding of our knowledgebase and key product terminology
- Web technologies
Important information:
- BookingLive supports major versions for 12 months after the first major iteration of that version was released.
- Support is open to system administrators and account holders only. All other users will be redirected to a system administrator.
- Customers are responsible for administering third party systems or plugins including but not limited to SSL Certificates, Email Accounts and SMS.
- For help with unsupported issues, please use our community, a great channel for discussions outside the bounds of support. You can also attend our weekly webinar or book one to one training with an Account Expert.
- BookingLive interfaces with a variety of technologies that is often critical to functioning of our products such as Web Servers, load balancers, single sign-on solutions (SSO), SSL certificates and LDAP repositories. BookingLive will endeavour to provide documentation for the product where possible.
- BookingLive does not offer support for milestone or beta releases, but we do support release candidates
Change or Feature Requests
A feature request is a change to the system that is deemed non critical and non-urgent. A feature request if accepted by BookingLive will be added to the product roadmap. To make a feature request use the feedback link from within your support console or via the member community forum. When a request is made, your feature will be added to our internal tracker. We prioritize feature requests based on the overall need, and value added to all members of the system. Please note: not all feature requests will make it into the platform.
A change request is a document containing a call for an adjustment of the system that is deemed outside of the agreed project scope and may be deemed chargeable. A change request should be raised formally for the attention of your account manager. It’s possible to upgrade your support plan at any time, simply contact us to find out more.
