Fixed quote after a free call

A hotel AI chatbot and guest messaging assistant that stays on your facts

Guests ask the same questions before and during a stay: check-in time, parking, breakfast hours, late checkout, pets and directions. We build an AI assistant for your website, WhatsApp and SMS, and where your PMS or messaging tool allows, OTA messages, that answers from your approved answers, takes booking and late-checkout requests for staff, says it is automated and hands complaints, refunds and accessibility needs to a person. Projects typically cost $2,500 to $7,500 and take five to eight weeks.

The problem

What a hotel AI concierge should and should not do

A small front desk handles check-ins, phone calls and walk-ins while messages arrive from the website, email, WhatsApp and every OTA inbox. Most are routine, but each one takes a minute, and a guest waiting at the desk notices.

An AI concierge only helps if it stays within limits. It must answer from the property's own facts, never promise an upgrade or a refund, never guess about accessibility and pass anything sensitive to a person with the reservation already attached.

What we build

What our hotel guest messaging assistant includes

Approved answer library

Check-in and checkout times, parking, breakfast, Wi-Fi, pets, accessibility features, local tips and policies, written and approved by the manager.

Every channel in one place

Website chat, WhatsApp, SMS and, where the PMS or messaging tool exposes them, OTA conversations.

Request capture

Late checkout, early check-in, extra beds and airport transfers captured as requests for staff to confirm.

Hand-off rules

Complaints, refunds, billing disputes, accessibility and safety questions go straight to the front desk with the booking attached.

Clear AI disclosure

The assistant says it is automated and offers a person at any time.

Multilingual answers

Replies in the guest's language from the same approved facts, with staff able to read a translation.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Guest messages

    A guest asks a question by web chat, WhatsApp, SMS or an OTA inbox.

  2. 02 Automated

    Answer from the library

    Routine questions get a short answer from the approved facts.

  3. 03 Automated

    Request captured

    Requests such as late checkout are logged for the front desk.

  4. 04 Front desk review

    Front desk confirms

    Staff confirm requests, check availability and reply to anything unusual.

  5. 05 Manager or owner decides

    Refunds and exceptions

    Refunds, upgrades, rate changes and complaints are decided by the manager.

How it behaves

How the hotel AI chatbot behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the guest sees

  • A clear note that the assistant is automated
  • Quick answers in their own language
  • Requests confirmed by a person
  • A person for complaints, refunds and accessibility

What staff see

  • Requests logged against the booking
  • Sensitive messages flagged at once
  • A weekly list of unanswered questions

What the automation does

  • Answers only from approved facts
  • Looks up bookings read-only
  • Logs every conversation for review

Edge cases and fallbacks

Question not in the library
The assistant says it does not know, offers a person and adds the question to the review list.
Guest reports a safety issue
Immediate alert to the front desk and duty manager; no automated advice.
Guest asks for a refund
Acknowledged and passed to the manager with the booking attached.
AI or messaging outage
Web chat falls back to a contact form and messages queue for staff.
Booking not found
The assistant asks for the confirmation number once, then hands over.

Architecture

An AI guest messaging assistant for a hotel at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Guest Chat, WhatsApp, SMS Assistant service n8n or Laravel Language model Claude, Gemini, GPT Approved answers Property-written PMS booking Read-only lookup Front desk Requests, issues Transcripts Weekly review
  • Input
  • Logic and services
  • AI step
  • Data
  • People

How it flows

  1. 1 A guest messages on any channel and is told the assistant is automated.
  2. 2 The service retrieves approved answers and passes them, with fixed rules, to the model.
  3. 3 Routine questions are answered; requests are logged against the booking for the front desk.
  4. 4 Complaints, refunds and accessibility needs go to a person, and every conversation is logged.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

AI guest messaging & hotel chatbot project plan

Typical time to launch: about 6 weeks, then support

  1. 01

    Discovery

    About 1 week

    Collect real guest messages by channel, agree what the assistant may and may not answer.

  2. 02

    Answer library

    About 1 week

    Write and approve answers with the manager, including hand-off wording.

  3. 03

    Build

    About 2 weeks

    Channels, retrieval, PMS lookup, request logging, alerts and admin view.

  4. 04

    Test

    1 to 2 weeks

    Real and tricky messages in several languages; the manager signs off.

  5. 05

    Launch

    2 to 3 days

    Start with website chat or overnight hours, then add channels.

  6. 06

    Support

    Ongoing

    Weekly transcript review at first, then monthly library updates.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

Claude, Gemini or OpenAI models n8n AI Agent node or Laravel WhatsApp Business Platform Twilio SMS Mews, Cloudbeds or OPERA Cloud API for booking lookups Slack, Teams or email for staff alerts

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and answer library

    Real messages reviewed, answers written and approved.

    $500 – $1,200

  • Build

    Assistant service, channels, retrieval, hand-off and admin view.

    $1,200 – $4,000

  • Integrations

    PMS lookup, WhatsApp, SMS and staff alerts.

    $300 – $1,000

  • Testing and evaluation set

    Real, tricky and multilingual messages tested.

    $300 – $900

  • Launch and training

    Soft launch, transcript review and team walkthrough.

    $200 – $400

  • Total project estimate

    $2,500 – $7,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Each extra channel adds build time. Model usage, WhatsApp and SMS fees are billed to your accounts directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • AI model usage: Billed by the provider per use; short answers at small-hotel volumes are usually a modest monthly amount.
  • Messaging: WhatsApp at Meta's own rates and Twilio US SMS at about $0.0083 per segment plus carrier fees.
  • Hosting: n8n Cloud from about €20 a month, or your own server.

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
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

EU: tell guests they are talking to AI

Article 50 of the EU AI Act requires AI systems that interact with people to inform them, from 2 August 2026. We add the disclosure on every channel.

Source: artificialintelligenceact.eu

US: accessible room information

Lodging reservation services must identify and describe accessible features, so accessibility questions go to staff who know the rooms rather than the assistant.

Source: www.law.cornell.edu

EU and UK: guest data

Conversations contain personal data under GDPR and UK GDPR, so the assistant collects only what a request needs and data stays with contracted processors.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 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. 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. 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. 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

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

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

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Hotel AI chatbot questions questions, answered.

Practical questions from your approved answers: check-in times, parking, breakfast, Wi-Fi, pets, directions and policies. It takes requests such as late checkout for staff to confirm and hands complaints, refunds and accessibility questions to a person.

Booking.com and other OTAs open their messaging APIs to certified connectivity partners. If your PMS or messaging tool connects those inboxes, we work through it; otherwise we start with web chat, WhatsApp and SMS. We confirm the route per project.

It can look up a booking read-only and log requests, but it does not change reservations, rates or payments. Staff confirm every change.

Yes. It says so at the start and offers a person at any time. The EU AI Act requires this from 2 August 2026, and we do it everywhere.

Yes. It replies in the guest's language from the same approved facts, and staff see a translation of every conversation.

We log every conversation and send a weekly list of unanswered questions. Watch messages resolved without staff, requests captured and response time overnight.

Free 20-minute call

Want this 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.

Book a free 20-minute call