Eleven conversations reached a person at a 60-unit property last week. Seven were answered within the hour and three the next morning. The eleventh was sent at 4:40 p.m. on Friday and opened on Monday at 9:15, which is 64 hours and 35 minutes later. The renter had asked for a Saturday showing. Those eleven are invented for this post. The shape is common all the same: most hand-offs are fine, and the one that is not costs a lease.
Leasing escalation workflows exist for that eleventh conversation. Sending every question to a person would put the team back under the repetitive work. The useful version lets automation keep the routine and passes the rest to someone who can decide, with enough context to act and a deadline for doing it.
What leasing escalation workflows should do
An escalation is not an alert that says "please call this lead." It is a hand-off with three parts: a condition that triggers it, a named owner, and a time by which the renter hears back.
Take away any one and it fails in a familiar way. With no trigger, every odd question interrupts someone. With no owner, the message lands in a shared inbox where each person assumes another has it. With no clock, it waits behind whatever is louder.
It takes 140 messages on average to rent out a property.1 Most are the same dozen questions. A workflow earns its keep on the few that are not, and it should record why each one was handed off and what the renter already said, so nobody asks for a move-in date twice.
Start with boundaries, not automation
Begin with one question: what may the assistant answer with confidence, and where must it stop?
For most portfolios the first list is long. Availability, published rent, pet policy, deposits, parking, showing times and application steps can all be answered at once, and a showing can be booked in an open slot. The line falls where a reply would need interpretation, an exception or authority: a concession, an unusual lease term, a dispute about a screening result, a complaint, an accommodation request, a household that does not fit the standard path.
Fair housing belongs on that line too. The assistant uses the same approved wording with everyone and routes anything that calls for a trained person. If the line itself is not yet on paper, write the guardrails first. A workflow carries a policy; it does not supply one.
Define the trigger and the owner
"Send to the leasing team" is not an owner. Match the owner to the decision, not only to the property:
- A price or term exception goes to the property manager who can say yes or no.
- A showing that will not fit the calendar goes to whoever controls the calendar that day.
- A maintenance request from a current resident leaves the leasing funnel altogether.
- A corporate or multi-unit inquiry goes to the regional person who handles them.
Write a backup for each. Owners take vacations, and a Friday at 4:40 p.m. is when the first name on the list has already left.
Build urgency around prospect intent
A question about utilities and a request to see a home tomorrow do not deserve the same clock. Three lanes are enough. The times below are a starting point to adapt:
- Now: 15 minutes in staffed hours, first task at opening otherwise. A same-day or next-day showing that does not fit the calendar. An applicant stuck at a step with a deadline.
- Today: 4 business hours. An exception to rent, term or pet policy from a renter who has answered the qualifying questions. An application problem with no deadline.
- This week: 2 business days. A question that needs an approved answer written once, so it stops arriving.
Sort by what the renter is trying to do, not by how many messages they sent. Signs of intent are a move-in date inside 30 days, a named unit, completed qualifying questions and a preferred time that was unavailable.
Keep the first lane narrow. If half of all hand-offs are marked urgent, people stop reading the word.
Make the handoff useful to the human
A hand-off should arrive as a brief, not a phone number. Here is one filled in, as an illustration:
- Who: Maria, by text, last message Friday 4:40 p.m.
- Wants: the two-bedroom at 412 Maple, move-in March 1, a showing on Saturday.
- Already told us: two adults, one cat, income above the published criterion by her own account.
- Why it is with you: Saturday's slots are full and she cannot come on a weekday.
- Lane and clock: Now. Reply by 4:55 p.m. today, or first thing Saturday.
- What she has heard: that a person will confirm a Saturday time, and when.
- Assistant status: paused on scheduling, still answering questions about the home.
The last two lines matter as much as the rest. The renter should never wonder whether anyone received the message, and the owner should know whether the assistant is still talking. With the brief in hand, Dana can open with something like this:
"Hi Maria, this is Dana at 412 Maple. I saw you can only make Saturday. I can open Saturday at 9:30, before our first showing. Would that work?"
That is a reply nobody had to research.
Connect escalation to the systems your team already uses
A hand-off that lands in a dashboard nobody opens is not a hand-off. Send it where the owner already works, whether that is text, email, the team chat or the PMS task list, and keep the conversation attached to the prospect and the property.
Three connections do most of the work. The live calendar, so a showing hand-off shows what is open. Current availability and rent, so the assistant's own answers stay right. Application status, so "why can't I continue?" reaches a person with the answer in front of them.
Integration does not move authority. Your screening criteria and leasing policy decide; the systems carry the information.
Measure whether the workflow is helping leases happen
Count the hand-offs, then read what the count means. A low number can mean the routine work is handled, or that sensitive conversations are being answered when they should have been passed on. Four patterns to look for:
- Many hand-offs share one reason. A policy needs a written answer. Thirty questions about a second pet is a rule waiting to be set.
- Hand-offs are answered late on the same days. That is a coverage gap. Check Fridays after 4:00 and Saturdays first.
- Renters go quiet after a hand-off. The holding message did not say who would reply or when.
- Showing hand-offs pile up. The calendar is short of slots, and no wording will fix that.
Then follow the escalated prospects forward to showings kept, applications started and applications finished. Once a month, read ten handed-off conversations with whoever owns compliance and ask whether each one stopped in the right place.
Keep people accountable, not overwhelmed
Nobody should answer a parking question at 10 p.m. Somebody does have to own the Saturday request. Coverage should fit the staff you have: a central team may take after-hours hand-offs for a portfolio, and a smaller operator may promise the next business morning and say so to the renter at once.
Whatever the model, write it where the owner can see it and check it every Friday at 4:00 p.m. Open the queue, look at what is unanswered, and make sure each item has a name beside it for Saturday.
When something falls outside your rules, Tallo asks you rather than guessing, then remembers your answer so the same question does not come back. It never approves applicants or signs leases, and the lines it holds are public.
Maria does not know which lane she was in. She knows whether someone wrote back before Saturday.
1 — Source: Tallo portfolio data, average messages per leased unit; the same figure appears on the About page. The eleven hand-offs, the three lanes and their clocks, the hand-off brief and the sample reply are illustrations to adapt, not standards or legal advice. The 64 hours 35 minutes is arithmetic from Friday 4:40 p.m. to Monday 9:15 a.m.