Listing lifecycle
- Draft listing with complete essentials.
- Submit for approval.
- Activate and monitor enquiries.
- Refresh content regularly (media + description quality).
Quality controls before publish
- Minimum photo count and clear hero image.
- Description depth: amenities, fees, restrictions, nearby context.
- Accurate pricing and period fields.
- Precise location and availability signals.
Listing quality workflow in the editor
- Use `/host/properties/[id]/edit` to improve weak listings before submit.
- The editor now surfaces step-specific quality nudges where the fix belongs:
- `Photos` for cover image and minimum images
- `Details` for title and description quality
- `Basics` for price and location gaps
- On the submit step, look for:
- `Listing quality`
- `Best next fix`
- jump-back actions such as `Go to Basics`, `Go to Details`, or `Go to Photos`
These are guidance cues, not hard publish blocks.
Demand capture workflow
- Use market hubs and discovery rails to identify demand locations.
- Keep one featured candidate listing per key location cluster.
- Track message response speed and viewing follow-through.
Property requests workflow
- Use the workspace sidebar `Property Requests` entry, or open `/requests`, to browse eligible seeker demand.
- Filter by intent, market, bedrooms, move timeline, and budget before responding.
- Open `/requests/[id]` to inspect the brief and send up to 3 matching listings you own or manage.
- Use this workflow for platform-mediated matching only; contact details stay private in this phase.
Property request alerts
- New published requests can trigger email alerts to responder-side users with saved request-alert criteria in the same market.
- Use `/profile` to manage `Email me when a new property request is published in my market`.
- The alert is criteria-based and opt-in; it is not sent for every request on the platform.
Host featured strip workflow
- Open `/host?view=all` to review the Featured strip above the media mosaic.
- The strip prioritizes active featured listings and caps to six cards for quick triage.
- Use the strip for top-of-day checks, then continue in the full mosaic for bulk actions.
- Use horizontal swipe/trackpad scroll in the strip to peek adjacent spotlight cards before deep review.
Canonical listing management routes
- Use `/host/listings` as the primary management surface for all inventory.
- Use `/host/properties/[id]/availability` for availability controls.
- Use `/host/shortlets/[id]/settings` for shortlet-specific setup.
- In feed cards, use the primary `Manage` button for editing and the `...` menu for secondary actions.
Transfer listing ownership
- For a listing you currently own, open its `...` menu and choose `Transfer ownership`.
- Review the transfer panel in the listing editor before sending the request.
- The recipient must accept before ownership changes.
- You will not see the transfer action on a listing you only manage through delegated access.
Demo vs real inventory
- Demo listings are for sandbox/training only.
- Do not use demos to represent live availability.
- Production conversion should come from approved, active, real listings.
Demo listing workflow
- In `/host/properties/[id]/edit`, go to `Basics` and use `Mark as demo listing` when a listing is training or showcase inventory rather than real supply.
- Saving that toggle applies the same persistent demo flag that admins can later view or change from `/admin/listings`.
Expected outcome:
- Demo listings follow platform demo visibility policy instead of normal live-inventory assumptions.
- A `Demo` badge can appear on cards and detail pages when admins keep demo badge presentation enabled.
- A `DEMO` watermark can appear on images when admins keep demo watermark presentation enabled.
- Demo listings are excluded from featured placement and other customer-facing promotional surfaces.
If you need demo visibility or presentation to change, that is an admin settings decision, not a host-side editor control.