An alert plus a drafted response from listing context. You review and send. No auto-reply, no conversion claims.
For Airbnb and direct-booking hosts
Never miss an enquiry or a dirty room between one or two units.
You do not have a night manager. zwigly catches the enquiry, drafts the reply, and makes sure the cleaner knows before the next guest does.
A single-property or two-property host is usually the operator, the cleaner coordinator, and the guest support line at once. The failure mode is not a missing tool, it is a missed WhatsApp message at the wrong hour. zwigly alerts, drafts, and hands off so nothing sits unanswered mid-turnover.
Where zwigly fits
Stay jobs built for airbnb hosts
Checkout marks the unit dirty and pings your cleaner on WhatsApp directly. No product login for them.
A payment link goes out, the status is watched, and the booking confirms once it clears.
Time-boxed PINs on Seam-supported locks, live for exactly the stay.
Built to work with Guesty or Lodgify for booking data, WhatsApp for guest and cleaner messages, and Seam-supported locks where you already have smart locks installed.
See the full stack and catalog →Questions airbnb hosts usually ask
I only have one or two units. Is this overkill?
The jobs are the same at one unit as at fifty: notify the cleaner, issue the PIN, answer the enquiry. zwigly starts with whichever one stalls you most.
Will guests get an automatic reply?
No. Inquiry assist drafts a reply and alerts you. A human sends it. We do not claim automated enquiry-to-booking conversion.
Other ways operators use zwigly
Bring one unfinished stay handoff.
Tell us the stall. We will show how it runs as an agent and a workflow you can review.