Use cases

The hour in between

Your PMS already knows who is staying. Your locks already know the door. zwigly is the hour in between: the PIN, the folio, the dirty room, the stop-sell, without a night manager on WhatsApp.

Integrations for these stays

Guesty, Lodgify, WhatsApp, Seam, and the rest of the hour

Named tools operators already run. Guesty early access first. Live vs Buildable honesty. No invented connector counts.

See the full stay stack and 700+ catalog →

Your PMSWho is staying

Guesty, Lodgify, eZee Absolute, or Kamra already hold the booking.

zwiglyThe hour in between

PIN, folio, dirty room, stop-sell. Keep your SOP. Finish the steps.

Locks + VoiceDoor, crew, calls

Seam grants, WhatsApp, Slack, and Voice AI handoffs when the SOP needs them.

Three jobs that finish the stay

Voice AI · Buildable

Calls that finish the hour

zwigly started inside hotel Voice AI: guest calls, follow-ups, room-ready handoffs. On the stay stack it is Buildable: welcome and checkout calls, stall pages, and morning briefs that can land on Voice as well as Slack.

  • Welcome and checkout callsBuildable

    Guesty booking events can trigger Voice AI welcome or checkout calls so the front desk is not the only channel.

  • Stall pages on VoiceBuildable

    When a handoff stalls, Voice and Slack hear it before the guest does. Same unfinished stay, another channel.

  • Morning brief by VoiceBuildable

    Same 7:30 shape as the ops brief: arrivals, departures, grants expiring. Optional Voice delivery beside Slack.

Voice AI is not on the eight eZee Absolute / Kamra / Seam cards below. Those stay PMS + lock stories. Bring a Voice SOP onbook a demoorContact us.

P0 · start here

Live and near-live handoffs

eZee AbsoluteSeam
Live

PIN before check-in

The room is ready when the flight is late. The lock is dumb again at 11:00.

A 20-80 room eZee Absolute hotel. Late-night arrivals. Thin night desk.

  1. 1eZee booking created then get booking.
  2. 2Seam create access grant (check-in to check-out, reservation as the key).
  3. 3Email the PIN.
The story

A 40-room eZee hotel can issue a time-boxed door PIN the moment the booking lands, and kill that grant at checkout. Front desk never texts a code from a notebook.

eZee departure then Seam revoke grant then lock door then Telegram host.

KamraSeam
Buildable

Waitlist to pay to unlock

The next guest is not a spreadsheet. They are a payment, then a code.

A Kamra villa.

PIN half is Live; waitlist head not seeded

  1. 1Kamra waitlist ready then promote waitlist.
  2. 2Kamra send payment link.
  3. 3After paid / confirmed: Seam create access grant then email PIN.
The story

A Kamra villa can promote the next waitlisted guest when a Saturday frees up, send the payment link, and only then issue the Seam PIN. No "is it paid?" in the group chat.

eZee AbsoluteSeam
Buildable

Noise on the folio

House rules that actually invoice.

A 40-room eZee stay.

  1. 1Seam noise detected.
  2. 2eZee find booking (today's in-house / room).
  3. 3eZee add extra charge + Telegram host.
The story

A 40-room eZee stay can post a noise extra to the folio the moment the sensor trips, and page ops with unit + reservation, before anyone wakes to argue about it.

eZee AbsoluteKamraSeam
Buildable

One morning brief, two PMS

You did not standardize the PMS. You standardized the morning.

An owner with eZee and Kamra under one roof.

  1. 1Schedule 07:30.
  2. 2Kamra owner briefing + eZee today arrivals/departures.
  3. 3Seam list access grants (expiring today) then one ops message.
The story

An owner with eZee and Kamra under one roof can get a single 7:30 a.m. brief: Kamra owner briefing + eZee today's arrivals/departures + Seam grants that expire today. They do not log into three products before chai.

P1 · buildable

Same hour, more plays

eZee AbsoluteSeam
Buildable

Offline lock, closed inventory

Inventory follows the hardware. Not the other way around.

A 40-room eZee hotel.

  1. 1Seam device offline or low battery.
  2. 2eZee update stop-sell (room type, short window).
  3. 3Slack / Telegram: unit, device, OTB blocked until lock is up.
The story

A 40-room eZee hotel can stop-sell the room type the moment Seam reports offline or low battery, and page ops. You do not sell a door you cannot open.

eZee AbsoluteSeam
Live

Cleaner shift, not a spare key

Turnover access is a shift. It is not a spare key in the group.

A 40-room eZee hotel.

  1. 1eZee new departure then get booking then update room status (Dirty) then Telegram cleaner.
  2. 2Seam revoke guest grant + lock.
  3. 3Morning: Seam create access code (cleaner, 4 hours) then WhatsApp; evening: delete access code.
The story

A 40-room eZee hotel can mark the room dirty on departure, revoke the guest grant, and issue a separate Seam code that exists only for the morning cleaner window, then deletes.

eZee AbsoluteSeam
Buildable

Late checkout, same PIN

An extra three hours is a calendar change, not a new keypad.

A 40-room eZee hotel.

  1. 1eZee booking changed (filter: checkout moved).
  2. 2Get booking.
  3. 3Seam update access grant then Telegram ops "PIN now until 14:00."
The story

A 40-room eZee hotel can move stay dates in the PMS and only extend the same Seam grant's end time. Guest never learns a second number. Lock still dies at the new time.

KamraSeam
Buildable

Ticket opens the door

The ticket is the key. The key expires.

A Kamra property.

  1. 1Kamra new ticket then AI classify (access vs info).
  2. 2Seam unlock / short access code + Slack tech.
  3. 3Later: Seam lock + optional Kamra post stay charge.
The story

A Kamra property can treat "room access needed" tickets as a short Seam unlock window for the tech, Slack the unit, then lock again when the ticket is done (or after 90 minutes). Optional folio post-stay charge if billable.

Partner names stay as text lockups on use-case cards. Homepage and Integrations show authentic connector marks from /brand/connectors.

Bring one unfinished stay

Guesty operators: book a demo. eZee Absolute or Kamra: talk to us.

Book a demoTalk to us
Book a demoJoin waitlist