Hospitality

How Guesthouses and Short-Let Hosts Can Answer Guest Questions 24/7

How to automate guest messages for a short-let or guesthouse: answer check-in, Wi-Fi and directions any hour, and keep payments and complaints for you.

· 6 min read

The Fless Blog cover: How Guesthouses and Short-Let Hosts Can Answer Guest Questions 24/7. A composer card shows the host's one-sentence job, with WhatsApp, Gmail and Google Calendar logos.

TL;DR

Short-let hosts and guesthouses can automate guest messages by giving one AI employee the guest-questions job: check-in steps, Wi-Fi, directions, house rules and checkout, answered at any hour from the host's own guide. Payments, damage, complaints and anything unusual go straight to the host. On Fless, you describe that in one sentence, add your house guide, and test it in practice mode before guests arrive.

It is 1.40am and Tunde's phone buzzes on the bedside table.

"Hi, we just landed. What's the code for the gate?" Ten minutes later: "Also, which apartment is ours?" Then: "Wi-Fi password please?"

Tunde manages three short-let apartments in Lekki alongside a day job. Guests are lovely, mostly. But they arrive at all hours, they rarely read the check-in message, and they always need an answer now.

If you host short-lets or run a small guesthouse, this is the job that never clocks off. This guide shows how to automate guest messages for a short-let: answering the routine questions at any hour, while keeping payments, damage and complaints firmly with you.

The questions guests ask, again and again

Most guest messages fall into a small set of questions. Here is a typical list:

When What guests ask
Before arrival "What time is check-in?" "Is there parking?" "Can we check in early?"
Arriving "How do we get in?" "Which building is it?" "Where do I leave the car?"
During the stay "What's the Wi-Fi password?" "How does the generator / inverter work?" "Where's the nearest pharmacy?"
Leaving "What time is checkout?" "Where do we leave the keys?" "Can we check out late?"

Almost all of these have the same answer every time. You wrote it in your welcome message. Guests ask anyway.

What you should never hand over

Before automating anything, decide what stays with you. For most hosts:

  • Money: payments, deposits, refunds and extra charges.
  • Damage: anything broken, missing or dirty.
  • Complaints: noise, cleanliness, anything that sounds unhappy.
  • Safety: security worries, medical issues, emergencies.
  • Exceptions: early check-in, late checkout, extra guests, parties.

An AI employee should answer the routine questions quickly and pass everything on this list to you, with a short summary, straight away.

How to set it up on Fless

Step 1: Describe the job in one sentence

Describe the jobOne sentence

“Answer guest questions about check-in, Wi-Fi and directions any time, and send me anything about payments, damage or complaints.”

Fless designs, tests and sets up the employee from this. Build this employee

That sentence covers the routine questions (check-in, Wi-Fi, directions), the hours (any time) and the boundary (payments, damage and complaints go to you). Fless works through Describe → Set up → Connect → Test → Go live, and shows each stage: understanding the job, designing the employee, picking apps and approvals, writing test conversations and checking it is safe.

Step 2: Write your house guide once

Paste your listing or website, and Fless learns the basics in one click. Then add a house guide to the Knowledge base, one per property if they differ:

  • Address, building and apartment number, with landmarks for drivers.
  • Check-in and checkout times, and how to get in.
  • Wi-Fi name and password.
  • How the power backup, water heater and air conditioning work.
  • House rules: guests, noise, smoking, parties.
  • Nearby essentials: pharmacy, supermarket, restaurants, ATM.

This guide is the single source of truth. Update it, and the employee's answers update too.

Step 3: Decide how access details are shared

Gate codes and key-box codes deserve their own rule. Common choices:

  • Send access details only on the day of arrival.
  • Send them only to the phone number on the booking.
  • Or keep them behind your approval: the employee prepares the message, you tap approve.

Pick one, write it into the job, and test it.

Step 4: Connect your channels

Connect WhatsApp, where most guests message, and Gmail for email enquiries. Connect Google Calendar if you track stays there, so the employee knows who is arriving when. If guests message you on another platform, you can request that app.

Step 5: Test it in practice mode

Before any guest sees it, test it in the sandbox. In practice mode, nothing is really sent: actions are simulated. Try the real ones:

  • "We just landed, what's the gate code?" at 1.40am, from an unknown number.
  • "The AC isn't working" (it should help with your troubleshooting steps, then tell you).
  • "Can we have a party on Saturday?" (it should pass it to you).
  • "There's a stain on the sofa, sorry!" (damage: straight to you).
  • A message in French, then one in English.

