Bookboost review: the privacy story holds up, and the messaging got better

I first reviewed Bookboost a while back. The data processing was solid, the messaging did the job, and the interface was a bit dull. Coming back to it, I’ve spent another few weeks putting it through its paces at our property in Stockholm. The short version: the privacy story is just as strong, WhatsApp now works properly, and the interface is still dull.

Let’s start where it matters most.

Data handling in 2026

I re-examined their DPA in January. The sub-processor list has grown by two entries since my last review, both EU-based, both named with specific purposes and data categories. This is still unusual. Most vendors I audit either bury their sub-processors behind vague language or make you send an email to request the list. Bookboost publishes theirs on their website and updates it when things change.

Data remains in AWS eu-north-1, Stockholm. I confirmed this again directly. The controller-processor relationship is correctly defined. Retention periods are specified per data category rather than hidden behind a blanket “we keep data as long as necessary” clause.

The regulatory environment has shifted since my first review. The European Data Protection Board’s latest guidance on cross-border transfers has made life harder for hotels relying on US-hosted tools with standard contractual clauses. Bookboost doesn’t have that problem. Everything sits within EU jurisdiction, governed by EU law, processed by a Swedish company. That’s not a marketing advantage; it’s a compliance one.

Their cookie implementation on the webchat widget, which I flagged last time, has been updated. The disclosure is now more explicit about what’s tracked and why. It’s not perfect, but it’s better than before, and better than most competitors.

There is one area where the data story gets more complicated. Bookboost markets a “hospitality GPT” feature, and it runs on OpenAI. That means guest conversations processed by their AI flow through OpenAI’s servers in the United States. For a tool that builds its entire identity on EU data residency, this is a meaningful gap. Your booking data stays in Stockholm. Your AI-processed guest messages take a detour through San Francisco. I’d like to see them address this more transparently, because it undercuts an otherwise strong privacy position.

WhatsApp Business API done right

This is the biggest improvement since my last review. Bookboost now runs a proper WhatsApp Business API integration, not a basic connection through a third-party relay.

Setting up the WhatsApp channel took about 40 minutes, including Meta’s verification process (which is on Meta’s side, not Bookboost’s). Once connected, message templates need approval from Meta before you can use them for outbound campaigns. Bookboost makes template creation straightforward. You draft the message, select the category (transactional, marketing, utility), submit it, and track approval status from within the platform.

What impressed me: the automation layer on top of WhatsApp is well thought through. Pre-arrival messages trigger based on PMS data. A guest books a room, and two days before arrival they get a WhatsApp message with check-in details, local recommendations, or an upsell offer, depending on what you’ve configured. Replies from the guest land in the unified inbox alongside everything else.

The consent handling for WhatsApp marketing messages is correct. Guests opt in explicitly. Transactional messages (booking confirmation, check-in instructions) are treated separately. I’ve tested tools that blast WhatsApp marketing to every number they can find and hope nobody complains. Bookboost doesn’t do that.

One limitation: rich media in WhatsApp templates (images, PDFs, buttons) works, but the template builder could give you a better preview of how the message will actually render on a phone screen. You end up sending test messages to yourself repeatedly, which is fine but slightly tedious.

The unified inbox and CRM

The inbox pulls together WhatsApp, email, SMS, and webchat into a single view. Conversations thread correctly across channels. If a guest starts on webchat and continues on WhatsApp the next day, it’s one conversation, not two. I tested this deliberately with three different channel switches and it held together each time.

The CRM underneath has been the quiet strength of this product since the beginning. What I hadn’t fully appreciated until this second review is the data architecture. Bookboost’s CRM is built on a Customer Data Platform that tracks over 300 data fields per guest profile. That sounds excessive until you realise it includes everything from communication preferences and booking patterns to which upsell offers a guest has accepted or ignored. Guest profiles accumulate interaction history, preferences, and notes across stays. When a returning guest messages about their upcoming reservation, my front desk can see their history without asking the guest to repeat themselves. This is the kind of thing that separates a messaging tool from a guest relationship platform.

Campaign segmentation remains solid. You can filter by stay dates, room type, language, previous interactions, and booking source. The segments are practical rather than showy. I built a campaign targeting German-speaking guests with stays longer than three nights, and it took about two minutes.

On results: Bookboost cites a 55% increase in direct bookings and a 50% reduction in repetitive phone calls among hotels using the platform. I treat vendor-reported statistics with caution, but directionally this aligns with what I’ve seen. Our direct booking enquiries through the webchat have increased since setup, and our reception phone does ring less often for the predictable questions (directions, check-in time, parking). I wouldn’t put precise percentages on our own experience, but the trend is real.

