This document is the Support Handbook, describing Mews' 24/7 support scheme and setting out how a Partner may access support, how cases are classified, and the response and resolution commitments Mews provides. All capitalised terms used in this Handbook have the meanings given to them in the Mews Master Terms and Conditions.
Mews may update this Handbook from time to time in accordance with the update mechanism set out in the Master Terms and Conditions.
In this document you can learn about:
- 1. Overview
- 2. Support Contacts
- 3. Partner Responsibilities
- 4. Support Channels and How to Raise a Case
- 5. Classification of Requests
- 6. Response and Resolution Commitments
- 7. Knowledge Base and Mews University
- 8. Self-Service Resources
- 9. When to Use Self-Service vs. Raising a Case
1. Overview
Mews operates a 24/7 support scheme. This Support Handbook sets out how Partners may access support, how cases are classified, and the response and resolution commitments Mews provides. All capitalised terms used in this Handbook have the meanings given to them in the Mews Master Terms and Conditions.
Mews may update this Handbook from time to time in accordance with the update mechanism set out in the Master Terms and Conditions.
1.1 Raising a Case via the Support Portal
To raise a case, Partner must log in to Mews and submit a case via the Mews Support Portal. Mews recommends the Support Portal as the primary channel for all non-emergency requests.
The emergency phone line is reserved for Critical incidents where the Mews Platform is completely unavailable and immediate human contact is required. Contact numbers are available at mews.com/en/contact-us.
Mews guarantees support in English. Mews will take reasonable efforts to support local language requirements for written support requests.
To submit and manage support cases, Partner must have one or more authorised contacts registered in the Mews system. Mews will only process cases from contacts who are verified users in the Partner's Mews account.
Authorised contacts may:
-
Raise new support cases via the Mews Support portal or other permitted channels.
-
Update existing cases with additional information.
-
View the status and history of cases associated with their account.
-
Receive case notifications and resolution communications.
Partner is encouraged to designate contacts with a working knowledge of the Mews Platform and the Partner's technical environment. This helps Mews provide faster, more accurate resolutions. Where a case requires escalation, Mews may ask to engage a contact with appropriate technical access.
Authorised contacts are managed by the Partner's account administrator directly within the Mews Platform. To add or remove a contact, the account administrator should contact Mews Support.
Partner can find out more about how Mews collects, processes, and protects personal data in the Privacy Policy, available at mews.com/en/legal/privacy-policy.
To enable Mews to deliver timely and effective support, Partner agrees to:
-
Respond promptly to Mews requests for information or confirmation. A reminder will be sent after 24 hours. If no response is received within 96 hours, the case will be automatically resolved, and Partner must open a new case to raise the issue again.
-
Provide accurate, complete, and relevant information when raising a case, including steps to reproduce the issue and the business impact.
-
Not include personal data (PII) in case submissions; anonymise or redact before submitting.
-
Designate and maintain authorised support contacts in the Mews Platform.
-
Keep the Mews Platform up to date as reasonably required. Mews may be unable to support issues arising on unsupported configurations.
-
Not submit cases via multiple channels simultaneously for the same issue, as this delays triage.
-
Use self-service resources provided for general product questions before raising a case.
|
Channel |
Availability |
|
Support Portal Chat |
Available 24/7 |
|
Emergency phone (Critical incidents only) |
24/7 — Critical requests only |
If Partner experiences the same or a related issue after a case has been closed, a new case should be opened. Partner should include a reference to the original case number so Mews can review the prior history.
Mews distinguishes among three types of incidents and requests. Classification applies to production environments only; the Critical and High Priority SLA commitments do not apply to sandbox, staging, or other non-production environments.
A Critical request is one concerning an error due to which the Mews Platform in a production environment is completely unavailable (i.e., a total failure of the Mews Platform). Critical SLA commitments apply to production environments only.
A High Priority request is one concerning any of the following errors occurring in a production environment:
(i) a failure of one or more core functions of the Mews Platform not causing complete unavailability (such as unavailability of check-in, check-out, or taking payments); or
(ii) core functions and features of the Mews Platform are available, but production is functioning at a materially impaired rate (such as slow performance of the system or any substantial part of it).
A General request is one concerning:
(i) errors not preventing production but impairing non-production operations (such as inability to check-in or check-out in a standard way);
(ii) other errors not falling within the Critical or High Priority definitions; or
(iii) procedural problems encountered in the use of the Mews Platform.
If Partner contacts Mews Support, Mews will acknowledge receipt of the request within the response time set out below. It is difficult to predict the nature of the incident, and therefore it is also difficult to determine how long the resolution time should be in general. This handbook does not stipulate any specific time limit for resolution requests; however, what we guarantee is that after reporting an incident, Mews will use reasonable endeavours to resolve Critical and High priority incidents as quickly as possible. Resolution commitments are targets only and do not constitute a contractual guarantee. The time required to resolve an incident will depend on its nature, complexity, and root cause, which cannot always be determined at the point of classification. Resolution is achieved by solving the root cause of the incident, implementing a workaround, or delivering a resolution plan.
|
Type of Request |
Response Time |
|
Critical |
4 hours |
|
High Priority |
8 hours |
|
General |
24 hours |
Where Mews requires information or action from Partner in order to progress a case, Mews will set the case status to "Waiting for Partner." The response and resolution clocks pause automatically when this status is set and resume when Partner responds or, in the absence of a response, when the case is automatically resolved under section 3(1) above.
Time spent in Waiting for Partner status does not count towards Mews's response or resolution commitments. Mews will use reasonable efforts to notify Partner promptly when a case is moved to Waiting for Partner status.
Where Mews fails to meet a guaranteed response or resolution time set out in section 6, Partner may be entitled to a service credit in accordance with the Service Level Agreement. Partner should raise a credit claim via the Support portal within 30 days of the incident. Please note that the maximum amount of credits that can be awarded by Mews shall not exceed 50% of the Monthly Fee payable to Mews.
For High Priority requests, Mews does not guarantee a fixed resolution time. Mews guarantees that, following notification of a High Priority incident, Mews will initiate a resolution plan and share it with Partner. The plan will set out the proposed resolution timeline and the steps Mews will take to resolve the incident.
Partner will receive unlimited access to the Mews Knowledge Base, which contains guidelines, FAQs, and articles on the use of the Mews Platform and Services. The Knowledge Base is available at help.mews.com.
Partner will receive access to Mews University, which contains video tutorials to assist with onboarding and use of the Services. Mews University is available at mews.com/en/mews-university.
Mews provides a range of self-service resources that can resolve many questions without the need to raise a case:
|
Resource |
URL |
What it covers |
|
Mews Digital Assistant |
help.mews.com (Help / Contact us icon in Mews Operations) |
AI-powered chatbot providing troubleshooting, how-to guidance, and general information. Available 24/7. |
|
Mews Help Page |
help.mews.com |
1,000+ articles on Mews features, workflows, and configuration. Available in English, Dutch, French, German, and Spanish. |
|
Mews University |
mews.com/en/mews-university |
Video tutorials for onboarding and feature adoption. |
|
Status Page |
status.mews.com |
Real-time platform availability and incident updates. |
|
Community |
community.mews.com |
Peer community for questions, tips, and best-practice sharing. |
|
PMS Release Notes |
releases.mews.com/en |
Changelog for PMS updates. |
|
POS Release Notes |
releases.pos.mews.com/en |
Changelog for POS updates. |
Partner should use self-service resources when:
- Partner has a "how do I..." question about a product feature.
- Partner wants to check whether a platform incident is ongoing (check status.mews.com first).
- Partner needs to understand a recent product change (check release notes).
Partner should raise a support case when:
- A feature is not working as described in the Help Centre.
- Partner has confirmed via the status page that there is no known ongoing incident.
- The issue is causing operational disruption that self-service resources cannot resolve.