The Sentence AI Support Quotes Back to a Guest

Support tools quote. A policy written as a paragraph gets quoted as a fragment, and the fragment is what the guest will hold you to.

Last updated: October 19, 2026

Airbnb's AI chat support now runs in more than fifty languages, with voice support arriving. Guests will use it. And any tool that answers in a sentence answers by finding a passage and returning it, which means your house rules are being read as quotable lines whether you wrote them that way or not.

Key Takeaways

• Quotation strips context, not words. The sentence comes back intact. The paragraph around it doesn't.
• Conditions are what get lost. "Early check-in isn't guaranteed" plus a separate paragraph about asking the night before becomes "yes" by the second hop.
• One rule per sentence is the whole technique. Condition and consequence in the same line, or the line will be quoted without one of them.
• Digits survive, words blur. "After 9pm" travels. "Late in the evening" turns into whatever the guest hoped.
• Every question you answer twice is a policy you haven't written. The log of those questions is the review.

Which sentences get quoted

Not all of your text has equal exposure. The lines that get pulled out and repeated are the ones that answer a question with a condition attached. Frequency does the ranking for you.

The most quoted line in most listings is the check-in window. It's the first practical question a guest has, it has a number in it, and it sits in a rule that's often written as a paragraph. Something like "check-in is from 3pm, and if you're arriving later just let us know and we'll arrange something" contains a permission, a condition and an escape hatch, all in one sentence. A tool returning that sentence gives the guest all three. A tool returning half of it gives them the permission.

Next is late arrival. Then parking, which is usually the vaguest of the lot. Then pets, extra guests, early check-in, luggage storage and rubbish. Each is a yes-or-no question with a condition, and each is a line a guest will quote back at you with your own name on it.

The pattern is worth stating plainly. Questions with binary answers get quoted most, because a retrieval tool only has to find one line to answer them. Questions that need judgement get answered differently, usually by a human, usually later.

One asymmetry to keep in mind. Guests rarely read your rule section end to end. They read the part a support answer surfaced, and that becomes their working understanding of your home. The rule section isn't a contract anyone reads in full. It's a set of sentences waiting to be picked up one at a time.

That's the practical reason to write for quotation. You're not optimising for a machine. You're making sure that the shortest true version of your policy is also the version that travels.

Why short answers win

A quoted fragment is a sentence without its neighbours. Everything you used to establish context — the tone, the exception above it, the caveat below it — is gone. What remains is the claim.

Writers tend to solve this by adding more. More caveats, more warmth, more explanation. That makes the paragraph truer and the fragment worse, because the fragment is now a smaller slice of a longer text, and the condition sits further from the permission.

There's a second effect, and it's the one that produces bad arrivals. Hedged language reads as permissive when it's quoted. "Early check-in is sometimes possible" is accurate in context and reads as encouragement out of context. "We'll try" reads as agreement. "Usually fine" reads as fine.

Three mechanics explain most of it.

The condition falls outside the quoted span. If the sentence says "yes, subject to availability" the condition travels. If the next sentence says it, it doesn't.

The hedge outranks the limit. "Generally" and "normally" survive quotation better than the number that follows them, because the number needs the sentence to make sense.

The exception is written as a separate paragraph. Guests don't read paragraphs in a support answer. They read the sentence they were given.

None of this argues for being blunt to the point of coldness. It argues for putting the warmth and the limit in the same place, so they can't be separated in transit.

Think of it as hops. A direct answer takes one: question in, sentence out. A conditional answer takes two, and the second hop is where meaning escapes. The shorter the path between your policy and the guest's understanding, the fewer places it can change shape.

Writing policies that survive quotation

Five rules cover almost every policy you'll ever write.

One rule per sentence. If a sentence contains two rules, one of them will be quoted and the other will be lost. Split them, even if the paragraph reads a little choppy afterwards. Choppy is a small price for accurate.

Keep the condition beside the permission. "Early check-in is possible if the previous guest leaves by 11 and you ask after 6pm the day before." Everything a guest needs is in the span. A tool can return that whole line and still be right.

Use digits. "After 9pm" survives. "Late in the evening" doesn't. This applies to times, nights, guests, fees and distances. Numbers also make a policy testable, which is useful when the two of you disagree later.

State the default, not just the exception. "Check-in is 3pm to 9pm. After 9pm, message me and I'll send the lockbox code." The default answers the ordinary case, and the exception answers the unusual one, and neither needs the other to be true.

Write the consequence into the same sentence as the rule. "Pets are welcome, at 15 per night, maximum two." The number sits inside the permission, so a quoted fragment can't grant free pets.

One more, less about wording. Keep the policy text where the conversation happens. LOCALSBNB's inbox connects to Airbnb, so the thread and the booking sit together and you can check an arrival time before you answer rather than guessing at it. localsbnb.com

Reviewing the ones that didn't

You'll know a policy failed when a guest arrives with an expectation you didn't set. That's late, and it's expensive. The review that catches it earlier is dull and takes twenty minutes a month.

Start with the questions. Scroll your last twenty conversations and write down every question a guest asked that your listing or your rules should have answered. You'll see repeats within three screens. Each repeat is a sentence that doesn't exist yet, or exists in a form that didn't survive being read.

Then test the lines you have. Take the five most-quoted policies and read each one as a standalone sentence, with nothing before or after it. Ask what a reasonable guest would conclude. If the conclusion is more generous than your actual policy, the sentence is the problem, not the guest.

Then check the gap between the two surfaces. Your listing rules, your arrival message and your replies should say the same thing in the same words. When they differ, the shortest version wins, because that's the one that gets repeated. If the shortest version is also the most generous, you've found the leak.

Finally, keep a note of the corrections. Every time you clarify something mid-conversation, that clarification belongs in the rule, not only in the thread. A thread helps one guest. A rule helps the next forty.

The note doesn't need software. One line per repeat, kept somewhere you'll see it, reviewed when you next edit the listing. What matters is that the clarification gets written once and then lives in the rules, where every future guest inherits it.

FAQ

Should I make my house rules shorter overall?

Shorter sentences, not fewer rules. A page of short lines beats a paragraph of long ones, because each line can be quoted alone and still be true. Cut the connective tissue, keep the conditions.

Does the platform's support tool quote my rules directly?

It can return text that matches what a guest asked about, and the exact behaviour isn't published. Write as if any line could be repeated on its own, and the question stops mattering.

What about policies I can't state simply?

State the simple version and point to the detail. "Deposit is 200, refunded within five days of checkout unless there's damage." That's one sentence, it's true, and it's short enough to be quoted without losing the exception.

Your rules are being read in fragments, by guests and by the tools answering them. Write each line as if it will travel alone, because it will. If you want the conversation and the booking in one place while you check an arrival, localsbnb.com keeps the Airbnb inbox beside the calendar.

---

This is general guidance for hosts, not legal, tax or insurance advice. Local rules and platform terms change, so check the current text with the competent authority and the platform's own terms.