Case Study
Case Study: Boutique Hotel Guest CRM & Messaging
We built a connected set of automations for an independent boutique hotel: a guest database and CRM fed by the PMS, an AI assistant for guest messages, pre-arrival emails with online check-in and extras, guest requests turned into housekeeping tasks, and review replies the manager approves. The front desk now works from one arrivals list and one request log, and the manager only sees what needs a decision.
- Property type
- Independent boutique hotel with a small restaurant
- Team involved
- Owner, general manager, front desk, head housekeeper, maintenance
- Systems connected
- Cloud PMS, booking engine, email marketing, WhatsApp, Google Business Profile, n8n
- Delivery
- Scrum, 1-week sprints, about 8 weeks to full launch
The challenge
Where the practice started
Guest messages arrived through the website, email, WhatsApp and OTA inboxes, and the front desk answered the same questions about parking and check-in many times a day.
The PMS held years of stays, but duplicates and OTA alias emails meant nobody could say who the repeat guests were, and past guests never heard from the hotel directly.
Arrival details were collected at the desk, so check-in queues built up on busy afternoons, and extras were rarely offered.
Requests were passed on by sticky note and WhatsApp, some were lost between shifts, and reviews were answered in occasional late-night bursts.
Goals
What the project had to change
- Routine guest questions are answered on every channel, and sensitive messages reach a person quickly.
- Every guest has one clean profile, and marketing reaches only guests who opted in.
- Arrival details and requests are in the PMS before the guest arrives.
- Every request is logged, routed and closed, with the guest told when it is done.
- Every review gets a calm reply approved by the manager.
What we built
What we built, as one connected system.
Guest database and CRM
We read stays from the PMS nightly, merged duplicate profiles, tagged repeat guests and occasions, kept consent with each record and set up a thank-you, an anniversary note and a seasonal invitation.
Service detailsAI guest messaging
An assistant on website chat and WhatsApp answers routine questions from the manager's approved facts, logs requests against the booking and hands complaints, refunds and accessibility questions to the front desk.
Service detailsPre-arrival and online check-in
A pre-arrival email three days out with an online check-in form, extras at their total price and answers written to the reservation, plus a daily arrivals list.
Service detailsRequests to housekeeping tasks
Every request from messages, the desk and the phone becomes a task on the team's chat app, with room status from the PMS, escalation timers and a guest update when done.
Service detailsReview replies
Fair post-stay requests, new reviews gathered in one feed, and reply drafts the manager edits and posts.
Service detailsArchitecture
How the hotel's workflows connect
- Input
- Logic and services
- AI step
- Data
- People
How it flows
- 1 Stays and arrivals from the PMS, guest messages and new reviews feed one n8n instance.
- 2 Five workflows update the guest CRM and task log and use an AI step to answer questions and draft replies.
- 3 The front desk works one arrivals list and one request log; the manager approves replies and exceptions.
- 4 Every step is logged, and a monthly summary shows the measures the hotel agreed to track.
How it behaves
How the system behaves day to day
What guests see
- Quick answers on chat and WhatsApp, with a person when needed
- A short pre-arrival email and online check-in
- Requests acknowledged and closed with an update
- One fair review request after checkout
What staff see
- One arrivals list and one request log
- Sensitive messages flagged with the booking attached
- Draft review replies to approve
- A monthly guest report
What the automation does
- Answers, sends, logs and routes on schedule
- Applies consent and opt-outs across every workflow
- Logs every step and alerts the manager if anything fails
Edge cases and fallbacks
- A guest reports a safety issue by message
- The duty manager is alerted at once; no automated advice is given.
- A guest requests an accessible room change
- The front desk confirms and blocks the room; the assistant never promises it.
- The PMS API is unavailable overnight
- The CRM run and arrivals list retry later and never send from stale data.
- A review names a staff member
- The draft avoids repeating names and the manager handles follow-up.
- WhatsApp or n8n has an outage
- Web chat shows a contact form, staff use the radio for tasks and the manager gets an alert.
Integrations
What we connected
Mews
PMSReservations and customers for the CRM, pre-arrival, requests and availability.
Mews Connector API (reservations, customers), server to server.
Cloudbeds
PMS and booking engineReservations, guests and rooms for the CRM, pre-arrival and requests, with booking webhooks.
Cloudbeds API and webhooks; API access depends on plan tier.
Google Business Profile
Reviews and local searchReview requests, new-review alerts and booking links.
Google Business Profile settings and APIs.
HubSpot
CRMGuest contacts and group deals for smaller properties.
HubSpot's CRM REST API.
WhatsApp Business Platform
MessagingAI assistant, requests and guest updates.
Meta's WhatsApp Business Platform with approved templates.
Slack and Microsoft Teams
Staff tasks and alertsHousekeeping and maintenance tasks, escalations and failure alerts.
Incoming webhooks and APIs.
n8n
Automation platformRuns every workflow, self-hosted or on n8n Cloud.
Your own n8n instance; we hand over every workflow.
How we delivered it
Week by week, one workflow at a time.
Delivery timeline
Typical time to launch: about 8 weeks, then support
-
01
Discovery
Week 1
We shadowed the front desk and housekeeping, gathered real guest messages, mapped arrivals, requests and reviews, and agreed hand-off rules.
-
02
Design and access
Week 2
PMS API access, approved answer library, email and form wording, consent rules, WhatsApp number and processor agreements.
-
03
Sprint 1: pre-arrival
Week 3
Built and shadow-ran the pre-arrival email, online check-in form and arrivals list; demo and sign-off.
-
04
Sprint 2: requests
Week 4
Pre-arrival went live. Built the request log, routing to the team chat and guest updates.
-
05
Sprint 3: guest CRM
Week 5
The request log went live. Built PMS sync, duplicate merging, tags and emails.
-
06
Sprint 4: AI messaging
Week 6
The CRM went live. Built the assistant for web chat and WhatsApp and tested it with real and tricky messages.
-
07
Sprint 5: reviews
Week 7
The assistant went live overnight. Built post-stay requests, the review feed and reply drafts.
-
08
UAT and handover
Week 8
The team ran acceptance tests on every workflow, the assistant went live around the clock, and we handed over the run book.
-
09
Support
Ongoing
Weekly check-ins during stabilisation, then monthly care.
Who does what
What the team does, and what automation does.
Automation does
- Answers routine guest questions from approved facts
- Merges guest profiles and keeps consent with each record
- Sends pre-arrival emails and writes answers to the PMS
- Logs requests and routes them as tasks
- Gathers reviews and drafts replies
The team does
- The front desk confirms requests and special needs
- Housekeeping and maintenance complete and close tasks
- Staff confirm unclear profile merges
- The front desk handles messages the assistant hands over
Manager or owner decides
- The manager approves every review reply
- The manager decides refunds, upgrades and compensation
- The owner sets rates, packages and offers to past guests
Compliance handled
Privacy, consent and safety, built in.
Total prices for extras
Extras and packages show the total price including mandatory fees, in line with the FTC rule in effect from May 12, 2025.
Source: www.ftc.govAccessible rooms confirmed by staff
Accessible room requests are confirmed and blocked by staff, never promised by automation.
Source: www.law.cornell.eduAI disclosure
The assistant says it is automated at the start of every conversation, in line with Article 50 of the EU AI Act.
Source: artificialintelligenceact.euProcessor agreements
Every vendor that touches guest data is under a processor agreement before go-live.
Source: gdpr-info.euMarketing consent
Emails to past guests go only to those who opted in, with an easy way to refuse.
Source: www.legislation.gov.ukNo review gating
Every eligible guest is asked the same way, with no incentives.
Source: support.google.comOutcomes
What changed for the practice
- Routine guest questions are answered on chat and WhatsApp at any hour, with a person a tap away.
- Every guest has one clean profile, and past guests hear from the hotel directly when they opted in.
- Most arrival details and requests are in the PMS before the guest walks in.
- Every request is logged, routed and closed, and guests are told when it is done.
- Every review gets a calm, approved reply.
- The front desk works from one arrivals list and one request log instead of several inboxes.
What we track
The measures the practice watches.
Messages resolved
Share of guest messages answered without staff, and response time overnight.
Online check-in
Share of arrivals completing the form and extras accepted by type.
Request times
Time to complete requests by type and overdue tasks per week.
Repeat guests
Repeat guest share and direct bookings from returning guests.
Reviews
Reviews per month, reply rate and time to an approved reply.
Cost estimate
What a project like this costs
-
Discovery and design
Shadowing, data flows, wording and the backlog for all five workflows.
$1,000 – $2,000
-
Guest CRM module
PMS sync, merging, tags, consent and emails.
$700 – $1,600
-
AI messaging module
Answer library, web chat and WhatsApp, hand-off and logging.
$1,300 – $3,200
-
Pre-arrival module
Email, online check-in, extras and arrivals list.
$600 – $1,500
-
Requests module
Request log, routing, escalation and guest updates.
$700 – $1,700
-
Reviews module
Requests, review feed and reply drafts.
$500 – $1,200
-
Integrations
PMS, WhatsApp, team chat, email and Google.
$300 – $800
-
Testing, UAT and launch
QA, acceptance testing, launch and training.
$400 – $1,500
-
Total project estimate
$5,500 – $13,500
Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: four workflows at our fixed per-workflow range plus an AI assistant. Every property gets its own fixed quote after a free call.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- PMS API access: Included in some PMS plans and an add-on in others.
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
- Messaging: WhatsApp at Meta's own rates; Twilio US SMS at about $0.0083 per segment plus carrier fees if texts are used.
- AI usage and email tools: Pay-per-use model fees and the email provider's own plan.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
Tools we built
Free tools we built and use every day.
The Make It Flow platform
Website audits, monitoring and reports
- Website Speed Test FreeLighthouse score, Core Web Vitals and ranked speed fixes
- SEO Audit FreeTitles, meta, headings, indexability, sitemaps and schema
- Email Deliverability Check FreeMX, SPF, DKIM, DMARC, MTA-STS and BIMI with ready DNS fixes
- Website Monitoring Scheduled re-scans, score emails and 5-minute uptime alerts
Free website tools for practices
Services in this case study
Hotel CRM & guest database automation
Turn PMS stays, direct bookings and enquiries into one clean guest database, tag repeat guests and occasions, and send opted-in guests the right offer before their next likely trip.
From $1,000 · About 4 weeks Details
AI guest messaging & hotel chatbot
One assistant for website chat, WhatsApp, SMS and OTA messages that answers parking, check-in, breakfast and pet questions from your approved answers and hands everything else to the front desk.
From $2,500 · About 5 to 8 weeks Details
Pre-arrival emails, online check-in & upsells
Send a pre-arrival email that collects arrival time, registration details and special requests, offers relevant extras from your list and gets everything into the PMS before the guest arrives.
From $1,000 · About 4 weeks Details
Guest requests & housekeeping tasks
Turn guest requests from messages, the phone and the desk into tracked tasks for housekeeping and maintenance, with priorities, room status from the PMS and a follow-up to the guest when done.
From $1,000 · About 4 weeks Details
Hotel review management & response drafts
Collect reviews from Google, Booking.com and Tripadvisor in one place where access allows, draft calm replies in your voice for the manager to approve and turn feedback into monthly themes.
From $1,000 · About 3 weeks Details
Manager or owner decides
-
How to Build a Hotel Guest Database From Your PMS and OTA DataAutomation · 10 min read
-
Hotel Direct Bookings: How to Build a Website Guests Book OnGuides · 9 min read
-
Hotel Pre-Arrival Messaging and Upsells: A Workflow That Guests WelcomeAutomation · 11 min read
-
Local Business Schema: A JSON-LD Guide for Small BusinessesSEO · 10 min read
-
AI Receptionist for Small Business: Costs, Uses and Safe SetupAutomation · 10 min read
Free 20-minute call
Want this built for your hotels & b&b?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
Sources we checked
Rules and product facts on this page come from these pages, checked in November 2026. This is general information, not legal advice; confirm the rules that apply to your practice with your own adviser.
- FTC: Rule banning junk ticket and hotel fees (effective May 12, 2025)
- 28 CFR 36.302(e) (ADA: reservations made by places of lodging)
- Immigration (Hotel Records) Order 1972, Article 4
- UK PECR regulation 22
- 47 CFR 64.1200 (TCPA rules)
- GDPR Article 28 (processors)
- EU AI Act, Article 50
- Google: Prohibited and restricted content (reviews)
- FTC: Final rule banning fake reviews and testimonials
- Google: About hotel free booking links
- Booking.com Connectivity: Review API
- Booking.com Connectivity: Messaging API
- Mews Connector API: reservations
- Mews Connector API: customer management
- Cloudbeds developer docs
- Cloudbeds webhooks
- Oracle OHIP: Property APIs
- Revinate guest data platform
- Schema.org Hotel
- HubSpot API overview
- WhatsApp Business Platform docs
- Twilio US SMS pricing
- Stripe Payment Links
- n8n pricing
- Google autocomplete phrasing checked for keywords (hotel CRM, hotel guest database, hotel AI chatbot, hotel pre arrival email, hotel guest request log, hotel RFP, hotel review management, hotel direct booking website, hotel schema)