Hospitality and tourism
Every guest enquiry answered, in the guest’s own language
A holiday rental agency brings enquiries from every channel into one CRM, gets replies drafted in the guest’s language for staff to approve, and turns bookings into tasks for cleaning and maintenance.
Holiday rental agency on the Adriatic, 12 people
Enquiries and bookings
New enquiry 2
Offer sent 2
Booked 1
The build at a glance
The sector
Tourism on the Adriatic is seasonal, and the season is short.
Enquiries arrive in several languages through booking platforms, the website, email and messaging apps, often outside working hours. A guest who waits for an answer books elsewhere. At the same time each booking sets off practical work: arrival instructions, cleaning, repairs and a report to the owner of the property.
Where the time goes
Each channel had its own inbox and each employee their own way of keeping track. In high season enquiries waited while staff handled arrivals, and nobody could say how many were unanswered. Replies in less common languages took longest. Cleaning was arranged by phone and messages, and owner reports were compiled at the end of the season from several spreadsheets.
Enquiries are scattered across platforms, email and messaging apps
Replies in the guest’s language depend on who is on shift
Cleaning and maintenance are arranged by phone
Owner reports are assembled by hand from several sources
One system around how the work is done
Booking to arrival
- BookingBooking confirmedFrom your channel manager
- CRMGuest and stay recorded
- EmailArrival details requestedIn the guest’s language
- TasksCleaning scheduled between stays
- MessageCheck-in instructions queued
- 01
One CRM for every enquiry, whatever channel it came through, with the guest, the dates and the property attached
- 02
An AI step that reads the enquiry and drafts a reply in the guest’s language from availability and your house rules, for staff to approve and send
- 03
Reminders for offers that have had no answer, so follow-up does not depend on memory
- 04
Scheduled messages before arrival, on arrival day and after departure, with directions and check-in details
- 05
A booking creates cleaning and maintenance tasks for the right team, with the times of departure and next arrival
- 06
A report per property owner: occupancy, bookings and costs, prepared from the same data
How the project runs
Four steps, one process at a time
- 01
Map the process
We follow an enquiry through to departure, in season and out of it, and note who does what and through which channel.
- 02
Pilot one process
Enquiries from the website and email go into the CRM first, with drafted replies for a few properties.
- 03
Extend
The remaining channels, guest messaging and cleaning tasks are added before the season, and owner reports after it.
- 04
Care
We keep the connections running through the season and use the quiet months to adjust templates and add what was missing.
What changes for the team
- Staff approve and send replies instead of writing each from scratch
- An unanswered enquiry is visible to the whole team
- Cleaning is scheduled from bookings, not from phone calls
- Owner reports are prepared from data that already exists
Every enquiry is in one place with an owner and a status, and a drafted reply is waiting when staff open it. Guests receive the practical information at the right moment without anyone remembering to send it. Cleaning teams and property owners get what they need from the same booking data.
A composite scenario based on typical projects in this sector. It does not describe a named client, and the sample data is illustrative.
The same working day, before and after
What a few ordinary moments look like once the system is in daily use.
Questions from this sector
Can we keep our channel manager and booking system?
Yes. Availability, rates and bookings stay where they are. The CRM reads from them and adds what they do not cover: conversations, tasks and reports.
Are replies sent to guests automatically?
Drafts are prepared automatically, and staff approve them before sending. Routine messages you have agreed in advance, such as arrival instructions, can go out on a schedule.
Which languages are covered?
The ones your guests write in most. We set them up with you and check sample replies with someone who speaks each language before going live.
What about guest data?
It stays in accounts that belong to you, and only the data needed for a stay is used. We agree with you how long it is kept.
When is the right time to introduce this?
Outside the high season. We start with enquiries from one channel, so the team gets used to it before the busy months.
Use cases in this story
Every enquiry in the CRM, without retyping
Enquiries from forms, email and chat become contacts and deals in your CRM, with the right person notified.
Open use case CRM implementationBusiness automationNo open quote left without a follow-up
The CRM reminds the owner, drafts the follow-up and shows which deals have gone quiet.
Open use case AI integrationsBusiness automationA support inbox that sorts itself
Incoming messages are sorted by topic and urgency, routed to the right person and given a draft reply.
Open use caseMore sector stories
Show us one process. We will show you what it could look like.
The analysis is free, takes about an hour of your time, and ends with a written summary you keep.
Prefer to read first? See examples