Operations

Marketing a listing ends at the confirmed reservation; operations begin there. This section covers the stay itself — the arrival, the door code, the departure — and everything attached to it before and after: recording the condition of the home, the evidence you keep of it, the reset between guests, incidents, and the note a guest leaves at the end.

One principle runs through these pages: the stay is born at confirmation, not on arrival day. As soon as a reservation is confirmed, the operational record that will follow the guest through to departure already exists, and every move you make on it leaves a reusable trace — an inspection feeds the evidence package, a package pre-fills an incident, a departure creates the reset task.

Nothing here decides for you. Checklists are ticked by hand, certificates are accepted or rejected, incidents are opened deliberately: YStay prepares, cross-references and keeps the record — you make the call.

Guides in this section

• Run a stay: check-in and checkout — the two arrival mechanisms, the checklists you tick yourself — including the steps the field worker confirms themselves —, and what departure really cuts off.
• Inspections: policy, guest link, templates — who records the condition of the home, how the guest gets their link, and how a template frames the record.
• StayProof: build and share the evidence — record findings, generate the package, compare entry with exit, and share the result.
• Incidents and disputes — open an incident by hand or from a StayProof analysis, claim against the deposit, and prepare the statement you will send.
• Housekeeping and turnovers — today's board, the reset tasks born from departure, their reasoned block and the forced close.
• The unit sheet: rooms, key locations, instructions and checklists — what the field team needs to know about a unit, the checklist templates a task picks up, and the sheet proposal to review item by item.
• Room-by-room guidance and reference photos — what the field worker reads from the sheet 24 hours before their task, the comparison slider and the ghost overlay, the photo quality flags, and offline work.
• NFC / QR tags — QR labels stuck in the rooms so that the field worker records their visit and opens the room's checklist: turning the setting on, adding and printing the tags, revoking them, and what YStay records — the time and the room, never the position.
• Terrain: the stay plan and My day — set what every stay triggers per listing, inherited settings, your notifications, and a task's detail on Host Ops.
• Proof of service — the PDF that proves what was done on a finished field task: when it is built, what it contains — roles, never names —, its two fingerprints, who can download it and how long it is kept.
• Add a field agent without an account — add someone without a YStay account, send them their personal link, assign them a task, then follow, resend or cut off their access.
• Your schedule by link — the agent's guide: open the link, read the schedule, accept, start and finish a task, confirm the arrival or departure steps, get the key handover signed, report a blocker, work offline.
• Early check-in and late checkout — offer an early arrival when the unit is ready, or a late departure when nothing follows: the policy to set per account, property or unit, copilot and autopilot, what the guest receives and what their payment changes on the access code and the tasks.
• Field network: partners and missions — your book of field partners and the mission dispatch, through to the proof you approve or reject, and the My jobs page of your contractors.
• Insurance certificates: accept, reject, unblock access — the review queue for the certificates your guests upload, and what your decision governs on the door code.
• Automate your guest messages — four triggers, one daily pass, and what a rule will never do on your behalf.
• Handle reviews and rate your guests — reply to the reviews received from your channels, and keep a private rating on the guest.
• Planning board — the grid of agents and hours: read the day, the workload and the travel, assign a task by drag and drop, understand a refusal, filter and save views (from the Team level, Agent Ops option).
• Control tower — the state of the field in five columns refreshed every 30 seconds — in progress, late, exceptions, agents, arrivals not ready — and its full-screen display for an office screen.