Human review layer
AI is useful for routine guest questions, but Airbnb hosting includes money, safety, access, cleaning, complaints, damage, and policy exceptions. Morphic Host Approval is the safety layer that lets AI move quickly on known facts and pause when the host should decide.
AI host assistant role
Host Approval is what makes faster replies credible. It separates routine facts from promises that affect money, safety, access, service recovery, or the guest's trust.
See the full AI host assistant workflowUse automatic answers only when the assistant has approved facts and low risk.
Use drafts for tone-sensitive or context-heavy messages where the host may want to edit.
Use host approval before refunds, access changes, complaints, safety, damage, cleaning uncertainty, or policy exceptions.
Host scenario
What Morphic does
Acknowledges the issue carefully, gathers the relevant context, and prepares a draft instead of pretending full automation can solve a real-world problem.
Host control
Escalates access, safety, compensation, or service-recovery decisions to the host.
Host scenario
What Morphic does
Summarizes the complaint, checks relevant rules, and prepares a host-review draft.
Host control
Does not approve money or compensation without explicit host review.
Host scenario
What Morphic does
Uses the approved rule if one exists; otherwise explains the decision needed and drafts a safe response.
Host control
The host decides whether the exception is allowed and whether it should become future guidance.
Workflow
The workflow should classify the message before drafting. Routine facts can be answered quickly; uncertain or high-impact promises need context, a draft, and host approval.
Morphic checks whether the guest is asking for a known fact, a subjective judgment, a policy exception, or a real-world action.
Low-risk known facts can move faster. Medium-risk replies can become drafts. High-risk or uncertain decisions pause for host review.
The host sees why Morphic paused, what context matters, and what draft or decision is proposed.
The outcome can improve AI Guide memory and future escalation behavior for the listing.
Boundaries
Host Approval is not a claim that AI can handle emergencies, repairs, inspections, or local service alone.
The safest workflow does not fully automate refunds, complaints, safety, access uncertainty, cleaning status, damage, or policy exceptions.
Host review should be concise enough to be useful, not a second inbox that doubles the work.
FAQ
Refunds, complaints, safety issues, damage, access uncertainty, cleaning status, early check-in, late checkout, policy exceptions, and unclear real-world details should usually pause for host review.
No. It focuses AI on the work it can do safely: routine answers, context gathering, drafts, summaries, and reusable guidance, while preserving host judgment for high-impact moments.
Yes. A short, honest holding acknowledgement can keep the guest informed without making a promise the host has not approved.
Approval workflow
Host Approval is the safety boundary behind faster guest service: routine known facts can move quickly, while refunds, access uncertainty, complaints, safety, damage, and policy exceptions pause for human judgment.