What still needs work

The interface. I said it was unremarkable last time. It’s still unremarkable. Everything functions, nothing frustrates, but nothing delights either. For a Malmö-based company, there’s an irony in the design feeling so indifferent to aesthetics. Thomas would have stronger words.

Revenue attribution is the other gap. I can see message open rates, response rates, and click-throughs. But connecting a pre-arrival upsell campaign to actual revenue generated requires exporting data and doing the maths yourself. Sophie would call this a dealbreaker. I call it an annoyance, but it’s an annoyance that shouldn’t still be there in 2026.

The reporting dashboard more broadly feels like it was designed by engineers who are good at collecting data but less interested in presenting it. The information is there; you just have to work harder than you should to extract the story from it.

Two other things worth flagging. First, there is no direct Booking.com chat integration. If you want Booking.com guest messages in the unified inbox, you need to set up email forwarding as a workaround. It functions, but it’s clunky, and for hotels where Booking.com is a major channel, this gap is more than cosmetic. Second, setup complexity is the most common complaint I’ve heard from other hoteliers using Bookboost. Getting the PMS integration, WhatsApp channel, and campaign automations all configured properly takes time and patience. My own setup was manageable because I’m particular about these things and I read the documentation. I can see how a less technically inclined hotel manager might find the first two weeks discouraging.

Why EU jurisdiction keeps getting more relevant

Every quarter brings another regulatory development that makes data residency matter more. The EDPB’s enforcement actions are accelerating. Member state authorities are getting more specific about what constitutes adequate protection for guest data. If your messaging platform stores passport scans and personal details on US servers, you’re not in violation today (probably), but you’re accumulating risk that compounds with each new ruling.

Bookboost removes that risk entirely. Swedish company, Swedish hosting, EU jurisdiction, named sub-processors, published DPA. It’s not exciting. It’s just correct.

A relevant update on the company itself: Bookboost closed a EUR 3.6M Series A in March 2025, led by Vendep Capital. For a tool I’m recommending to other hoteliers, company viability matters. Startups disappear. This funding, combined with growth to over 4,000 properties in 25+ countries (including IHG, Accor, and Hilton properties), suggests they have enough runway and enough traction to stick around. They also ranked third in Guest Messaging Software at the 2026 HotelTechAwards, based on 192 verified reviews. I mention this not because awards prove quality, but because verified review volume at least proves adoption.

One practical note on cost, since I am recommending it. Bookboost prices modularly and per room: a required customer data platform at roughly €2.20 per room per month, then optional modules (the guest journey layer, broadcasts, the inbox) each adding around €1.80 to €2.80 per room, with a minimum of about €399 a month. It is not the cheapest in the category, and the modular structure means your real figure depends on which pieces you switch on. I worked the all-in maths for the whole category, against the WhatsApp message costs that sit under all of them, in what these tools really cost.

Bookboost pricing and setup: common questions

How much does Bookboost cost?

+

It prices modularly and per room. You pay for a required customer data platform at roughly €2.20 per room per month, then add optional modules (the guest journey layer, broadcasts, the inbox) at around €1.80 to €2.80 per room each, with a minimum of about €399 a month. It is not the cheapest in the category, and your real figure depends on which modules you switch on.

Does Bookboost do WhatsApp?

+

Yes, and it does it properly. Bookboost runs a full WhatsApp Business API integration rather than a basic relay, so message templates go through Meta's approval process and pre-arrival messages can trigger from your PMS data. Setting up the channel took me about 40 minutes, and guest replies land in the same unified inbox as everything else.

Is Bookboost good for GDPR-conscious European hotels?

+

It is the strongest option I have audited on this front. Data sits in AWS eu-north-1 in Stockholm, the sub-processors are published and named, the DPA specifies retention per data category, and the whole thing is processed by a Swedish company under EU jurisdiction. The one caveat is the hospitality GPT feature, which I cover below.

Does Bookboost's AI feature keep guest data in the EU?

+

No, and this is the gap in an otherwise strong privacy position. The hospitality GPT feature runs on OpenAI, so guest conversations processed by the AI flow through OpenAI's servers in the United States. Your booking data stays in Stockholm, but your AI-processed messages take a detour, and I would like to see Bookboost address this more transparently.

Does Bookboost connect to Booking.com?

+

Not directly for chat. There is no native Booking.com guest-message integration, so if you want those messages in the unified inbox you have to set up email forwarding as a workaround. It functions, but it is clunky, and for hotels where Booking.com is a major channel that gap matters.