The property is full in July. The problem is May's requests.
Masserie, agriturismi, event villas. Requests arrive by phone, WhatsApp, forms and portals, and get lost among each other: whoever isn't called back in time books elsewhere, and whoever has already stayed is never reactivated for a return visit.
The season isn't lost in August. It is lost in April's replies.
None of these moments seems serious while it happens. It is the sum, repeated across the whole pre-season, that decides how full the calendar will be.
The messages of the night
Three requests arrived on WhatsApp between 22:00 and midnight, when people really plan their holidays. The first reply will arrive mid-morning, if it arrives.
Requests from WhatsApp, email and the website flow into a single point and receive an approved first reply, even at night. Inbox AIThree channels, no list
One request is on the phone, one in the email, one on the website form. There is no place to see them all, so there is no way of knowing which one hasn't had a reply.
History and status of every request unified, with the queue of those not yet contacted again. Pipeline & RecoveryThe wedding quote
It has to be written by hand, like the eight before it, with the same information on capacity, seasonality and services included. Forty minutes, and the couple has asked for two more elsewhere.
Recurring questions have an answer approved by the property; the person steps in where judgement is genuinely needed. Knowledge baseThose who haven't confirmed
Two bookings for the day after tomorrow have never confirmed. Nobody contacts them again, and if they don't show up the rooms stay empty without anyone having been able to reassign them.
A reminder before arrival, a follow-up call to whoever doesn't confirm, slots freed up in time to be reassigned. Booking recoveryYesterday's review
A four-star review with a remark about breakfast. Nobody will reply, because in the evening there is no time and by tomorrow it will have slipped down the list.
The review is collected and the draft reply arrives ready for the owner's approval. Review follow-upA guest accommodation business doesn't lose customers because it is worse than the competition. It loses them because the competition replied first, and whoever is organising a trip has stopped waiting.
Not our opinion. Public research, with the source alongside.
more likely to make contact with a potential customer by replying within five minutes rather than thirty. The useful window is much narrower than it seems.
Harvard Business Review · InsideSalesof bookings still come by phone, against 38% from platforms and 22% from the website and Google combined: without a point that collects them all, that 21% risks never being called back.
Osservatorio Incrementoo · Ristorazione 2025fewer no-shows with automatic reminders by SMS, WhatsApp or email. In clinical settings, where measurement is more rigorous, those who receive a reminder are 25% less likely not to show up.
BMJ Open · systematic review, 21 studiesof consumers are inclined to choose a business that replies to all its reviews; 97% read them before deciding. BrightLocal 2026 survey of 1,002 US consumers.
BrightLocalThe pieces that in this sector pay for themselves first.
They aren't all built at once. You start from one, the one that costs most today, and add the next only if the first has paid off.
Capture and first reply, on every channel
Requests from WhatsApp, email, website and phone are collected in a single point and classified in real time. Recurring questions have an answer approved by the property; the rest passes to a person with the context already gathered.
Reminders, confirmations, reassigned slots
A reminder goes out before arrival; whoever doesn't confirm is contacted again. The slot that would otherwise go empty can be reassigned in time.
Draft replies, ready to approve
After the stay the system collects the reviews and prepares a draft reply, ready for the owner's approval before publication.
The first of the month, already read
A narrative letter for the owner and a report already in the format the accountant needs, on the indicators defined together during the analysis.
Not a concept: prototypes already built and put under stress.
We built it with the real needs of two types of Apulian guest accommodation in mind, and put it under stress before the first conversation. Anonymised, as it is.
Built for a historic masseria in Apulia, with a new management and falling reviews in mind.
Booking channel reduced to two personal mobile phones, hundreds of past customers never contacted again, negative reviews with no reply. Four engines, from the first request to the review.
| Activity (per week) | Today, by hand | With the system |
|---|---|---|
| Incoming requests | 150 min · +20 lost | 13 min · 0 lost |
| No-show reminders | 53 min | 6 min |
| Dormant customer reactivation | 100 min | 10 min |
| Review replies | 36 min | 3 min |
The Collector
It replies on WhatsApp in under 3 seconds, collects name and contact details, lets no request drop.
The Confirmation
Automatic reminder the day before. Tables at risk flagged in time to resell them.
The Reactivation
It brings back customers who have been inactive for months, one by one, without spending on advertising.
Reputation
A dignified draft reply to every review, ready within a few hours.
How we calculate it
We calculate the recovery together on your numbers, before any quote, and agree beforehand which value it has to exceed for the work not to have failed.
Built for a property with an events hall, with wedding quotes lost to slow replies in mind.
Not a visibility problem: the problem was speed on quotes. No follow-up on pending deposits, evening requests that waited for a reply until the next day.
| Activity (weekly example) | Today, by hand | With the system |
|---|---|---|
| Event requests captured | variable, depends on who is free | all of them, in under 3 seconds |
| Quotes qualified on the spot | by hand, long lead times | immediate, data collected in chat |
| Follow-up on pending quotes | 0 · no follow-up call | automatic, with priority |
| Review replies | when there is time | draft ready within a few hours |
The Event Collector
Every request, from website, social media or phone, gets a reply in under 3 seconds, with data qualified straight away.
The Follow-up
Automatic reminder on pending quotes, priority on those at risk of going cold.
Reputation
A draft reply in an elegant register to every review, the story gathered at the right moment.
How we calculate it
On tickets this high it takes little to change the sums, and that is why we don't write the number here: we calculate it on your data, in front of you.
The first step, here
The requests that today go unanswered. Thirty days to count them.
In hospitality the piece that pays for itself first is almost always capture: bringing all requests into one place and ensuring none is left without a first reply. It is also the easiest to verify, because the before and after can be counted.
We choose the indicator for this sector together before starting: average time to first reply to a request, or no-shows avoided in the month. It is the yardstick you will judge us by.
If the piece has returned more than it cost, the next one is assessed. If it hasn't, we stop there: no automatic renewal, no penalty, and the system stays yours.
The objections we hear every time.
Our guests want to talk to a person, not a robot.
They are right, and the system doesn't replace that conversation: it serves to get there: the 23:40 request immediately gets a correct reply on availability and basic information, and the next day the person calls whoever is genuinely interested, already knowing what they are looking for.
The real alternative isn't «a person instead of a system»: it's «a system or no reply until mid-morning tomorrow».
We are seasonal. Do we pay for a system in January too?
It is a question that changes the design, not one that blocks it. The pieces are built to be switched on and off with the season, and seasonality is one more reason for the piece-by-piece model: you start from the period when the loss is greatest, almost always the pre-season and not the peak, and assess the rest after seeing that period's numbers.
We already use management software and the portals. Do we have to change them?
No. Channel manager, management software and portals stay where they are: they are tools your team knows and that work. The work lies in the layer that doesn't exist today, the one that collects the requests outside the portals (WhatsApp, phone, direct email) and brings them back to the same place as the others.
We propose replacing a tool only if it is the bottleneck measured during analysis, never out of preference.
Other questions, such as price, data and time required, are answered on the Method page.
How many requests, last month, never received a reply?
If the answer is «I don't know», that is already the most useful piece of information. The diagnostic is twenty questions and five minutes: it returns a score across five operational dimensions and the three priority interventions, without talking to anyone.
Start from the diagnostic (in Italian)