Tenant maintenance requests, no call center

Published · Updated · 7 min read

The short answer

A call center solves a capture problem: someone answers the phone and writes the request down. Most buildings do not have a capture problem. They have an ownership problem. Requests come in through the concierge, the security desk, the building manager’s mobile, email, a residents’ WhatsApp group and the occasional note under the office door, and nobody can say which ones are open.

The fix is a process, not more people on phones:

  1. One written intake channel for routine requests, plus an emergency phone line.
  2. Triage rules that set priority in seconds.
  3. A named owner and a deadline for every request.
  4. Escalation when the deadline passes.
  5. Updates to the tenant at the moments that matter, and a closing message.

Step 1: one intake channel

Pick one channel for routine requests and make it easy. The best channel is the one that captures the details without a conversation: a short web form, a link in the tenant welcome pack, or a QR code in the lift lobby and inside each unit’s service cupboard. A QR code per unit, common area or asset opens the request already tagged with its location, so the resident never has to describe where they are.

Whatever the channel, it should capture:

  • Unit number or exact common-area location (floor, lobby, car park level and bay)
  • Category: plumbing, electrical, air-conditioning, doors and locks, lifts, cleaning, pests, other
  • A short description in the tenant’s own words
  • At least one photo
  • Contact number and preferred contact method
  • Access permission and preferred times
  • For leaks: is water actively running, and is it affecting a neighbour?

Keep the form short. Each extra field reduces the number of people who finish it. Location, description, photo and access matter most.

What to do with phone and WhatsApp requests

They will keep coming, especially in the first months. The rule is simple: whoever receives a request outside the channel logs it in the channel before acting on it. Once the front desk logs every phone request, tenants learn quickly that the form is faster.

Step 2: triage in under a minute

Triage means reading the request, checking the location, setting priority and assigning an owner. A written priority table makes this quick and consistent between shifts.

Priority Examples Typical response target Typical resolution target
Emergency Active water leak, lift entrapment, no power to a unit, gas smell, fire alarm fault, security breach Immediate Make safe as fast as safely possible; permanent fix scheduled
Urgent No hot water, AC failure in hot weather, blocked toilet (only one in unit), main door not locking Within a few hours Same or next day
Routine Dripping tap, loose handle, faulty socket, common-area light out Within one working day Within a few working days
Planned Repainting, minor improvements, tenant-requested upgrades Acknowledge within a few working days Scheduled with the tenant

The targets above are typical starting points. Set your own based on staffing, contract terms and any lease or local requirements, then publish them to tenants.

Two rules that save a lot of trips

  • Call before going. A two-minute call to confirm access and the exact fault often saves a wasted visit and lets the technician bring the right part.
  • Look at the photo first. A photo of a “leak” frequently turns out to be condensation from an AC unit, which is a different trade and a different priority.

Step 3: one owner, one deadline

Every request needs exactly one named owner, whether a technician, a team or a contractor, and a deadline that comes from its priority. “Maintenance” is not an owner. “Ahmed, today by 4 p.m.” is.

The owner should:

  • accept the job so the desk knows it has been seen
  • update status when on the way, on site, waiting for parts and done
  • record what was actually done
  • attach a photo of the finished work

Status updates matter more than they seem. Most tenant follow-up calls are the question “has anyone seen my request?” A visible “accepted” status answers that without a call.

Contractors

For work done by contractors, the same rules apply: an owner on your side, a deadline, and proof. If the contractor cannot update your system directly, the building manager updates it when the contractor reports back. Do not close the request on the contractor’s word alone; ask for a photo or a signed job sheet.

Step 4: escalation when it is late

Requests rarely get lost because someone refuses to do them. They get lost because the owner gets busy and nobody notices the deadline has passed. Escalation fixes that:

  • When a request passes its response target without being accepted, notify the shift supervisor.
  • When it passes its resolution target, notify the building manager.
  • When an emergency is not closed within the day, notify the chief engineer or property manager.

Escalation should be automatic or at least routine. A daily review of overdue requests at the morning meeting works if it actually happens every day.

Step 5: close the loop with the tenant

Tenants judge maintenance on two things: whether the fault was fixed, and whether they were kept informed. The second costs almost nothing.

