Philippines staffing guide · Published
Set up maintenance intake triage for a property management virtual assistant
How to capture tenant maintenance requests while safety and repair decisions stay with authorized staff

A maintenance inbox can become dangerous when every request looks like another ticket. A dripping faucet, a sparking outlet, a broken exterior lock, and a complaint about an appliance do not call for the same response. Yet the person reading the first message may have only a sentence, a blurry photo, and an old tenant record. A property management virtual assistant can bring order to that intake if the role starts with collection and routing, not repair judgment.
The assistant's job is to establish which property and unit the request concerns, capture the tenant's words, ask approved factual questions, locate the right contact path, and put the issue in front of an authorized property manager or emergency provider. The assistant should not diagnose a hazard, tell a tenant that a home is safe, authorize an unapproved repair, or decide what the lease or local law requires.
Give tenants one clear way to report a problem
Start with the channels the property manager can monitor reliably. A web form or resident portal may be the main route, with a telephone option for people who cannot use it. State plainly that an inbox is not an emergency service. Publish the emergency instructions approved for each property, including when a resident should contact public emergency services. Do not bury that direction at the end of a long form.
The intake should ask for the property, unit, resident name, reliable callback method, when the problem began, what the resident can observe, whether the condition is changing, and whether anyone has already taken action. Let residents use their own words. A forced category can help sorting, but it must not replace the description. Someone may choose "plumbing" for water coming through a ceiling even though the source is unknown and the immediate concern is broader than a fixture.
Avoid questions that invite the assistant or tenant to perform an unsafe test. The property manager should approve every follow-up prompt. Asking whether water is still visible may be appropriate. Telling a resident to open an electrical panel or climb onto a roof is not routine intake. When the approved script does not fit, the assistant should preserve the message and escalate it.
Verify the record before assigning the request
The first operational error often happens before anyone discusses the repair: the ticket is attached to the wrong unit, owner, or vendor agreement. Match the resident's details against the current property record. Confirm the service address and unit without revealing information about another resident. If two buildings have similar names, use the stable property identifier rather than relying on the email subject.
The work record should retain the original message, attachments, received time, channel, property and unit identifiers, callback information, and any approved follow-up answers. Add the assistant's summary in a separate field. That separation matters. A summary such as "minor leak" can erase the tenant's statement that water has reached a light fitting. The property manager needs both the short queue view and the source wording.
Check for an open request about the same condition. A second report may be a duplicate, an escalation, or evidence that the problem spread. Link the records instead of deleting one. Keep the new timestamp and description. A vendor appointment on an earlier ticket does not prove that the later report has been handled.
Route by written triggers, not personal instinct
The property manager should create a routing table using its own properties, local obligations, insurance instructions, vendor agreements, and after-hours coverage. The table can name observable triggers such as active water flow, loss of access, signs of fire, a reported gas odor, sewage, no essential service, or a condition involving an injured person. Qualified owners decide the response attached to each trigger.
The assistant applies the table and records which trigger matched. If the facts are unclear, the record moves to urgent owner review rather than down to a routine category. Speed matters, but so does accuracy. An assistant should not make a condition sound less serious to fit an available vendor slot, and should not label every vague complaint an emergency to avoid responsibility.
Write an explicit fallback for system outages and unanswered calls. It should identify the next approved contact, the time allowed before escalation, and what the assistant may tell the resident in the meantime. A status message should report what has actually happened: the request was received, an approved contact was notified, or a visit was scheduled. It should not say that the problem is fixed before the responsible person confirms it.
Keep vendor dispatch within an approval boundary
A vendor directory needs more than phone numbers. Record approved trade, service area, property access rules, hours, after-hours status, insurance or qualification review owner, spending authority, and who may approve work. The assistant can contact a listed provider under the conditions the property manager has accepted. A convenient search result is not a substitute for vendor approval.
The dispatch note should contain the service address, safe contact information, observable problem, access instructions that the resident and manager have approved, ticket number, response deadline, and the person who can authorize changes. Do not include unrelated tenant records. If a vendor proposes a different scope, higher charge, destructive access, or work outside the standing authorization, return the proposal to the named owner.
Treat banking or payment changes as a separate security event. A new remittance account in an email thread should not update the trusted vendor record automatically. The assistant may flag the request and start the company's independent verification process. The person who approves the vendor record should not rely only on the contact details contained in the change request.
Make access coordination visible
Entry rules vary by property, agreement, and jurisdiction. The assistant should use instructions approved for the specific building and request. Record whether the resident supplied a preferred window, whether notice is required, who sent it, which approved person may enter, and whether the appointment was confirmed. Do not translate a resident's silence into consent.
Keys, lockbox codes, alarm details, and resident schedules need restricted handling. Keep them in the authorized property system and share them only through the accepted method. A broad task board can show that access instructions exist without displaying the instructions themselves. Remove temporary access when the visit ends or the provider changes.
Accessibility and communication needs belong in the operating plan. A resident may need a different contact method or a reasonable modification to the normal process. The assistant can capture the request exactly and route it to the responsible manager. The assistant should not decide whether the request is legally required or medically justified. The U.S. Department of Housing and Urban Development provides official fair housing information; property managers should obtain advice for the laws and duties that apply to their locations.
Close with evidence, not a changed status label
A vendor marking a visit complete is one event, not the whole closure record. Capture the arrival and departure information available, work description, photos or documents allowed by policy, parts or follow-up noted, invoice reference, resident communication, and the manager's review. If the resident says the condition continues, reopen or link a follow-up according to the written procedure. Do not erase the original completion event.
Use separate states for dispatched, appointment confirmed, access blocked, vendor attended, follow-up required, manager review, resident update due, and closed. Each open state needs an owner and deadline. This shows whether delay belongs to access, vendor capacity, approval, or missing information. A single average completion time hides those differences.
Audit a small sample each week. Compare the queue summary with the resident's source message. Check that triggers were applied correctly, the right property and vendor were used, access information stayed controlled, approvals were recorded, and resident updates described the real state. Review every urgent escalation and a sample of routine closures. Correct the earliest process defect rather than merely editing the final ticket.
Build a pilot around real failure points
Test the workflow with synthetic or safely redacted cases before expanding it. Include a duplicate report, an after-hours water problem, a vendor that cannot attend, a resident who cannot use the portal, an unclear unit number, an access disagreement, and a proposed cost above the assistant's limit. These cases reveal more than a stack of straightforward appliance requests.
For each case, ask whether a second person can reconstruct what the resident reported, which trigger applied, who decided the response, what was communicated, and what remains open. If the answer depends on a private chat or somebody's memory, the workflow is not ready.
A virtual assistant can keep the intake complete, timely, and visible. The authorized property manager retains safety assessment, legal interpretation, repair scope, vendor approval, spending decisions, access authority, and final closure. Teams scoping this work can review OverseasVirtualAssistant.com's virtual assistant services and bring a redacted maintenance form, routing table, and difficult closed ticket to the first conversation.
Source
Plan the next step
Use the related service page to scope systems, approvals, stop rules, and owner responsibilities before delegating this workflow.
Review the related service