Feature Guide · Stays and Pricing
A plan for everyone.
A price for one.
A monthly plan has one price. A building has two hundred residents and a dozen arrangements nobody wrote down. The software should be able to hold both without a spreadsheet on the side.
What it is
A price that belongs to one stay.
A resident or guest on a plan can be given a custom price, or made complimentary, without creating a new plan for one person. The stay is labeled so anyone looking at it can see whether it is on the plan's price or its own.
When a plan's price changes, people can be moved onto the new price together, and the change can be undone.
The exceptions every building has
Handled where they live: on the person.
A custom price
For one resident or guest
Set it on their stay. Their billing follows it from then on.
Complimentary
One person on a paid plan
Comp a single stay without touching the plan everyone else is on.
Labeled
Plan price or custom
Every stay says which it is, so an exception is visible rather than a surprise.
When the plan changes
A price increase is a decision, not a data-entry project.
Move together
Onto the current price
People on the old price can be moved to the new one in one action.
Undo
If it was the wrong call
The move can be reversed.
Edit the details
Room, name and phone
A stay that was added by hand can be corrected by hand.
From the car's ticket
The valet is often the first to know.
Enroll at the curb
From an open ticket
A valet can enroll a guest in a configured stay from the car's ticket.
See the membership
Room, term and vehicles
What the stay includes is visible to the person standing next to the car.
The practical result
The exceptions live in the system instead of in someone's memory.
A property manager should be able to answer what any resident pays, and why, in one click.
Next: see how residents request their own cars.
