One holiday let is a side business. Five is a job. Fifteen is an operation where nobody remembers which property has the temperamental boiler, which has parking for two cars and which one guests always struggle to find in the dark.
The messages multiply faster than the revenue, and they all arrive on changeover day.
Where it breaks
A single owner can hold the details of one cottage in their head. Across a portfolio, nobody can, so answers become vague, wrong or slow. Guests notice immediately, because the answer to whether there is a cot is either yes or no and they can tell when someone is guessing.
Build a guest guide per property
Access, parking, Wi-Fi, appliances, heating, bins, local information and checkout, with photographs of the actual controls in that property. This is the foundation, and it is the thing most portfolios never complete because it feels like a large job.
Standardise the structure, not the content
Every property answers the same categories of question. The answers differ entirely. That combination is what lets a portfolio scale without guests receiving generic replies, which is the framework described in AI receptionist for businesses with multiple locations.
Separate the enquiry types
Pre-booking questions, in-stay questions and owner enquiries are three different conversations that arrive through one inbox. Routing them separately is the first practical improvement most portfolios can make.
Pre-booking questions need the property
Beds, pets, parking and the area decide bookings, and they are property-specific, as covered in guest questions before booking a holiday rental.
In-stay questions need speed
Guests who cannot get in, cannot work the heating or cannot find the bins need answers now, not after changeover. Answering from the property's own guide, at any hour, solves nearly all of these without anyone stopping work.
Guest: We are at the cottage and cannot get the Wi-Fi to connect. Assistant: The guide for that property shows the network name and password, with a photograph of the router and where it sits, and explains how to restart it if it is not responding. If it still will not connect after that, I can pass it to the team as an urgent message.
Maintenance and reporting problems
Guests report faults that need triage: something genuinely broken, something they cannot work and something that can wait until changeover. Capturing what has happened, which property it is and how urgent it seems lets the team dispatch properly rather than driving between properties reacting to whoever messaged most recently.
Changeover day is the pressure point
Cleaners, outgoing guests, incoming guests and maintenance all converge. Automating the routine answers on that day alone removes a large share of the operational stress across a portfolio.
Owner enquiries are a separate business
Property owners considering letting through you are a different audience with different questions, covered in holiday let owners and the questions before they instruct.
Direct bookings at scale
Commission across a portfolio is a significant annual figure, and the case for direct booking is covered in direct bookings that save holiday let owners commission.
Setting it up
Write a guest guide for each property in the same structure, then answer from them at any hour. SpideyChat for hotels and holiday lets answers from your own pages, and the guides to installing the widget and training your bot explain how.