Mews guest messaging vs Duve: do you still need the guest platform?

I should say at the start that I haven’t used Mews’s own messaging yet, because nobody has. Mews announced Mews Guest Messaging at Unfold 2026, it comes with the advanced plan, and the full rollout is promised for August. What I do have is two seasons with Duve and a few years running Mews as our PMS at my family resort on the Greek coast. So this is the rare comparison where I actually run both products, just not the half of Mews that isn’t live yet. When the Mews side is a promise rather than something I’ve watched work, I’ll say so.

What Mews messaging will take over

The inbox, and the answering. Mews Guest Messaging pulls WhatsApp and the other channels into one place and ties each message to the booking, with an AI it calls the Mews Agent that reads the property’s own information and answers the recurring questions. My head of reception, Katerina, lives in Duve’s WhatsApp inbox all season. That part of her day, the steady stream of “what time is check-in, is there parking, can we get a late checkout”, is exactly what a native agent does, and it does it without reading the booking back through a connector first, because in Mews the booking is already there. I expect the native version to handle the routine messaging at least as well as Duve does. So I’m not going to pretend the inbox is Duve’s to keep.

What Duve actually earns its keep on

Here is the thing people miss about Duve, and it’s why I’m not cancelling it the day Mews ships. Duve was never really an inbox. The messaging is the least of it.

What it earns its place on is the part Mews doesn’t touch. The pre-arrival upselling brought in real money this season, and guests respond to it on WhatsApp in a way they never did to a form: early check-in, airport transfers, a bottle of wine in the room. That’s a proper upsell engine, not a chat feature. The digital guidebook is the other one. Our guests actually open it and use it, which the laminated folder in the room never managed in twenty years. And the auto-translation is still the small miracle it always was: a Swedish guest wrote to us at ten at night in Swedish, and Katerina answered in Greek without thinking about it. None of that is the inbox. None of it is what the Mews Agent replaces.

So the honest split is simple. Mews messaging replaces Duve’s messaging. It does not, at launch, replace Duve’s upsell, its guidebook, or its check-in flow. Those are the reasons to keep it.

The caveats, in both directions

I won’t oversell Duve. The admin dashboard is a maze, half of it built for hotels ten times my size. The automation is a patience test, one wrong condition and nothing fires. Support goes quiet exactly when I need them, in peak season. And more than one hotelier I trust has been caught by a surprise charge, so read every line of the contract. If Mews eventually builds the upsell and the guidebook into its own guest journey, and a PMS absorbing features over time is the safe bet, then the case for a second bill gets thin. There’s also a quieter point Anna would make before I do: Duve is hosted in Tel Aviv, outside the EU, where Mews keeps your data in Europe. For a privacy-minded hotel that matters more than it does to me.

What I’d actually do

Don’t cancel anything on a press release. When Mews Guest Messaging ships in August, turn it on, let it take the inbox, and run Duve alongside it for a season on the parts that bring in money: the upsell and the guidebook. At renewal, ask the only question that counts, which is whether Duve is still earning its separate cost on something Mews can’t do for free. For now it is. The day Mews’s guest journey grows an upsell engine as good as Duve’s, ask it again. If you’re shopping the rest of the category while you think about it, the other guest communication tools we’ve tested sit alongside Duve, and the wider argument is in our piece on Mews going native.

• Elena