This describes work that is in design. Everything below is what we are building, not something you can switch on today.
An applicant replies to a booking confirmation with a question about an assistance animal.
Or they ask why their application was turned down. Or they mention, politely, that their lawyer suggested they ask about something. It is a quarter past eleven at night and the message has arrived in a thread that, until this moment, was about which Thursday suited them for a viewing.
Every one of those messages has a correct first response, and it is the same one in each case: a person reads it, and a person answers it.
The cost of software being helpful in that moment is not an awkward sentence. It is a firm having answered a question it should never have answered in writing, at eleven at night, with nobody at the firm aware it happened until the reply is already sitting in someone else's inbox. Whatever was said went out under the firm's name. That is the whole risk, and it is not a risk about tone.
Most systems treat stopping as the failure
Here is the pattern this industry keeps repeating.
Handover gets built as the error case — the branch you reach when the software is stuck. Being stuck sounds like failure, so nobody wants much of it, so the threshold gets tuned down. And a threshold tuned down does not produce a smarter system. It produces one that stays in conversations it should have walked out of, because leaving was treated as losing.
We are designing it the other way round. Escalation will be the default, and it will be free. No counter treats it as a miss, nothing gets tuned to reduce it, and no capability is ever specified as handle it, escalate if stuck. Each one is specified as handle this exact thing; escalate everything else.
That inversion is the whole design. What the software will do is a short, explicit, written-down list. Everything not on the list is somebody's job, and the software's correct behaviour is to go and find them.
A short list of things it will do is a stronger promise than a long list of things it will attempt.
A floor you can build on, and cannot lower
Some of those stopping points will not be yours to configure.
There is a set of triggers that live in the product, apply in every account, and are not editable by anyone — not by a firm, not by us on a firm's request. A message that raises an accommodation, an assistance animal or accessibility. A question about the decision itself: approval, refusal, the criteria, an appeal, why. Any mention of a lawyer, a complaint or a tenancy board. Anyone asking to speak to a human. Any request to change a rule, a term, a fee or a price.
For that set, the software will not send a careful reply. It will not send a holding line or a polite deflection either, because a deflection is a response, and the question of what your firm says to an applicant about their accommodation request at eleven at night is not a question we are willing to have software answer on your behalf in any form. The message goes to a person, unanswered, and the person decides everything from there.
A firm will be able to add to that floor. A firm will not be able to lower it.
We would rather say that plainly now than be asked for it later, because a product that lets its safety rails be switched off for a big enough account does not really have them. This is a position, not a limitation, and it is one of the few things a company can commit to honestly before the thing is built: it is true the moment we write it down.
Be clear about what that floor is. It is a routing decision: it puts a message in front of a person instead of answering it. It is not a safeguard we are selling you, and it makes no promise about your obligations as a landlord — those are yours, exactly as they were before any software was involved. What it does is make sure the messages that need your judgement are the ones that get it.
Your triggers, on top of ours
Above the floor, the interesting configuration is yours, and it is the part that will differ most between two firms of the same size.
Anything touching lease terms goes to Marie. Anything about the heritage building goes to the owner, who has always handled that one personally and intends to keep doing so. A message whose tone reads as unhappy goes to whoever is best at those. Second reschedule on the same booking — you want to see it. A question the pack you wrote has no answer for, so there is nothing grounded to say and the right move is to hand it over rather than improvise.
Each of those gets a destination you choose. The point is not that the list is long. The point is that it is written, and therefore inspectable, changeable in ten minutes, and the same on a Sunday as on a Wednesday.
There will be a structural stop underneath all of it too: a hard cap on how many messages the software may send in a row before a person has touched the thread. Not a judgement call, not a confidence threshold — a counter in the send path. Software that has been talking to someone unsupervised for a long stretch is a situation, whatever the content of the messages.
What arrives when it stops
Handover is only worth having if what lands on your desk is usable, so the design target is that stopping produces work you can act on rather than a notification you now have to go and research.
The whole thread, attached. What was asked, what the software understood the question to be, and why it stopped — which trigger fired. Where a draft exists and the trigger allows one, the draft, clearly marked as unsent. And a destination that was decided in advance, so the message is already with the right person rather than in a queue somebody has to sort.
That is the difference between finding out on Tuesday and finding out in a complaint.
The honest trade-off: more will reach you, not less
Escalation-first means more messages come to a person than a maximally automated system would allow. In the first months of an account, noticeably more.
That is the intended behaviour and we are not going to dress it up as a temporary condition on the way to something quieter. A system that hands you fifteen messages a week it was not sure about is a system you can form a view about. One that hands you two is either much better than it has any right to be, or it is answering thirteen things nobody checked.
The honest framing is that your firm is choosing where its attention goes, in advance, in writing — rather than discovering after the fact where it went.
Releaser is available to property management firms in the United States and Canada today: one shareable link per property, your screening completed before anyone reaches your calendar, and self-serve booking for the people who meet the criteria you set.
The rules you write are described in your leasing rules exist, and the out-of-hours work these stopping points sit inside is in the inquiry that landed at 10:41 on a Sunday. Escalation as it is described here is in design. This is what we are building it to be.