Tenant Maintenance Intake: Make the Handoff Actionable

Tenant maintenance intake works when the next person can understand where the issue is, what the tenant reported, and what still needs to happen. It fails when a confident summary invents a diagnosis, drops the unit number, or suggests a contractor is already on the way.

An answering assistant can help collect a coherent request, but request capture and maintenance dispatch are different services. Agree which one you are implementing. Without a verified work-order connection and an accepted dispatch process, the caller should hear that their report is being passed to the responsible team.

Collect the location before the story expands

Begin with the building and unit, then establish whether the caller is a resident, an owner, or someone reporting a shared-area issue. This affects who can provide access and who should receive follow-up. A neighbour reporting a corridor leak should not be treated as the account holder for a nearby apartment.

Ask the tenant to describe what they observe. Preserve their language: “water beneath the sink” is better than “failed waste pipe” when no technician has examined it. Record when the issue started and whether it is changing, without conducting an improvised technical diagnosis.

The property-management guide covers the wider use case. For this specific workflow, the useful output is a report another person can act on, not a score for how convincingly the assistant discussed plumbing.

Separate access preference from permission

A caller saying “I am normally home on Tuesdays” is not necessarily authorizing entry on Tuesday. Capture availability and any stated access constraints as separate fields. Follow the property's approved process for permission, identity checks and contractor visits.

Avoid asking callers to dictate entry codes into a general conversation record. If access information is necessary, use the business's approved secure channel. The intake note can say that access arrangements need staff confirmation without storing a code alongside routine request details.

Write the urgency procedure with the property manager. The assistant should follow approved escalation instructions and avoid assuring the caller that a reported condition is safe. If a caller describes an immediate emergency, the response must use the organization's locally appropriate instructions rather than a universal number invented for a global audience.

A hypothetical handoff with an unresolved access question

Imagine a tenant reports water appearing below a kitchen cabinet in Unit 4C. They noticed it that evening and will be away until lunchtime tomorrow. They ask whether somebody can enter while they are out.

The handover should preserve five points: the exact unit, the observed issue, when it was noticed, the tenant's availability, and the unresolved access question. It should also identify who is expected to review it. “Maintenance request received; access authorization requires staff confirmation” is clearer than “Send plumber tomorrow.”

If the caller rings again, attach the additional observation to the same request where identity and record matching are reliable. Do not erase the earlier report or create two competing instructions for two teams.

Make ownership visible

A shared inbox can be a destination, but it is not automatically an owner. Decide who checks new requests, who covers absence, and how failed delivery is noticed. Use separate states for captured, received by staff, assigned, and completed if your operating system supports them.

Property platforms such as EliseAI explicitly position maintenance alongside resident workflows. That illustrates the importance of the surrounding process; it does not establish that another assistant has the same integrations.

Review a small set of cases with incomplete addresses, communal-area reports and repeat calls. Check that your call-routing approach has a usable fallback when the preferred person cannot respond. Before launch, ask the maintenance team to turn one sample note into its normal work order. Any question they must ask again is a candidate improvement to the intake.