It works inside the PMS you already run: reading the card, the deposit and the rate plan on each arriving and in-house reservation, fixing what is safe, and leaving a briefing by morning. Your team stops reconciling folios at 3am.
One pass across every property you run, on the system you already pay for.
Kept reads the card, the deposit and the rate plan on each reservation and compares them. A card that expires before arrival, a deposit that does not match the plan, a missing guarantee: it finds each one and says which reservation it is on.
Kept never charges a card on its own authority. Anything that moves money stops and asks, in one line you can answer from your phone. You approve, it acts; you deny, it finds another way.
Add as many properties as you run. Kept works out which ones a question is about, signs in to just those, and works them at the same time. Each keeps its own system, its own login and its own local clock.
The same agent that works the night audit answers questions during the day. Ask it to check one reservation, pull a report, or explain what it changed last night. It answers from the live system, not from a stale copy.
Save an instruction in plain words and Kept runs it on the schedule you choose, across the properties you choose. Each run opens as a conversation you can read, so you can see exactly what it did.
Every call Kept made is kept in order, with what it asked for and what came back. When an auditor asks why a folio changed at 03:14, the answer is one click from the reply that changed it.
Setup takes one sitting. After that Kept runs on its own.
Add a property and give Kept the sign-in your night auditor uses, or the API credentials if your system has them. No migration, no data import, no change to how your team works.
Four settings, from looking without touching to working unattended. Most properties start on the one where Kept asks before every change, then loosen it once they have watched a few nights.
It signs in at the hour that is night for that property, reads every arriving and in-house reservation, and checks the money on each one against the rate plan and the card on file.
Clear cases it corrects. Anything ambiguous, and anything that moves money, waits for a person with the context needed to decide in seconds.
One page by morning: what was checked, what was fixed, what needs your eyes. Approve or deny the queue in a couple of minutes and the shift starts clean.
Three minutes: connect a property, watch the audit run, read the briefing.
Kept is built so a finance controller can answer for anything it did.
Four modes per conversation. Read only looks and never changes anything. Ask stops before every change. Auto works alone and asks only before a risky one. Read and write works without prompting. A separate check classifies each action before it runs, so the mode is enforced rather than suggested.
Every action Kept proposes passes a rules engine and an independent verification pass, and carries a confidence score. Low confidence goes to a person. The score, the reason and the before-and-after are all stored against the action.
Sign-ins are held encrypted and are never shown back, not in the interface and not to Kept's own staff. Each property's data is walled off by organisation at the database, and no password or key is ever carried in a live update.
Every call, its timing, what it asked for and what came back. A run that changed a folio can be opened months later from the line that reported it.
Certifications and formal reports are in progress. Ask us for the current security summary before you connect a property.
Kept reaches a property through its API where one exists, and drives the screens where it does not. Either way there is nothing to install.
…and 23 more. Tell us what you run and we will confirm before you commit to anything.
One plan. Priced per property, per month. Every feature included at every size.
No setup fee. No contract. Stop whenever it stops being useful.
Quotes go in once the first properties agree to be named.
No. Kept works in the system you already run. It signs in the way your night auditor does, or through the system's API where one exists. There is nothing to install on your machines and nothing to migrate.
Not unless you tell it to. Every action that changes a record is classified before it runs and checked against the mode you set. On the setting most properties start with, anything that moves money stops and waits for a person.
It queues the case for a human with the reservation, what it found, what it would do and how confident it is. That is the design: a wrong write on a folio costs more than a slow one.
Each property carries its own timezone, so a group spread across countries gets its audit at the right local hour rather than all at once.
Your organisation's rows are separated at the database, so one customer's query cannot reach another's data. Sign-ins are stored encrypted and are never displayed back.
Every action is recorded with its before-and-after state, so a mistake is visible and reversible in the PMS. Start on read only for a week and compare what Kept found against what your team found; most properties do.
One sitting. Add the property, add the sign-in, pick the timezone, choose a mode. Kept runs that night.
It takes the reconciliation pass, which is the part that is repetitive and happens at 3am. The judgement calls still come to your team, with the work already done.
Bring one property and a night's arrivals. We will connect it and show you what Kept finds.