Production evidence note · June–August 2026 · reviewed August 27, 2026
Host control is an operating record, not a checkbox.
Morphic does more than generate a guest reply. In the live product workflow, it proposes work, keeps host decisions visible, records what executed or did not, and turns eligible corrections into controlled future guidance. This is the evidence behind Copilot-first hosting assistance.
Prepared and reviewed by Liam, Founder, Morphic
Current public proof scope: June–August 2026. The same aggregate usage and system-coverage figures appear on Morphic's main acquisition pages so the public evidence does not drift by URL. They are not a customer-outcome benchmark, conversion study, or promise of Airbnb ranking, revenue, or service results.
20+
Hosts using Morphic
80%+
Replies prepared by Morphic
200+
Optimization suggestions and actions
4.82+
Average rating across connected listings
90%
Routine calendar & pricing coverage
“Replies prepared” includes AI-created reply work; “optimization suggestions and actions” combines supported recommendations and assistant actions; calendar and pricing coverage describes deterministic workflow support, not autonomous revenue management.
Direct safety answer
What can Morphic handle, and what must wait for the host?
Morphic starts new Airbnb conversations in Copilot. Known routines may progress only inside host-authorized boundaries; uncertainty becomes a draft or question; consequential decisions pause for review. The operating record keeps the proposal, host decision, execution state, and unresolved work visible.
May proceed within an approved mode
Known, property-specific routine facts
A reply can move faster when the answer is supported by imported listing, booking, calendar, house guidance, or a host-approved rule and the host has authorized that routine. Copilot still remains the default starting state for new conversations.
Draft or ask
Missing, conflicting, or time-sensitive context
Morphic should prepare an editable draft or ask for judgment when the source facts are incomplete, conflict with each other, or depend on readiness that has not been verified. The assistant must not turn uncertainty into a guest promise.
Pause for host review
Money, access, safety, complaints, and policy exceptions
Refunds, discounts, access uncertainty, cleaning readiness, damage, complaints, safety issues, and policy exceptions stay behind explicit host controls. A message, task, or cleaner confirmation is not independent proof that physical work is complete.
Observed operating categories
The record includes actions beyond guest-message drafting.
Calendar and stay rules
Supported calendar, minimum-stay, gap-optimization, and bounded pricing work remains visible to the host through explicit proposal and execution states.
Channel and listing control
Consequential listing-channel changes remain visible decisions rather than silent background work.
Turnover coordination
The workflow records coordination and confirmation states; it does not treat a message or task as proof that physical cleaning is complete.
Controlled learning
Candidate guidance is checked for support, conflict, scope, and existing coverage before it can shape future assistance.
These are aggregate product-workflow records, not claims that every Morphic account used every capability or achieved a particular business result.
The closed loop
Propose, review, execute, and improve.
01 · Propose
Morphic identifies a guest, listing, calendar, review, guidance, or task action that may be useful.
02 · Review
The host can approve, reject, change, let it expire, or take over. High-impact work does not silently become autonomous.
03 · Execute
Supported actions record whether they completed, failed, stayed pending, or became irrelevant before completion.
04 · Improve
Learning candidates are assessed for support, conflict, scope, and existing guide or listing coverage before reusable guidance changes.
What this proves
A controlled assistant can do more than draft.
Real host workflows contain approvals, rejections, expiry, execution, and unresolved work. Those states are product behavior, not failure states hidden from the host.
Learning is also constrained. A candidate fact can be supported, contradicted, already covered, missing from existing guidance, or restricted by a post-booking access boundary. A new message does not automatically rewrite future behavior.
That makes the relevant question more useful than “does the AI reply?”: what can proceed, what needs judgment, what completed, and what should improve before the next guest interaction?
Method and limits
This note uses aggregate operational counts and structured action and learning states. It does not expose guest or host identities, message text, addresses, reservation details, access information, or private support content.
The snapshot is deliberately not presented as a customer testimonial, a statistically representative study, or proof that any one host achieved a commercial outcome. Individual customer stories require separate permission and review.