Creating a house guide: what changed this cycle on Nest

At 11:40 PM on a rainy Tuesday in Lyon, a guest sent four consecutive messages to a Nest host asking how to initiate the damp cycle on a mid-tier Bosch washer-dryer. The host was asleep. The guest spent forty minutes trying variations of the touch panel before giving up and leaving damp linen in the drum overnight, resulting in mildew and a mild review penalty.

This is not a customer service edge case; it is the baseline reality of short-term rentals. Hosts copy-paste six-page PDF manuals or dump raw text blocks into chat threads. Guests do not read six-page PDFs at midnight. They skim, fail to find the specific detail, and ping the host or open a platform ticket.

During this cycle, we rebuilt the house guide workflow inside Nest from the schema up. The objective was straightforward: transform static, passive house rules into an active, machine-readable dataset that feeds directly into Mia’s operational memory.

From Static Text to Structured Nodes

Previously, creating a house guide on Nest involved a single longform text field. Hosts pasted everything from Wi-Fi passwords to garbage sorting rules into one container. When a guest asked Mia a question during their stay, Mia had to parse unstructured text, often misinterpreting vague instructions like "leave the keys by the planter near the back door" when there were three planters on the property.

The new workflow breaks property instructions into discrete, categorized nodes: Access & Keys, Connectivity, Climate Control, Appliances, Waste & Recycling, and House Boundaries. Each node requires three distinct inputs:

1. A precise action statement (e.g., "To light the gas stove, push the dial in for 3 seconds while pressing the electronic igniter").
2. An evidentiary photo or diagram with mandatory alt-tagging.
3. An urgency classification (Standard Operational, Emergency, or Checkout Requirement).

By forcing this structure at creation, Nest converts raw host knowledge into a queryable graph. When a guest asks about the hot water heater, Mia does not scan a 2,000-word document; she queries the Climate Control: Hot Water node directly.

Time-Gated Permissions and Dynamic Exposure

Security remains a core vulnerability in digital house manuals. Leaving gate codes, alarm disarm sequences, or physical key lockbox combinations visible inside a chat thread three weeks before check-in exposes hosts to unauthorized entry. Leaving them accessible three weeks after check-out creates a persistent security leak.

Nest’s updated guide architecture implements time-gated payload exposure. Information marked as Sensitive Access is encrypted at rest and tied directly to the booking state on the WEVONE ledger.

• T-24 Hours: Guest receives location coordinates, public transport instructions, and general house rules.
• T-2 Hours (or upon host mark-as-ready): The key code, Wi-Fi password, and alarm sequences are decrypted and made visible in the guest’s native Nest interface.
• T+2 Hours post checkout: Access codes are revoked on the client interface, and Mia purges the temporary access tokens from the active session context.

This cycle, we also shipped native integration with smart locks from Nuki and August. If an integrated lock is detected, Nest auto-generates temporary, single-stay PIN codes that align exactly with the dispute and stay windows recorded on-chain.

How Mia Operates as the First Responder

To understand how this changes the host-guest dynamic, consider a stay in Lisbon involving Julian (a host managing three apartments) and Elena (a guest visiting from Colombia).

Julian built his Lisbon apartment guide using the new structured editor. Under Appliances: Cooktop, he tagged a photo of the main circuit breaker alongside instructions on how to reset the induction hob if an F-04 error appears.

At 1:15 AM, Elena attempts to cook. The hob flashes F-04. Instead of messaging Julian, Elena opens the Nest interface and types in Spanish: "La estufa no funciona, dice F-04."

Mia reads the query, maps estufa and F-04 to Julian’s Appliances: Cooktop node, executes zero-shot translation, and responds immediately in Spanish with Julian’s exact steps and the annotated photo showing the breaker location. Mia does not ask Julian to intervene unless Elena indicates the step failed.

The interaction takes 12 seconds. Julian’s sleep is undisturbed. Elena cooks her meal. No support ticket is opened.

Dispute Windows and Ledger Verification

The house guide update is not merely an editorial UX improvement; it fundamentally alters how disputes are handled under WEVONE’s transactional escrow framework.

Historically, when a guest claimed a property amenity was broken (e.g., "the air conditioning did not work during my three-day stay"), support agents had to review ambiguous chat logs. Under the new architecture, the house guide version hash is tied to the escrow contract upon booking confirmation.

If a host updates the guide mid-stay—for instance, changing the Wi-Fi network name or modifying trash rules—that update creates a new immutable version on the Nest ledger. The guest’s stay contract remains pegged to the version active when their check-in window opened, unless the guest explicitly accepts the operational update inside the app.

During a formal dispute, WEVONE’s automated triage checks three deterministic data points:

1. Did the house guide contain explicitly documented operating steps for the disputed item?
2. Did the guest query Mia or the host regarding the issue during the active stay window?
3. Did the host or Mia provide the documented resolution within the mandatory response SLA?

If a host failed to document how to operate a complex heating system, escrow adjustments lean toward the guest. If the host documented the step precisely in the guide and Mia presented it to the guest upon query, the host’s escrow payment remains protected against retroactive claims of non-functional amenities.

Limitations and Open Questions

While the structured guide builder reduces friction, two clear operational constraints remain open as of this release:

• Offline Edge Cases: In remote listings—such as mountain cabins in the Valais region—guests often lose cellular coverage before reaching the property. If the guest has not opened the Nest app while online during the T-24 hour window, the time-gated access payload cannot decrypt locally without a cached key exchange. We are currently testing a local Bluetooth local-mesh fallback in beta, but it is not live in production.
• Over-Structuring Fatigue: Requiring hosts to fill out individual nodes increases setup time by an average of 14 minutes per listing. Early telemetry shows a 12% drop-off rate during the initial listing creation flow when hosts hit the Appliances node set. We are evaluating whether to make node completion optional at publish, while applying a slight search ranking penalty to listings with incomplete node structures.

What is Live Today

The new House Guide Builder is live across all Nest accounts in Europe as of build 4.12.0. The machine-readable node parser and Mia’s automated operational queries are active for English, French, Spanish, and German stays. Advanced integrations with smart lock hardware remain in open beta for selected host tiers.