Local guides · Post 2
How a holiday let in Cardigan or Tenby can answer guest questions without you on the phone
For owners of holiday lets in Cardigan, Tenby and the West Wales coast: how to answer the same guest questions every week without being on the phone, and keep a person approving what goes out.
It's a Tuesday in July. A guest emails to ask about the parking, the Wi-Fi code, and whether the dog is allowed. You've answered all three before, twice this month. You type the same three answers again, because the guest is waiting and it's easier than finding the last reply.
That's the loop: the same guest questions, asked over and over, answered by hand every time. For a holiday let on the West Wales coast, the questions barely change. The parking, the check-in time, the Wi-Fi, the dog policy, what's nearby. Each one is a short, safe answer. Each one is also a small slice of your week.
The maths (a sketch, not a client figure)
Take the questions a holiday let answers in a season. Say 20 minutes a day on average, spread across emails, messages and the phone.
- × 7 days = 2.3 hours a week
- × £25 an hour = £58 a week
- × 20 weeks of the season = £1,160 a year
Now the same questions with a draft step. Software writes the answer from your saved facts, a person reads and approves it in a minute, and it goes out.
- 1 minute × 7 days = 7 minutes a week
- × 20 weeks = about 2.3 hours a year of human time, instead of 46.
The gap is only real if the check happens. Skip the check and you're back to reading every reply from scratch, which is the worst of both.
Score it: the three checks
- Hours. Two or more hours of someone's week, every week of the season. Under that, the hand-over costs more than it saves.
- Repeat. Could a new starter answer the questions from one written page? If you can't write the page, nobody can automate the job.
- Risk-if-wrong. If a slip happens, how bad? A wrong Wi-Fi code is recoverable. A wrong check-in time that leaves a guest waiting is worse.
Our example scores Hours 4, Repeat 5, Risk 3. Verdict: hand it over, but start narrow. One kind of question, drafted and approved, for a fortnight. Then widen.
Try one thing this week (free)
Write the page for the questions you answer most. The parking, the check-in, the Wi-Fi, the dog policy, what's nearby. One line each, in your own words. Then run the page test: give it to someone else and have them answer a guest from it. By Friday you'll know whether the job is writable. If it isn't, it isn't ready to hand over.
Where a person stays
The whole design is one line: software prepares, a person decides. AI drafts the answer from your saved facts, a named human approves it, nothing goes out unchecked. The check isn't a tax on the automation. It's what makes the hand-over safe. Your guests get a straight answer, and you get the season back.
FAQ
They'll notice the answers are right, because they come from your facts. The approval check is where a person confirms the details before anything leaves. What no guest should ever get is an answer nobody looked at.
Those stay human. The automation covers the repeating, safe questions. Anything unusual, a person answers. That's the point of starting narrow.
It works for one let. The questions are the same whether you have one property or ten. The savings just grow with the number of bookings.
The draft waits for a person to approve. If a question is genuinely urgent, it should reach a human anyway. The automation handles the routine, not the emergencies.
No. We connect the tools already in use and file the answers where they belong. No new logins for you or your guests.