Fixed quote after a free call

Hotel pre-arrival emails with online check-in and upsells

A good pre-arrival email shortens check-in, prepares the room and sells extras guests actually want. We build a workflow that sends it a few days before arrival, collects arrival time, registration details and special requests through a short online check-in form, offers extras such as early check-in, parking or breakfast at their full price, and writes the answers into the PMS as notes and tasks. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why check-in queues start days before arrival

Most check-in delays come from details that could have been collected days earlier: arrival time, registration information, car registration for parking, cot requests and dietary needs for breakfast. The front desk ends up typing them in while a queue forms.

Upsells suffer the same way. Extras are offered at the desk, if at all, when the guest is tired and the line is long. Offered earlier, with clear total prices, they are more welcome and easier to prepare.

What we build

What our hotel pre-arrival email workflow includes

Timed pre-arrival email

Sent a set number of days before arrival, in the guest's language, with directions and what to expect.

Online check-in form

Arrival time, registration details your country requires, car registration and special requests in one short form.

Relevant extras

Early check-in, late checkout, parking, breakfast, packages or room upgrades from your list, shown at the full price including mandatory fees.

Into the PMS

Answers written to the reservation as notes, and accepted extras posted where the PMS API allows.

Tasks for the team

Cots, accessible room checks and dietary needs become tasks for housekeeping or the kitchen, confirmed by staff.

Arrivals list

A daily list of arrivals with forms completed, missing details and accepted extras.

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

    Arrival approaching

    The workflow sees an upcoming arrival in the PMS.

  2. 02 Automated

    Email and form sent

    The guest gets the pre-arrival email with the online check-in link.

  3. 03 Automated

    Answers recorded

    Details, requests and accepted extras are written to the reservation.

  4. 04 Front desk review

    Front desk prepares

    Staff confirm requests, check accessible room needs and prepare keys.

  5. 05 Manager or owner decides

    Upgrades and exceptions

    Free upgrades, waived fees and anything off-policy are decided by the manager.

How it behaves

How online check-in and upsells behave

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

What the guest sees

  • A short pre-arrival email in their language
  • A quick online check-in form
  • Extras shown at their full price
  • A faster check-in at the desk

What staff see

  • A daily arrivals list with forms and extras
  • Requests as tasks for housekeeping or the kitchen
  • Missing details flagged before arrival

What the automation does

  • Reads arrivals and sends emails on schedule
  • Writes answers and extras to the PMS
  • Creates tasks and updates the arrivals list

Edge cases and fallbacks

Same-day booking
Gets a short welcome message only; details are taken at the desk.
Guest asks for an accessible room change
Goes to the front desk to confirm and block the room.
OTA alias email bounces
The guest goes on the arrivals list as missing details.
PMS write-back fails
Answers are kept in the form tool, staff get an alert and the write retries.

Architecture

Pre-arrival and online check-in 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.
PMS arrivals Upcoming stays n8n schedule Days before arrival Pre-arrival email Guest language Check-in form Details, extras PMS notes Requests, extras Front desk Arrivals list
  • Input
  • Logic and services
  • Output
  • Data
  • People

How it flows

  1. 1 Upcoming arrivals are read from the PMS on a daily schedule.
  2. 2 Each guest gets a pre-arrival email with an online check-in link.
  3. 3 The form collects details, requests and extras at full prices.
  4. 4 Answers reach the PMS and the front desk's arrivals list.

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.

Pre-arrival emails, online check-in & upsells project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Current pre-arrival messages, check-in steps, registration rules and extras list.

  2. 02

    Design

    2 to 3 days

    Email timing and wording, form fields, extras and PMS write-back.

  3. 03

    Build

    1 to 2 weeks

    Email, online check-in form, PMS notes, tasks and the arrivals list.

  4. 04

    Shadow run

    About 1 week

    Forms go to a share of arrivals while staff compare with the desk process.

  5. 05

    Launch

    1 to 2 days

    Switch on for all arrivals and train the front desk.

  6. 06

    Support

    Ongoing

    Seasonal extras, wording and new languages.

What it runs on

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

n8n Mews Connector API, Cloudbeds API or OPERA Cloud Reservation API Your email provider A GDPR-suitable form tool or a custom form Stripe Payment Links for prepaid extras

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

    Check-in steps, registration rules, extras and wording.

    $200 – $400

  • Build

    Email, form, extras, tasks and the arrivals list.

    $500 – $1,300

  • Integrations

    PMS, email provider and payments.

    $150 – $400

  • Testing and shadow run

    A share of arrivals run side by side with the desk.

    $100 – $250

  • Launch and training

    Switch-on 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. Posting charges to folios depends on your PMS API. Email and form costs are billed to you 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.

  • Email and forms: Your email provider and form tool on their own plans.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
  • Payments: Stripe at its published card rates for prepaid extras.

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: total price including mandatory fees

The FTC rule on hotel and ticket fees, in effect from May 12, 2025, requires the total price including mandatory fees to be shown clearly and most prominently. Extras in the email follow the same rule.

Source: www.ftc.gov

UK: guest registration details

Hotels must record full name and nationality of guests aged 16 or over, and passport details for foreign nationals, under the Immigration (Hotel Records) Order 1972. The form collects only what the rule requires.

Source: www.legislation.gov.uk

US: accessible room requests

Requests for accessible rooms are confirmed by staff, because the ADA rule requires requested accessible rooms to be held and blocked in all reservation systems.

Source: www.law.cornell.edu

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 pre-arrival email and upsell questions questions, answered.

Arrival details, directions and parking, check-in time, a link to online check-in and a short list of relevant extras with clear total prices. Keep it short and useful; the form does the work.

It is the online check-in step: guests submit details and requests before arrival, and the front desk sees them in the PMS. Keyless entry and kiosks are separate systems we can connect where they offer an API.

Ones that solve a real need: early check-in after a red-eye flight, parking, breakfast, late checkout or a room with a view. We start with your current extras and use the reports to see what guests take.

Accepted extras can be posted to the reservation where the PMS API allows, or paid through a payment link. Card details stay with the payment provider.

Some PMS platforms include pre-arrival messaging. If yours does, we connect and extend it, such as extras, tasks and the arrivals list, rather than duplicating it.

Share of guests completing online check-in, check-in time at the desk, extras accepted and revenue from extras by type.

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