Step 6: Go live and read the morning brief

Once you are happy, go live. Every message is logged, approvals wait in your queue, and your Chief of Staff can send a morning brief: arrivals today, questions answered overnight and anything waiting for you.

Messages that stop questions before they start

The best guest message is the one a guest never needs to send. Alongside answering questions, the employee can send short, timely messages so guests have what they need at the right moment:

  • Two days before arrival: check-in time, the address with a landmark, and parking.
  • On arrival day: how to get in, following your rule for access details.
  • The first evening: Wi-Fi, how the power backup works, and who to contact for problems.
  • The day before checkout: checkout time and where to leave the keys.

Keep each one short. Guests read short messages; they skim long welcome letters.

When something goes wrong

Even with a good house guide, things break. The water heater stops, the generator will not start, a neighbour is noisy. Here the employee's job is not to fix the problem, but to make your response faster:

  1. Acknowledge the guest straight away, kindly.
  2. Share any troubleshooting step from your guide, such as the breaker location.
  3. Tell you at once, with the property, the guest's name and a one-line summary.

You then decide what happens next: a call, a technician, or a refund conversation that only you should have.

What changes for the host

Before After
Woken at 1.40am for a Wi-Fi password Guest gets the answer in a minute; you sleep
Same five questions every stay Answered from your house guide, every time the same way
Complaints buried between routine messages Complaints come to you straight away, with a summary
Guests from abroad struggle with English Replies come in the guest's language
No record of what was said Every conversation in the activity log

Why Fless for short-lets and guesthouses

  • One sentence to build. No message flows to draw.
  • Your house guide as its knowledge. Paste your listing, add the details once.
  • Practice mode before guests. Every action is simulated until you are ready.
  • Approvals for what matters. Payments, refunds and access codes can wait for your OK.
  • Your guests' languages. It replies in the language the guest uses.
  • Marketing too. Marketing employees are live today and can plan posts about your properties, for your approval.
  • A morning brief. Your Chief of Staff reports on arrivals and open issues, free on every plan.
  • Fair pricing. A Free plan to build and test, and paid plans from $39 a month plus usage, billed in NGN, GHS, KES, ZAR, USD, GBP, EUR or AED.

Where we are today: Fless is in private beta, and public launch is Tuesday November 10, 2026. Guest enquiry roles are open to early-access teams. See Fless for hospitality and pricing.

Start with your own message history

Scroll back through the last three stays. Sort every guest message into "the same answer every time" and "needed me". The first pile is your AI employee's job. The second pile is the rule for what comes to you.

Write the job as one sentence and join the private beta. Your next 1.40am message can be answered without waking you.

Frequently asked questions

Can I automate guest messages for my short-let?

Yes. An AI employee connected to WhatsApp or email can answer the questions guests ask most, such as check-in time, how to get in, the Wi-Fi password, directions and checkout, from a house guide you write once. On Fless, you set it up by describing the job in one sentence.

Is it safe to let an AI share door codes or Wi-Fi passwords?

Decide carefully. Many hosts let the employee share the Wi-Fi password but keep access codes behind a rule, such as only sending them on the day of arrival to the number on the booking, or only after the host approves. Test the rule in practice mode before going live.

What should the AI never handle on its own?

Payments and refunds, damage, complaints, safety issues, and requests to bend house rules. Set these to come straight to you. On Fless, sensitive actions wait for your approval.

Does Fless connect to booking platforms?

Fless connects to apps such as WhatsApp, Gmail and Google Calendar. If your guests message you through another platform, you can request that app or add your own connection.

Can it reply to international guests in their language?

Yes. Fless employees reply in the language the guest writes in, which helps hosts with visitors from many countries.

Is guest messaging available on Fless today?

Fless is in private beta, with public launch on Tuesday November 10, 2026. Marketing employees are live today. Guest enquiry roles are open to early-access teams.

Found this useful? Share it with someone who answers customer messages by hand.

Describe the job. Fless builds the employee.

Fless is in private beta, with a free plan and paid plans from $39 a month plus usage. We launch publicly on Tuesday November 10, 2026, live online. See a guest-messaging employee for a short-let built live, from one sentence.

All posts