When leasing moves off site, who owns the resident's problem?

Picture a resident who calls about a charge on her ledger that she says she already paid. In a centralized model, that call may reach a shared team that serves many properties, while the onsite staff who know her are at the property.

MRI Software's October 14 guide to multifamily centralization describes this arrangement as one where tasks that "do not require a physical presence on site" move to specialized teams serving many properties at once, while onsite staff focus on tours, maintenance and resident relationships. The guide is a useful test case, because it is specific about which work moves and less specific about what happens when a resident's issue needs both teams.

What the guidance assigns

MRI's guide is fairly specific about which work should leave the property. It recommends centralizing collections and delinquency follow up because "one policy applied consistently is fairer to residents and easier to manage," and centralizing application processing and screening so the same criteria are applied every time. Tours stay mostly on site. Renewals and maintenance are listed as hybrid functions. For renewals, the guide says offers "can be centralized" while onsite relationships influence the decision to stay. For maintenance, dispatch and scheduling "can be centralized" while the work happens on site.

For the boundary between teams, the guide offers several recommendations. Operators should "define the handoff," which it describes as agreeing on when a prospect moves from the central team to onsite staff, "typically at the tour or at move-in." Central and onsite teams should work from the same record so residents "never have to repeat themselves" when a central agent hands off to the property. AI tools and central teams should route emergencies and sensitive issues to staff "without delay." Operators should map the resident journey and keep moments such as move in, renewals and service issues on site. Onsite job descriptions should be updated so those staff "own resident relationships, tours, and property condition." For a centralized business office, the guide says to write down how invoices are approved, how payments are posted and "how delinquency is escalated" before moving the work, and to set service level agreements with onsite teams covering "turnaround times for invoice approvals, resident ledger questions, and month-end reporting."

These are MRI's recommendations, and several of them are tied to MRI products, including its Engage CRM and its Engage Interact voice agent, which the company says escalates calls to staff when needed. The performance figures MRI reports in the guide concern application completion speed and accounting cost savings. None of them measure how resident disputes are resolved.

What the guide leaves to the operator

The one handoff point the guide specifies is for prospects, who move from the central team to onsite staff "typically at the tour or at move-in." A disputed balance doesn't follow that sequence. The guide assigns collections to the central team and resident relationships to onsite staff, and a resident disputing a charge involves both.

The guide's turnaround standard for "resident ledger questions" and its advice to document delinquency escalation address part of this. Neither says which team owns the resident while a question is pending, who has authority to reverse a fee, or who tells the resident the outcome. The guide leaves those decisions to each operator.

The shared record has a similar limit. A single system can show both teams the same ledger and the same notes. Whether anyone is assigned to close the case is a staffing and policy decision that the guide does not spell out.

Application exceptions raise a version of the same problem. MRI's argument for centralized screening rests on applying the same criteria every time, which it says supports fair housing compliance and fraud detection. An exception, such as an applicant whose documents don't fit the standard workflow, is a case the standard process wasn't built for. An operator that centralizes screening needs a written answer to who can approve a departure from the criteria, and who documents why.

Questions to settle before the next transfer

Operators already running a central office, or planning one, can test their own process against a single disputed charge. The useful questions are specific:

• Which role owns the resident's issue from the first contact until the resident is told the outcome, regardless of who does the research?
• Who has authority to waive or reverse a charge, and up to what amount, at the central office and at the property?
• What must the property send back, and in what form, for the central team to act without a second request?
• What happens when the turnaround deadline passes and the property hasn't answered?
• Does the case count as closed when the ledger is corrected, or when the resident has been told?
• Can the operator report, by property, how many ledger disputes were reopened or produced a repeat contact?

MRI's guide recommends publishing response time targets, reporting on them by property, and tracking satisfaction scores and online reviews. Response time measures how fast someone replied. It does not show whether the reply settled the issue, which is why the repeat contact question belongs on the list.

A practical first step is to pull ten recent ledger disputes and trace each one from first contact to closure, noting every point where the case changed hands and whether a single named role stayed responsible throughout. If the answer differs from case to case, the escalation procedure needs an owner before it needs a faster deadline.