Inquiry triage
Review website requests, contact guests, and track human follow-up status.
ADMIN
Use this workspace to move live inquiries and reservation checks first, then prepare availability and property publishing surfaces without pretending pending workflows are complete.
Review website requests, contact guests, and track human follow-up status.
Scan canonical reservation records after a human converts inquiry context into booking operations.
Scan seller opt-ins from the public owners form before deciding whether to follow up.
Review canonical availability blocks, source context, and linked reservations without changing availability data.
Property content, media, and Bulgarian review are being prepared before any publishing workflow is treated as live.
Open Payload for CMS access while product-specific editing workflows continue to mature.
Review guest requests, check contact details, and update human follow-up status.
Review owner opt-ins, apartment context, contact details, and acquisition fit.
Review canonical reservation records after a human turns inquiry context into booking operations.
Review blocked dates, source context, and reservation links before promising availability.
Create launch property content records with canonical slugs, capacity, location, and bilingual draft fields.
READINESS
These areas are intentionally informational until their editing and approval workflows are approved.
PROPERTY CONTENT
This checklist shows what operators can trust today and what still needs source material or approval before it becomes a live workflow.
Website copy, property names, slugs, capacity, and location data are available.
Create matching Payload records before wiring any website publishing flow.Operational notes are useful, but there is no approved admin note workflow yet.
Capture source notes outside the app and avoid treating them as published state.Real property photography is not approved for wiring into listing/detail surfaces.
Wait for approved assets instead of using placeholder, stock, or AI media.Bulgarian launch copy is AI-assisted and still needs human/native review.
Preserve canonical English meaning and do not mark drafts as approved.Payload now has the first property records surface aligned to the launch website fields.
Operators can scan canonical blocked-date records while source calendars and reservation context stay human-reviewed.
Collect owner-facing context separately until an approved owner-note workflow exists.
Approved real property photography is required before website media wiring can move forward.
Bulgarian copy and AI-assisted drafts stay behind human approval before public publishing.