Maggie runs a six-room guesthouse on the coast. She cooks breakfast, changes beds, does the accounts and answers every message that comes in. She loves her guests. She does not love the fourteenth message of the week asking whether there is parking.
This is a typical week for a one-owner guesthouse, before and after routine enquiries were handled automatically.
Before: Monday
Maggie starts the day with nine messages from overnight. Four ask about availability for dates that are clearly shown on her booking page. Two ask about parking. One asks whether dogs are allowed. One is a genuine booking for a family of four. One is a cancellation.
She answers them all between serving breakfast and stripping beds. It takes an hour, and she replies to the booking last because it needs the most thought.
Before: Wednesday
A couple from abroad write at 11pm her time asking about check-in after 9pm, because their flight lands late. Maggie sees it at 7am, but the couple have already booked a hotel that answered straight away. The issue of guests writing across time zones is covered in late night hotel enquiries from other time zones, and it hits small guesthouses hardest.
Before: Friday
Friday is changeover day. Maggie spends the afternoon cleaning and does not check messages until the evening. There are six waiting, including two people asking whether she has a room that night. By the time she replies, both have found somewhere else.
Counting the hours
Across the week, Maggie spends around six hours answering messages. Most of those answers are already on her website. The hidden cost of this kind of repetition is explored in the hidden hours you lose to repetitive questions, and for a one-person business, those hours come straight out of rest or family time.
After: Monday
Maggie adds a website assistant trained on her own pages. SpideyChat for hotels reads her site, including her house rules, breakfast times and parking notes, and answers from them.
Monday's overnight messages look different. The availability, parking and dog questions have been answered already. What is left for Maggie is the family booking and the cancellation, both captured with names, dates and contact details.
After: Wednesday
The late-arriving couple ask about check-in after 9pm. The assistant explains the late arrival arrangement published on Maggie's site, such as a key box with a code sent before arrival, and captures their details and flight time. Maggie wakes up to a booking request rather than a lost guest.
After: Friday
On changeover day, two people ask about rooms that night. The assistant captures both requests with their details, and Maggie sees them flagged as urgent when she takes a break. She confirms one within the hour.
What does not change
Maggie still greets every guest at the door, recommends her favourite walks and remembers returning guests' breakfast orders. The assistant handles the questions; she handles the hospitality. Enquiries that need her judgement, like special occasions or accessibility needs, come straight to her.
Other small operators with the same problem
The pattern is the same for many one-owner businesses. We looked at it for small fitness businesses in boutique studios with one owner and constant messages. Guesthouses also get questions from non-staying visitors, such as people asking about afternoon tea, which we covered in spa and restaurant enquiries from non-resident guests.
Setting it up
Make sure your website clearly covers check-in and check-out times, parking, breakfast, pets, late arrivals and cancellations. Those pages become the assistant's answers. See what it can capture on the features page, or try SpideyChat and ask it the questions your guests ask.
A good first step is to look back through the last month of messages and list every question that came up more than twice. For most guesthouses, that list is short, and every item on it can be answered on the website.