What a custom agent looks like inside an independent hotel, inn or short-term rental operation — the ten roles in your language, and what each plugs into in a property running Cloudbeds, Mews or a channel manager.
last reviewed
Lodging sells a perishable room-night, which makes two things decisive: what you charge for it and whether the guest books direct or through a channel taking fifteen percent. Both are decisions made continuously and both are made badly when the person responsible is also handling front desk, housekeeping coordination and every guest message that arrives at eleven at night.
The honest version of "does it integrate with my software." These are the systems this industry actually runs on, and what each one means for a build.
The systems of record for reservations, rates, folios and housekeeping, all with modern, accessible interfaces.
Keeping availability and rates in step across Booking.com, Expedia, Airbnb and the direct site, where a mismatch means either an overbooking or an empty room.
Rate decisions against demand, competitor pricing and pace, which is where independents most consistently leave money behind.
Pre-arrival, in-stay and post-stay communication, arriving at every hour through several channels.
Room status, turnover sequencing and work orders, where coordination failures directly become guest complaints.
Google, TripAdvisor and OTA reviews, where response rate and speed affect ranking and conversion.
Deposits, incidentals and settlement across direct and channel bookings with different payment models.
Each of these is a real build, not a feature of a product you already pay for. Follow one through to see how it works in general.
Nothing you are owed gets dropped.
Whatever arrives, in whatever format, becomes a clean record.
Writes the recurring document from your own past work.
Knows what expires, renews or comes due — and says so first.
Answers from your own records, not from the internet.
The conversation becomes the record, without anyone typing it up.
Assembles the recurring report from systems that do not talk.
Matches two sets of records and queues only the exceptions.
Two systems that do not talk, now talking.
Applies your rules, escalates only what needs judgment.
If that is a job in your business, the next step is half an hour on a call. Bring whatever you know about the volume — how many a month, who owns it now, which systems it touches. That is enough to scope it properly and quote it flat before anything starts.
Everything in this library is built to order rather than bought off a shelf — and whatever I build, I host and maintain. The rest of the library is here.