Mews Operations must be live. Mews Payments is required for all payment steps in the guest journey, such as booking payments, preauthorizations, kiosk payments and online check-out settlement.  

Digital Key additionally requires a supported door lock integration. 

1. Booking Engine: Configure branding, rates and product visibility in Mews Operations, then embed the Booking Engine on the property website. 

2. Guest Portal: Configure the check-in form, mandatory, optional and hidden fields, terms and signature step, upsell products and email templates; enable online check-out. 

3. Kiosk: The property sources tablet hardware. See hardware requirements in Section 03, installs the Mews Kiosk app and pairs each device to the property via QR code from the Kiosk settings page in Mews Operations. Payment terminal and key cutter are connected where used. 

4. Digital Key: After arranging installation with the property’s door lock provider, the property can issue digital and wallet keys directly through Mews so guests can bypass the reception desk. 

5. Guest Messaging: Guest messaging is activated for guest portal channels; after adding property information, additional channels like SMS and WhatsApp can be enabled, and responses can be automated with AI. 

Booking Engine and Guest Portal: typically configured within the standard Mews Operations onboarding, with no separate activation period.  

Kiosk: dependent on the property sourcing hardware; configuration and pairing take hours once devices are on site.  

Digital Key: Timeline depends on the door lock integration. 

• Website access to embed the Booking Engine, plus brand assets, such as logo, colors, imagery and content 

• Kiosk hardware: Mews does not supply tablets, stands or enclosures. See Section 03 for device requirements 

• Door lock system details for key issuance, including physical key encoding or Digital Key 

• Decisions on check-in form fields, terms and conditions text and upsell products 

For the full integration catalogue, see the Mews Marketplace: https://www.mews.com/en/hospitality-software-marketplace.  

Module-specific integrations include certified door lock systems with key issuance and guest messaging platforms that complement the Guest Journey. 

Three guest-facing surfaces: the Booking Engine embedded on the property website, and the Guest Portal accessed via secure links in emails and SMS.  

No guest account or app install required, and the Mews Kiosk app runs on a lobby tablet. All are configured from Mews Operations. 

1. Guest books directly on the property website through the Booking Engine 

2. Guest completes online check-in via the Guest Portal: registration form, companion details, space upgrade, add products, payment card storage 

3. Guest self-serves arrival at the Kiosk: find reservation, complete registration, ID scan, pay balance, receive key 

4. Guest reviews folio, settles balance and checks out online via the Guest Portal or at the Kiosk 

Booking Engine and Guest Portal: Continuous deployment by Mews with no Partner action.  

Mews Kiosk:  

• App updates are published to the Apple App Store and Google Play. Properties are responsible for keeping all kiosk devices on the current version.  

• Kiosk configuration data is cached on device; cache refresh timeframes: 15 minutes for kiosk configuration and exchange rates, 24 hours for enterprise settings and service documents. 

Feature releases: Continuous for web surfaces; Kiosk app releases ship regularly via the app stores.  

Security patches: As required, applied by Mews without advance notice. 

No Partner action for Booking Engine and Guest Portal updates.  

For the Kiosk, the property must update the app on every kiosk device when new versions are released; running an outdated Kiosk version is the most common cause of kiosk faults and the first support troubleshooting step. 

Door lock systems including Assa Abloy Visionline/ Vostio, Salto, Dormakaba and others, for key issuance, Partner-configured via the Marketplace.  

Third-party kiosks and guest apps integrate via the Connector API and run their own flows.  

Full catalogue: https://www.mews.com/en/hospitality-software-marketplace. 

Twilio https://www.twilio.com/en-us/legal/tos  

Integrations with third-party products and services are provided and operated by the relevant third party. Mews does not warrant the availability, performance or continuity of any third-party integration, and third-party integrations are not covered by the Mews SLA.  
 
Existing Integrations for Guest Messaging  

Meta/WhatsApp at https://www.whatsapp.com/legal 

Twilio https://www.twilio.com/en-us/legal/tos  

Fees for Guest Messaging depend on the Communication Channel, the direction of communication (inbound or outbound), the recipient's country and the pricing model that applies to your account. Current pricing is displayed in your account settings within the Mews platform. 

Guest Messaging fees may be charged on a usage basis (billed in arrears), under an allowance-based package, or under any other pricing model as communicated to you. Where an allowance-based package applies: 

• Monthly Package Allowance means the value of credits available to you each month under your package. 

• Price per Unit means the cost per unit of communication (including per SMS segment or other messaging interaction), per country, as communicated to you, which is deducted from your Monthly Package Allowance. 

• Top-Up means an additional credit amount applied automatically once your Monthly Package Allowance is reached, where you have enabled it. 

• Spend Cap means the maximum amount of Top-Ups you can set in your account beyond your Monthly Package Allowance. 

Mews may offer trials, promotional credits or similar offers in respect of Guest Messaging. Any such offer is one-time and non-recurring unless stated otherwise, non-refundable and non-transferable. Where an allowance-based package applies, a trial or credit does not replace your standard allowance, and once consumed, standard pricing applies

9.4 SMS