We’ve automated a lot of our guest messaging. Door codes, directions from the station, luggage storage, trash separation, how the air conditioner works: a chatbot grounded in each property’s own information answers those in seconds, and it’s usually more accurate than a tired human at 11pm.

One group of messages still comes to me, though, and I don’t think that’s going to change: “Can we move our dates?”, “One of us can’t come anymore, can we get money back?”, “We arrived late because of a typhoon, can you refund the first night?” These are the ones that take real judgment, so this post covers how we handle them.

TL;DR

  • Reservation changes and refund requests are the main guest messages that still need a human, because each answer costs or earns you money.
  • Always process changes and refunds through the booking platform. Off-platform deals put your payout protection and your records at risk.
  • A change in dates, guest count or effective nightly rate can change the accommodation tax you owe, and in jurisdictions with price bands a discount can move a stay into a different band.
  • A simple four-question check (calendar, sunk cost, policy, goodwill) makes most decisions quick and consistent.
  • Reply fast even when the answer is “let me check.” A prompt acknowledgment calms most guests down.

Why can’t a chatbot handle reservation changes and refunds?

A chatbot shouldn’t handle them because every answer is a financial decision, and the right one depends on things the bot can’t see. The bot can explain your cancellation policy. It can’t know that the week around the date change is already fully booked, that the cleaner has been paid, or that this guest has stayed with you three times.

Most guest questions have answers that are specific to the property but don’t change. Refund and change requests are the opposite. They’re about one reservation, they’re often emotional, and whatever you say can be quoted back to you in a review or a platform dispute. So we let the bot recognize them and pass them to a person, and it’s designed not to promise anything.

What kinds of change requests do we actually see?

Almost all of them fall into five types:

  1. Date shifts: same number of nights, different dates. These are often easy if the new dates are open.
  2. Shortened stays: a flight changed or plans fell through, and the guest wants money back for the nights they won’t use.
  3. Guest-count changes: someone drops out or joins. This can affect pricing, bedding and, as I explain below, tax.
  4. Late arrivals or early departures because of disruption: typhoons, cancelled shinkansen, missed connections. In a Japanese autumn this is very real.
  5. Complaint-driven refunds: “the room wasn’t what we expected.” This is really a service-recovery conversation that looks like a refund request.

Sorting a message into one of these first stops you from treating every request as a crisis. A date shift and a complaint-driven refund need completely different responses.

Should you handle changes on the platform or off it?

Keep everything on the platform where the booking was made. Use its alteration and refund tools, even when a guest suggests “just sending the difference by bank transfer.”

There are three reasons. First, off-platform arrangements generally fall outside whatever host protection or dispute process the OTA offers. If something goes wrong, you have nothing to point to. Second, your records need to match your payouts. At tax time, a refund that exists only in a chat thread is a reconciliation headache. Third, most platforms’ terms discourage or prohibit taking payment outside the platform, and it isn’t worth risking your listing for that.

For direct bookings, the same principle applies to your own system. Record the change in the reservation itself, not just in the conversation.

What happens to accommodation tax when a booking changes?

A changed booking can change the accommodation tax you owe, so update the numbers along with the reservation. Japan’s accommodation tax is set by local jurisdictions such as prefectures, cities and towns, and is usually charged per person per night. Changing nights usually changes the tax proportionally, but a change in guest count should be recalculated from the final per-person, per-night accommodation charge. In banded systems, fewer guests can sometimes increase the per-person rate. In Tokyo, for example, one person staying alone in a ¥20,000 twin room owes ¥200, while two people sharing it owe ¥100 each.

The less obvious issue is the rate. Jurisdictions such as Tokyo Metropolis and Osaka Prefecture use price bands, where the amount per person depends on the per-person nightly accommodation charge. If the operator itself discounts or refunds the accommodation charge, the discounted amount may be the tax base, and in some cases that moves the stay into a different band. Third-party points, subsidies or OTA-funded discounts may be treated differently, so check the local FAQ. Deciding whether the band is based on the rate before or after cleaning fees is already a common filing mistake we see, and a mid-stay adjustment makes it easier to get wrong. For example, Tokyo and Osaka include mandatory cleaning fees in the accommodation charge, while meals and consumption tax are excluded. Always confirm the local rule.

Tokyo is also changing its rules. Its current ¥100/¥200 bands apply to hotels and ryokan until 2027-03-31. From 2027-04-01, Tokyo will also cover simple lodgings and minpaku, with a 3% tax on stays of ¥13,000 or more per person per night.

Don’t assume the OTA payout has handled accommodation tax. Check the reservation and payout records and your local rules. In many jurisdictions the accommodation operator is the special collection obligor and must reconcile and remit the tax, so you’re the one who has to catch this. We recalculate with the final reservation data, and this is one reason we built japan-stay-tax as an open-source library: the calculation should come from the booking data, not from memory. Also keep your guest register accurate when the names or number of guests change.

How do we decide whether to say yes?

We ask four questions in this order:

  1. Calendar: Can we realistically resell the freed nights? A shortened stay in peak koyo season is very different from one on a quiet Tuesday in February.
  2. Sunk cost: What have we already spent? Cleaning scheduled, linens prepared, consumables stocked.
  3. Policy: What did the guest agree to? We start from the published cancellation policy, and it gives us a clear default.
  4. Goodwill: Would a small concession protect a review, a repeat guest or our own sense of fairness? Weather disruptions often land here.

When the calendar is flexible and our costs are low, we usually agree to date shifts. For shortened stays we often offer a partial refund that depends on whether we manage to rebook the nights. Complaint-driven refunds get a fix first (a cleaner sent back, an item replaced) and money second.

What should the reply look like?

Reply quickly, even if you don’t have the answer yet. Something like: “Thanks for letting us know, and sorry about the flight. I’m checking the calendar now and will confirm the options within a few hours.” That takes the pressure off. Then give a clear, specific offer, point to the platform’s alteration request, and don’t use vague phrases like “we’ll see what we can do.”

Consistency is what keeps this manageable. Write down how you’ve handled past cases so that the next person who covers your inbox, or you six months from now, can make the same call.

FAQ

Q: Should I give refunds outside Airbnb or other OTAs to save time?

No. Process refunds and changes through the platform that took the booking. Off-platform arrangements can leave you without dispute support, cause problems when you reconcile your payouts, and may breach the platform’s terms.

Q: Do I have to recalculate accommodation tax if a guest shortens their stay?

Generally yes. Fewer nights usually reduces the tax proportionally, and a change in guest count should be recalculated from the final per-person, per-night accommodation charge. In jurisdictions with price bands, an operator-funded partial refund can also change which band applies. Check your local jurisdiction’s rules.

Q: Can a chatbot help with refund requests at all?

Yes, as a triage step. It can recognize the request, collect the reservation details, explain the published policy and hand the conversation to a human. It shouldn’t commit to any refund or change on its own.

This post is for informational purposes only and does not constitute legal or tax advice. Please consult a qualified professional for your specific situation.