Fixed quote after a free call

A hotel guest request log that turns requests into finished tasks

Extra towels, a broken kettle, a late checkout, a cot for room 12: guest requests arrive by phone, message and at the desk, and too many live on sticky notes. We build a workflow that logs every request as a task with a room, priority and owner, sends it to housekeeping or maintenance on the channel they already use, reads room status from the PMS and tells the guest when it is done. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why guest requests get lost between shifts

In a small hotel the person who takes a request is rarely the person who fulfils it. The night porter hears about a dripping tap, the morning housekeeper never does, and the guest asks again at checkout, now unhappy.

Without a request log nobody can see what is open, what is late or which rooms keep generating maintenance issues. Dedicated housekeeping software helps, but many properties run on WhatsApp groups and paper, and need something that fits how they already work.

What we build

What our hotel guest request log includes

One request log

Requests from messages, the AI assistant, phone notes and the desk logged with room, guest, type and time.

Routing by type

Housekeeping, maintenance, kitchen or front desk tasks sent to the right team on Slack, Teams, WhatsApp or your task app.

Priorities and timers

Safety and no-hot-water issues marked urgent; overdue tasks escalate to the duty manager.

Room status from the PMS

Occupied, vacant, departure or out-of-order status read from the PMS so staff knock at the right time.

Guest follow-up

A short message to the guest when the request is done, on the channel they used.

Weekly patterns

Recurring issues by room and type, so the manager can plan maintenance rather than react.

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

    Request received

    A guest request arrives by message, phone note or at the desk.

  2. 02 Automated

    Task created

    The request becomes a task with room, type, priority and owner.

  3. 03 Automated

    Team notified

    Housekeeping or maintenance gets it on their usual channel.

  4. 04 Front desk review

    Staff complete and confirm

    The team marks it done; the front desk checks anything unclear with the guest.

  5. 05 Manager or owner decides

    Room out of order

    Taking a room out of service, moving a guest or offering compensation is the manager's call.

How it behaves

How requests and housekeeping tasks behave

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

What the guest sees

  • A quick acknowledgement of their request
  • Staff arriving at a sensible time
  • A short note when the request is done

What staff see

  • Tasks on the chat app they already use
  • Room status before they knock
  • Escalations when a task runs late

What the automation does

  • Logs and classifies every request
  • Routes tasks and tracks timers
  • Reports recurring issues by room

Edge cases and fallbacks

Request is unclear
Goes to the front desk to clarify rather than being guessed.
Guest has checked out
Task closed and noted; maintenance issues stay open for the room.
Two requests for the same room
Grouped into one visit where it makes sense.
Chat app or workflow outage
Staff fall back to the radio or phone and the log catches up afterwards.

Architecture

Guest requests to housekeeping tasks at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Guest messages Chat, WhatsApp Desk and phone Staff notes n8n workflow Classify, route PMS room status Occupied, vacant Task log Room, priority Housekeeping Maintenance Guest update Request done
  • Input
  • Logic and services
  • Data
  • People
  • Output

How it flows

  1. 1 Requests arrive from guest messages, the desk and phone notes.
  2. 2 n8n classifies each request, checks room status and creates a task.
  3. 3 Housekeeping or maintenance get the task on their usual channel.
  4. 4 When it is done, the guest gets a short update and the log closes it.

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.

Guest requests & housekeeping tasks project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    How requests arrive, who fulfils them, current tools and PMS room status access.

  2. 02

    Design

    2 to 3 days

    Request types, priorities, escalation timers, channels and guest updates.

  3. 03

    Build

    1 to 2 weeks

    Log, classification, routing, PMS status, escalation and guest updates.

  4. 04

    Shadow run

    About 1 week

    Tasks flow to teams while the old process continues, and we compare.

  5. 05

    Launch

    1 to 2 days

    Switch on and train housekeeping and the front desk.

  6. 06

    Support

    Ongoing

    New request types, channels and pattern reports.

What it runs on

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

n8n Mews, Cloudbeds or OPERA Cloud API for room status Slack, Microsoft Teams or WhatsApp Business Platform Airtable or Google Sheets for the log Claude or OpenAI for request classification

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 design

    Request types, routing, priorities and updates.

    $200 – $400

  • Build

    Log, classification, routing, escalation and updates.

    $500 – $1,300

  • Integrations

    PMS room status and team chat channels.

    $150 – $400

  • Testing and shadow run

    Side-by-side run with the current process.

    $100 – $250

  • Launch and training

    Housekeeping and front desk training.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. If you already use housekeeping software, we connect to it where it offers an API instead of rebuilding it.

Monthly running costs you pay directly

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

  • Team chat: Slack, Teams or WhatsApp on their own plans.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
  • AI model usage: Pay-per-use fees for classification, usually small.

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.

US: accessible room features

Requests that affect accessible rooms or features are confirmed by staff, in line with the ADA rule on accessible guest rooms in reservations.

Source: www.law.cornell.edu

EU and UK: staff and guest data

Task logs hold guest names and room numbers, so access is limited to staff who need it and processors are under contract (GDPR Article 28).

Source: gdpr-info.eu

Safety issues go to a person

Anything about safety, such as gas smells, injuries or fire alarms, triggers an alert to the duty manager and your emergency procedure, never an automated reply.

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 housekeeping software questions questions, answered.

A record of every guest request with time, room, type, owner and status. It shows what is open and what is late, and it turns complaints into patterns you can fix.

Not always. Dedicated tools are great for larger properties. Many small hotels do well with a task log and the chat app the team already uses. If you have housekeeping software with an API, we connect to it.

Yes. A QR code in the room can open a short request form or a WhatsApp chat that feeds the same log.

Usually not. Tasks arrive on Slack, Teams or WhatsApp, and staff mark them done with a tap or reply.

Safety and no-hot-water issues are marked urgent and go straight to the duty manager as well as maintenance. Overdue tasks escalate automatically.

Requests by type and room, time to complete, overdue tasks and repeat issues per room each week.

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