Reference · built on requestOperator by FibricHospitality & guests

Lost and Found

Matches items housekeeping logs as found to the guest who left the room, pairs them with inquiries, and proposes the return and label.

Request accessPricing ↗

About

A found item is logged with a room number and a date. The guest who asks about it writes to the front desk or the support inbox a day later with a description and a name. The two records sit in different systems and the match is made from memory. Lost and Found reads the found-item log your housekeeping team keeps, the reservation history in your property management system, and the inquiries that arrive as support conversations or tickets.

When a description, a room, and a departure date line up, it proposes the match with the evidence beside it. On approval it proposes a reply to the guest and a shipping label to the address they confirm. Nothing ships until a person approves it.

This is a reference listing. It documents what Fibric would read from Lost and Found and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Found-item entries with room number, date, description, and storage location, from the Google Sheets range or Airtable table housekeeping records them in
  • Housekeeping tasks that record a found item, through tasks/getAll in Mews, filtered by department
  • Departed reservations by room and check-out date, through getReservations in Cloudbeds or the rsv module in OPERA Cloud
  • Guest inquiries about lost property arriving as Kustomer conversations or Zendesk tickets, with the requester's name and message
  • Guest contact details and mailing address on the profile, where the property management system holds them
  • Label and tracking events in ShipStation for returns already sent, so a second inquiry gets the tracking number

Proposed actions

  • Target capability: propose a match between a found item and a departed guest, with the room, dates, and description that support it, for your approval
  • Target capability: propose a reply on the guest's conversation or ticket asking them to confirm the return address
  • Target capability: propose a shipping label in ShipStation to the confirmed address once the guest has agreed to the return
  • Target capability: propose closing the found-item entry with the tracking number and the date it left the property
  • Target capability: propose a disposal reminder for items unclaimed past the holding period you set

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Return a charger left in a room

    Housekeeping logs a charger from a fourth-floor room in the Airtable base. The next day a Zendesk ticket asks about a charger after a Saturday checkout. The operator matches the two through the Cloudbeds departure list and proposes the reply and label.

    With Airtable, Zendesk, Cloudbeds, ShipStation

  • Answer a second inquiry with tracking

    A guest writes to Kustomer again about an item already sent. The operator finds the ShipStation label tied to the earlier match and proposes a reply with the tracking number.

    With Kustomer, ShipStation

  • Work from housekeeping tasks in Mews

    Where attendants log found items as Mews tasks by department, the operator reads those tasks and the departed reservations from the same system, and proposes the match without a separate sheet.

    With Mews

  • Clear the shelf on schedule

    Items past the holding period you set are listed from the Google Sheets log with their log date and any inquiry they were matched to, and a disposal or donation reminder is proposed for the housekeeping manager.

    With Google Sheets

Requirements

  • A property management system connector that exposes reservation history by room and departure date, such as Mews, Cloudbeds, or Oracle OPERA Cloud
  • A found-item log the operator can read: a Google Sheets range, an Airtable table, or housekeeping tasks in the property management system
  • A support connector with read access to inquiries and write access for replies, such as Kustomer or Zendesk
  • A ShipStation account with a ship-from address for the property and carrier services selected
Authentication
Lost and Found holds no credentials of its own. It reads the found-item log, reservations, and inquiries through the connectors you have connected, and proposes replies and labels through the same support and shipping connectors.

Limits

  • It matches on room, dates, and description. A guest who cannot name the room or the stay dates gets a shortlist, not a match.
  • Found-item logs kept on paper are outside its reach until someone enters them in the sheet or task system.
  • A label is proposed, never purchased on its own. Carrier cost is shown in the proposal and a person accepts it.
  • It does not decide who owns an item. Two guests claiming the same item are both shown to the front desk.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Lost and Found ↗

Questions and answers

What does a person approve before an item is returned?
Each step on its own: the match between an item and a guest, the reply asking for an address, and the label. Each proposal shows the log entry, the reservation, and the inquiry side by side. You can approve, edit the address, or dismiss.
What record is left after a return?
A receipt per item: the log entry, the reservation it was matched to, the conversation or ticket, who approved each step, the label and tracking number, and the date it left. The found-item entry is proposed closed with the same tracking number.
Does it ever ship something on its own?
No. It proposes a label only after a person approves the match and the guest confirms the address. Purchasing the label is a separate approval. It never replies to a guest, buys postage, or discards an item without someone acting.
Ask about Lost and Found

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy