Phones & Front Desk

The Crib, the Late Checkout, the Anniversary: Catch Every Request

AI Agency Massachusetts · 2026-10-12 · 5 min read

A guest emails you in April. They've booked the second week of August, and almost in passing they mention that one of them is coming off knee surgery, so a ground-floor room would mean a lot. You read it on your phone between a checkout and a delivery truck. Of course you'll remember. It's April. There's time.

By the time August actually lands, you've read a few hundred messages like that one. A crib for Room 4. A late checkout because the ferry doesn't leave until four. A quiet anniversary, please don't make a fuss, but maybe a bottle of something waiting in the room. Each one felt easy to hold onto the day it arrived. Stacked up across a season, they're a pile.

And they don't land in one place. One comes by email, one through the Airbnb message thread, one by phone while you're wrist-deep in a clogged sink, one as a text to your cell because the guest kept your number from last summer. By a full Saturday in July, half of those requests have quietly slipped through the cracks, and the ground-floor guest is standing at your desk looking up a staircase. That's how a forgotten crib becomes a one-star review with your inn's name in it.

Why the good requests slip through

It's rarely that you stopped caring. It's that the request and the stay are weeks apart, and the request has to survive everything that happens in between. Six weeks of other guests, other messages, a broken water heater, a no-show, a Tuesday that ate itself. A note you trusted your memory to hold in April doesn't stand a chance.

The channels make it worse. There's no single inbox, so there's no single place to look. A request buried forty messages deep in a booking-site thread may as well not exist on the morning that guest pulls into the lot. You'd have to go hunting for it, and nobody hunts for a thing they've forgotten is there.

Log it the moment it comes in

The fix starts with a habit, not software. Every special request gets written down the second you see it, attached to that guest's reservation, in one agreed place. It can be a notes field in your booking system, a shared doc, or a simple spreadsheet. What matters is that it's always the same place, so there's one list and everyone knows where it lives.

Keep what you capture short and plain:

That last line matters more than it looks. There's a real difference between a request you've noted and a request you've promised. A guest who hears nothing back assumes you missed it, and starts the stay already braced for disappointment. A two-line reply, "Got it, ground-floor room is set for your arrival," does half the work of good service before they've even packed.

Make it surface on arrival day

Logging solves half the problem. The other half is that a note written in April is useless if nobody reads it in August. You need each request to come back to you on its own, the morning the guest arrives, without anyone remembering to go dig for it.

This is where a little automation earns its keep. The pieces are simple, and most small inns can wire them up once and leave them alone:

Now the request finds you instead of the other way around. The note from April shows up on the exact morning it matters, next to the guest's name, and your desk looks like it remembered everything. It didn't. The system did.

What this looks like on a full Saturday

Picture the same July weekend, done right. It's a little before check-in. You glance at today's arrivals and the list already tells you Room 2 needs the pack-and-play, the couple in Room 5 are celebrating thirty years and asked you to keep it quiet, and the guest with the bad knee is downstairs in Room 1, confirmed back in April.

Housekeeping sets the crib before the room's even turned. The anniversary bottle is on ice. When the ground-floor guest walks in, their key is ready and nobody looks surprised. You didn't work harder that morning. You just stopped carrying it all in your head, which is the part that fails first on a busy day.

Where it helps, and where it doesn't

Be clear-eyed about the limits. Software that reads messages is good at catching the obvious ones and flagging them for you. It will still miss the oddly worded request and occasionally flag something that isn't one. Treat it as a net under the trapeze, not the trapeze. A human should glance at the day's list every morning.

And it should never auto-confirm anything that costs money or that you might not be able to deliver. A ground-floor room when you're fully booked, a late checkout on a sold-out turnover day, these are judgment calls, and judgment stays with you. The delicate ones, the surprise anniversary where the tone has to be right, are yours too. Let the tool remember the request. You decide how to answer it.

Worth doing this week

You don't need a big project to stop losing these. Start here:

  1. Pick one place to log requests, today, and tell anyone who works your desk that it's the only place
  2. Go back through this week's incoming messages and log any request you find sitting there unanswered, then reply to confirm each one
  3. Set up a simple daily arrivals list that shows every logged request for the guests checking in that day
  4. Add a short standard reply you can send the moment a request comes in, so the guest always hears "got it" the same day
  5. For anything that needs a crib, a vendor, or prep, give yourself a two-day heads-up so it's never a morning scramble

Getting the logging habit and the morning list in place takes an afternoon, and it's the kind of quiet setup we help inns put together so it runs without you thinking about it. The payoff shows up on the busiest Saturday of the season, when your desk remembers every small promise and your guests never know how close one came to slipping.

Want this working in your business?

We build and manage systems like this for Massachusetts small businesses, scoped in plain English and priced flat.

Call or Text 617-398-0033 Prefer email? mg@brandadvertisers.com · Free consult, no obligation
← All guides