What's changing inside Morphic.

Start from the booking context: Morphic can help coordinate a known cleaner or teammate through WhatsApp, follow up for confirmation, and surface an exception to the host.

You can correct the turnover status when plans change, rather than leaving an out-of-date task attached to the next guest’s stay.

A cleaner confirmation records coordination, not an independent physical inspection or a guarantee that the property is guest-ready. Local people and specialist tools remain the right fit for field work, inspections, repairs, contractor payments, and cleaner marketplaces.

Choose a future date, a recurring schedule, or a booking event such as checkout — then keep the routine tied to that context instead of relying on a separate to-do list.

Date-anchored reminders update or cancel when the connected booking changes, so a moved or cancelled stay does not leave the original reminder behind.

Automations remain reviewable. Copilot is the default; Autopilot only runs the scoped, reversible actions a host explicitly authorizes.

Standing preferences — like "always confirm cleaning" or "default to three nights" — can be learned over time from host instructions.

One-off dates, current prices, and single-instance exceptions are never treated as durable preferences.

Nothing changes without host review: proposed Operation Guide updates are presented for approval first.

The assistant no longer blocks new input while a reply is being drafted.

This keeps fast back-and-forth moving even when a longer reply is still being prepared.

The preview experience brings more listing, calendar, and host-knowledge work into a mobile-friendly flow.

This remains a preview until the experience is approved for broader product communication.

Reply drafts and supported action proposals can wait for host review before anything is sent or changed.

Selected routine work can move to Autopilot without turning the whole operation into an unattended system; exceptions and high-impact decisions remain under host control.

Hosts can see what an automation covers, where review is required, and how to change or pause it.

The aim is bounded, understandable automation rather than an all-or-nothing switch.

Supported pending actions can be planned and reviewed in context, with reversal guidance where the workflow allows it.

High-impact judgment calls still require the appropriate host or team decision.

Recommendations are connected to the relevant host decision instead of being presented as generic assistant answers.

Booking performance, listing freshness, and readiness signals can point to the next host-approved improvement.

Availability and pricing changes remain subject to the connected channel and the host's chosen settings.

A host can ask what needs attention, review a draft, correct guidance, or inspect a supported next action by text or voice from the surface that fits the moment.

The assistant remains the product experience; the channel is the access point.

The workflow is built around reachable, host-defined information and a recovery plan.

Access details, timing, cleaning readiness, smart-lock state, lockbox or key problems, late arrival, and safety concerns remain subject to host judgment.

When a host corrects a response, the correction can become a candidate for reusable guidance.

Corrections remain reviewable rather than silently rewriting the assistant's entire memory.

The workflow includes proactive assistant messages, turnover checks, coordinated reminders, and reviewable follow-up work.

Morphic can coordinate software context and the people responsible for physical work; it does not clean, inspect, repair, unlock, or provide emergency response at a property.

The workflow keeps the host in the decision loop and accounts for the connected channel's calendar state.

It is a bounded calendar workflow, not a promise of a particular occupancy or revenue outcome.

The assistant should report what it did, what it could not do, verify the supported result, and show when the host needs to take over.

The exact action set depends on the connected workflow.

Owner, admin, and member access remain distinct.

Team access does not mean that every person can approve every sensitive action.

Hosts can keep guest-message review close to the phone instead of relying on a desktop dashboard.

The mobile experience is another way to reach the assistant; the product remains the host-controlled workflow behind it.

Guest questions, booking context, listing facts, and host decisions can point toward the next improvement.

Repeated questions, review themes, booking performance, and listing freshness can become a practical readiness signal rather than a generic score.

The goal is to connect the improvement to the problem that revealed it.

Later improvements reduced unnecessary intermediate updates and made deferred responses easier to follow.

Response timing depends on the source facts, the conversation, the action, and host-defined boundaries.

Hosts can inspect supported reservation or alteration requests alongside the affected booking rather than treating them as ordinary messages.

The connected channel, booking context, and explicit host decision remain part of the workflow for changes that affect a stay.

The assistant has more operating context for real hosting workflows rather than answering from a generic chat window.

Hosts can review or edit sensitive reply drafts and supported actions before sending or execution, including review-related follow-up where the workflow allows it.

The assistant can point to missing or unclear information that may belong in the listing, the AI Guide, or a host follow-up workflow.

Hosts decide which improvements become part of the home’s guidance.

The goal is to help hosts notice the important exception without turning every routine event into an interruption.

Attention is tied to the relevant workspace and conversation context.

The assistant is designed to help run today's Airbnb work and improve tomorrow's operation while keeping sensitive decisions with the host.

WhatsApp and the web workspace became connected ways to reach the same host assistant.

Hosts can refine the assistant with the facts that make one home different from another.

A missing fact remains a missing fact: Morphic should ask, draft cautiously, or request host input rather than inventing a confident answer.

The assistant could distinguish a routine question from a request that depends on booking status, calendar state, review context, or host approval.

This became the basis for a connected guest-service workflow rather than a standalone message inbox.

A connected Airbnb listing can move toward useful assistant work in about one minute without required guide or rules setup.

The 21-day trial requires no card, so hosts can connect every listing before deciding whether the workflow fits.

The goal was to help a host move from a connected listing to a usable assistant without first configuring a large property-management system.

Hosts could see the setup state of the listing before moving into daily workflows.

Hosts gained an additional way to reach the assistant and review hosting work from a familiar mobile conversation surface.

Guest conversations remain subject to the same host knowledge, approval, and safety boundaries as other Morphic surfaces.

Availability and pricing changes remain subject to the connected channel and the host’s chosen settings.

The controls are designed for deliberate host decisions rather than invisible calendar mutation.

The early workflow connected listing identity with booking events and calendar state, so a host could work with more than a standalone message inbox.

This created the foundation for later guest communication, booking, pricing, and host-assistance workflows.