Make the handoff from receiving a tenant’s request to assigning it visible to everyone responsible.
Mitra Team · 3 min read
A tenant calls about a dishwasher that won’t drain. Someone writes it on a pad by the phone. Days later, the tenant calls again, and the maintenance coordinator is hearing about it for the first time. Receiving the report was only the first step. It never reached someone responsible for the next one.
Find the gap between intake and assignment
Reports may arrive by phone, email, a portal, or a conversation at the property. If each lands somewhere different, your coordinator has to discover the work before assigning it. Choose one existing place to track routine requests and one person responsible for reviewing incoming reports.
Stage | Question to answer |
|---|---|
Received | What was reported, where, and by whom? |
Assigned | Who owns the next action? |
Scheduled | Has someone agreed to attend? |
Closed | What was completed and communicated? |
The labels can fit your current system. What matters is that “received” doesn’t quietly become “someone is handling it” without a handoff.
Use a consistent intake format
Ask for the address, unit, tenant name, callback number, description in their own words, and when the issue started. Note whether they already reported it so your team can find a related request. Avoid collecting access credentials in general call notes.
A report saying “dishwasher won’t drain in unit 4; tenant available for a callback after three” gives your coordinator more to work with than “appliance problem.” It still needs review before anyone decides the cause, repair, or attendance time.
For phone intake, your team, an answering service, or an AI phone assistant can collect information. Mitra can answer calls and provide summaries and transcripts. A person still needs to move the report into your established workflow and assign it; a call summary does not prove that a work order or dispatch happened.
Make ownership explicit after hours
Define who reviews routine overnight reports and who covers absences. Keep your established urgent and emergency procedures separate from this routine intake process. Choose review timing based on the responsibilities your team already has.
When updating the tenant, state only what is known. “We received your report” differs from “the coordinator has accepted it” and “a contractor has confirmed a visit.” Name who sends the next update so the tenant isn’t waiting for a message nobody owns.
Trace requests through to the next action
Review a sample of recent reports. How long did each wait without an owner? Were repeat calls linked to the existing request? Could your team see the current status? Fix the handoff where information stopped moving, then review another sample.
Common questions
What if a tenant reports the same issue twice?
Check whether it relates to an open request, add any new information, and communicate the current status. Don’t assume a repeated report contains nothing new.
Who should review new reports?
Assign a named person and a backup. A shared inbox alone doesn’t establish responsibility.
Read next: getting useful after-hours messages.