Send updates at three moments:

  1. Received: “We have your request about the kitchen tap. A technician will contact you today.”
  2. Scheduled or delayed: “Parts are ordered and expected Thursday. We will confirm a time.”
  3. Done: “The tap has been replaced. Please let us know if anything is still wrong.”

Asking for a quick rating at the end is useful. Low ratings point to a technician who needs coaching, a category that is always slow, or a communication gap.

Getting tenants to use the new channel

A new channel only works if tenants use it. Expect a transition period of a few months, and plan for it.

  • Tell them once, clearly, in several places. A one-page notice in the welcome pack, a sign in each lift lobby, an email or message to every unit, and the link in the signature of everyone who replies to tenants.
  • Make the form faster than the phone. If the form takes longer than a call, people will call. Test it yourself on a phone, standing in a corridor.
  • Answer phone requests politely, then point to the form. “I’ve logged that for you. Next time the QR code in your lobby is the quickest way, and you’ll see when someone accepts it.”
  • Show progress. The real incentive is visibility. Once tenants see that a written request gets an acknowledgement and an update, they stop calling to chase.
  • Do not punish the old channel. Refusing to take a phone request damages trust. Log it, and let the better experience do the persuading.

What to measure

Once requests are in one place, a few numbers tell you most of what you need:

  • Open requests by priority and age. Anything old and open is a problem.
  • Time to first response. How long until someone accepts the job.
  • Time to completion by category. Shows which trades or contractors are slow.
  • Repeat requests from the same unit or location. Points to a root cause that has not been fixed.
  • Tenant ratings. The fastest feedback you will get.

Review them weekly with the team, not just monthly with the owner.

Where TaskLoop fits

TaskLoop covers this workflow end to end: a resident, tenant or hotel guest scans the QR code for their unit, room, common area or asset, submits a request, sees it tracked and rates the service, while the admin dashboard assigns it with priority and deadline, the staff mobile app handles accept, update and photo proof, and overdue tasks escalate to supervisors. Contractors can be assigned jobs and close them with photo proof too. See guest and tenant requests and escalations.

Summary

A call center answers phones. What tenants actually need is a request that is captured once, owned by one person, escalated when it is late, and closed with a message. Set that up with one intake channel, a written priority table and a daily look at what is overdue, and a small building team can handle a large building without adding phone lines.

  1. Tenant reports
  2. Triage and priority
  3. Assign
  4. Technician acts
  5. Tenant updated
  6. Closed and rated
A tenant request from report to rating

Written by the TaskLoop team at RozaMoon LLC · About

Questions people ask

Should we stop taking maintenance requests by phone?

Not completely. Emergencies such as floods, lift entrapments, gas smells and fire alarms should always have a phone number that a person answers, day and night. For everything else, a phone call is the slowest and least reliable way to log a request. Keep the phone for emergencies and steer routine requests to a form or QR code that captures the details in writing.

What information should a tenant request include?

Unit or exact location, a short description, a category such as plumbing or electrical, a photo, contact details and access permission: can the technician enter if the tenant is out, and at what times. Location and access are the two fields most often missing, and they cause most wasted technician trips.

How fast should we respond to tenant requests?

Set targets per priority, not one target for everything. An emergency needs an immediate response and someone on site as fast as is safely possible. Urgent issues such as no hot water usually need same-day action. Routine requests can be scheduled within a few working days. Publish the targets to tenants so expectations match what your team can actually deliver.

Who should triage requests in a small building team?

Usually the building manager or the front desk during the day, with a clear on-call rule at night. Triage means checking the location, setting priority and assigning an owner. It takes less than a minute per request once the rules are written down. The important part is that one person owns triage per shift, so nothing sits unassigned.

How do we stop the same request being reported many times?

Common-area faults such as a broken lift or a corridor light get reported by many tenants. Log the first report, link duplicates to it rather than creating new jobs, and post a short notice in the lift lobby or on your tenant channel once it is acknowledged. Visible acknowledgement is what stops people reporting the same fault again.

See your own workflow in TaskLoop

Tell us how requests reach your team today. We will show you the same flow running in TaskLoop, with your roles and your request types.