Send
Known house facts
Wi-Fi, parking, checkout steps, appliance notes, and house rules can send automatically when the source guidance is clear and approved.
Examples
These examples show the difference between safe routine automation and messages that should involve the host. The goal is better guest service without pretending AI can make every real-world decision alone.
Reply pattern
A good Airbnb AI reply example should not only show a better sentence. It should show the operating rule behind the sentence: which facts are approved, where the host keeps control, and what should improve for the next guest.
Send
Wi-Fi, parking, checkout steps, appliance notes, and house rules can send automatically when the source guidance is clear and approved.
Draft
Local tips, tone-sensitive responses, and flexible preferences are better drafted from host guidance when the answer may need taste or caveats.
Pause
Refunds, compensation, failed access, cleaning complaints, damage, safety, and policy exceptions should notify the host before AI promises anything.
What good looks like
The reply should use listing facts, house rules, host-approved local tips, and booking context before general AI knowledge.
Facts like Wi-Fi location can be automated. Promises about refunds, early access, or cleaning status should ask the host.
A good AI host assistant should notice when the same guest question points to unclear listing content or missing guidance.
Reply workflow
The useful product behavior is not only the final sentence. It is the decision path: whether the answer came from approved guidance, whether the promise needed host review, and whether the pattern should improve the listing or AI Guide.
Known fact
Wi-Fi, parking, house rules, appliance notes, and local tips can use host-approved AI Guide content when the fact is clear.
Risky promise
Refunds, complaints, early check-in, lockouts, safety, damage, and cleaning uncertainty should ask the host before the guest receives a commitment.
Repeated pattern
If guests keep asking the same thing, the fix should become listing copy, arrival guidance, local tips, or AI Guide memory.

Example library
These examples are intentionally practical: each one separates guest-facing copy from host control and the reusable guidance Morphic needs before automation becomes safe.
Routine house question
Weak generic reply
The Wi-Fi password should be in the check-in instructions. Please check your Airbnb messages or ask the host if you cannot find it.
Better host-assistant reply
The Wi-Fi details are in the check-in guide. The router is in the living room cabinet under the TV. If the connection drops, unplug it for 20 seconds and plug it back in. I can help if it still does not come back.
Morphic setup
Store the Wi-Fi network, password, router location, and reset step in AI Guides before allowing automatic replies.
Host control
Safe to answer automatically if the Wi-Fi facts are already approved in the listing guide.
Reusable insight
If many guests ask this, the Wi-Fi location should be added to pre-arrival instructions.
Local recommendation
Weak generic reply
There are many restaurants nearby. You can search Google Maps for late-night dining options and check opening hours before you go.
Better host-assistant reply
For a late arrival, I would try the host-approved nearby options that usually work after 10pm. I would avoid recommending a full dinner plan unless the host has confirmed current opening hours.
Morphic setup
Save late-arrival recommendations, distance, caveats, and fallback advice in the local guide instead of letting AI invent options.
Host control
Use host-approved local tips. Ask the host if no late-night option is known.
Reusable insight
Late-arrival guests may need a saved local guide snippet rather than a generic city recommendation.
Early check-in
Weak generic reply
Early check-in may be possible. We will do our best to accommodate your request and let you know.
Better host-assistant reply
Thanks for letting me know. I will check whether the home can be ready earlier and come back to you before confirming anything. Standard check-in is still the safe plan unless the host confirms the earlier time.
Morphic setup
Define the normal check-in time, allowed exceptions, cleaning dependency, and whether early access is ever paid or host-approved.
Host control
Escalate before promising early access because cleaning and inspection status are real-world dependencies.
Reusable insight
If early check-in requests are frequent, define a standing rule or paid option.
Refund request
Weak generic reply
We are sorry for the inconvenience. We may be able to offer a partial refund for the issue.
Better host-assistant reply
I am sorry the Wi-Fi caused trouble during your call. Could you share when it happened and whether the connection recovered? I will flag this to the host before confirming any refund or compensation.
Morphic setup
Set refunds, compensation, discounts, and service-recovery offers as host-only decisions, even when AI can gather context.
Host control
Always escalate before offering money, discounts, refunds, or compensation.
Reusable insight
If Wi-Fi complaints repeat, the listing should clarify speed, router location, and any known limitations.
Access uncertainty
Weak generic reply
Please try the code again carefully. If it does not work, contact the host for help.
Better host-assistant reply
I am sorry you are stuck outside. Please confirm the last four digits of the booking phone number so I can check the right access path, and I am alerting the host now because this needs immediate human review.
Morphic setup
Keep access instructions specific, but route failed-code, identity, lock, and safety cases to immediate host review.
Host control
Access problems need urgent escalation because security, identity, and real-world status matter.
Reusable insight
Repeated access issues should become a lock/code reliability issue, not only a message template.
Cleaning complaint
Weak generic reply
Sorry about that. We want every guest to have a great stay and may be able to offer compensation for the inconvenience.
Better host-assistant reply
I am sorry this was not right on arrival. Could you send a photo of the issue? I will flag it to the host now so they can decide the right next step.
Morphic setup
Use a safe complaint intake path: acknowledge, ask for useful detail, notify the host, and avoid compensation promises.
Host control
Never offer a refund automatically. Collect context, acknowledge the guest, and escalate.
Reusable insight
Repeated cleaning complaints should become a service issue, not only a messaging issue.
Why this matters
Morphic is designed to answer when the context is safe and specific, but pause when a message depends on money, safety, access, cleaning, damage, policy exceptions, or local judgment. That boundary is what makes AI useful for experienced hosts instead of annoying or risky.
Next pages
Use this if you want the parent workflow behind these examples: listing signals, approved guidance, host review, and WhatsApp control.
ReadUse this if you are comparing AI replies, PMS inboxes, native Airbnb tools, and Morphic's Airbnb-first workflow.
ReadUse this if you want a practical benchmark for property context, service quality, escalation safety, and host control.
ReadUse this if the main risk is AI sending refunds, access promises, complaint responses, or other sensitive decisions too freely.
Read