Mews integration: what Romy’s AI agents read and write in Mews
Romy integrates with Mews, and is listed on the Mews Marketplace as of 6 November 2026. Our AI agents read the hotel’s live data from Mews and write their actions back into it, so the team does not copy anything by hand.
An integration is only worth what it lets an agent do. So rather than a logo on a slide, here is what Romy actually reads and writes in Mews, at a level a general manager can check.
What is Mews?
Mews is a cloud property management system (PMS): the software where a hotel keeps its reservations, guest profiles, rooms, products and bills. Its Marketplace lists the apps that connect to it. Romy appears there in the Guest technology category.
What Romy reads from Mews
| Data in Mews | What the agents do with it |
|---|---|
| Reservations | Know who is arriving, when, in which room type, and write to the right guest at the right moment |
| Guest profiles | Speak to the guest by name, in their language, with the right contact details |
| Rooms and room categories | Describe rooms accurately, with their features and photos |
| Products (extras) | Offer the hotel’s real extras, at the hotel’s prices |
This is what makes a WhatsApp conversation useful: the agent answers from the hotel’s own data, not from a generic script.
What Romy writes back to Mews
- Orders. An extra a guest buys, such as breakfast or parking, is posted to Mews, on the stay or on the guest’s account depending on how the product is set up in Mews.
- Tasks. A guest request that needs a person becomes a Mews task for the team.
- Guest notes. Useful facts from the conversation are added to the guest profile.
Mews is the only PMS we connect to where tasks go both ways, which is why requests routed from WhatsApp show up where the team already works.
How does a hotel turn it on?
The hotel starts from Romy’s page on the Mews Marketplace. Romy’s team then connects the property, prepares and tests the agents from the hotel’s information, and supports the launch. Go-live takes days.
Limits
I prefer to state them, because they are what makes the rest believable.
- Romy works with what is in Mews. A product missing from the Mews catalogue cannot be sold, and a wrong room description stays wrong until it is fixed in Mews.
- When Mews does not confirm an order (a lost network response, for instance), Romy does not post it a second time blindly: it is set aside for a person to check, so the same extra is not posted twice.
- The integration does not replace the hotel’s judgment. Complaints, exceptions and commercial gestures stay with the team, who can take over any conversation.
Questions to ask any PMS integration, ours included
- What exactly does it read, and what does it write? A list of data and actions, not “we integrate”.
- What happens when the PMS does not answer? Retries can create duplicates; ask how they are avoided.
- Where does the team see what the agent did? In the PMS itself, or only in another tool?
For the bigger picture on agents and why acting in the PMS matters, read what an AI agent for hotels is and how to grow direct bookings. To see it on your own Mews property, book a demo.
Sources
- Romy on the Mews Marketplace, read on 6 November 2026.
- Mews Connector API documentation, read on 6 November 2026.
Frequently asked questions
Does Romy integrate with Mews?
Yes. Romy is listed on the Mews Marketplace in the Guest technology category. It reads reservations, guest profiles, rooms and products from Mews, and writes back orders, tasks and guest notes.
How does a Mews hotel connect Romy?
From Romy’s page on the Mews Marketplace, then Romy’s team configures the connection, prepares the agents from the hotel’s information and tests them before go-live. It takes days, not months.
Can guests buy extras that land in Mews?
Yes. When a guest orders an extra from the hotel’s Mews products, Romy posts it to Mews, on the guest’s account or on the stay depending on how the product is set up in Mews.