Example automation · Property management

Maintenance requests triaged and dispatched

Tenant maintenance requests are sorted by urgency, matched to an approved vendor and turned into a work order and a tenant reply. Emergencies go to the on-call person straight away.

Try it: open an item, then approve it or take it over. The data is fictional sample data and this is an example of what we'd build, not a client project.

Maintenance QueueExample · sample data

New requests0 of 3 handled

Unit 304, Riverbend Court · 6:12 am

No heat since last night

What arrived · Text message, 6:12 am

"its freezing in here, furnace not coming on since last nite, baby in the apt, -22 out"

What it read

Category
Heating98%
Urgency
Emergency (no heat, -22°C outside, infant in unit)96%
Vendor
On-call HVAC (approved list)100%
Access
Tenant home all day90%

% is how sure the software is of each field. Under 80%, a person checks it.

Emergency: on-call was texted at 6:12 am, before this was shown to you. Approving logs the work order and sends the tenant reply.

Work order and tenant reply

WORK ORDER: Furnace not running, Unit 304. Emergency, same day.

To tenant: "Thanks for letting us know. A heating technician is booked for this morning and will call you before arriving."

What it could save

Estimate · not a client result

For a 20-person property manager with about 400 suites. These numbers are assumptions, not measurements: the audit measures yours.

By hand today
60 requests a week × ~8 min each
≈ 8 h a week
With the automation
60 requests a week × ~2 min to review each
≈ 2 h a week
Difference
8 h − 2 h
≈ 6 h a week back

By hand: read, judge urgency, find the vendor, type the work order and the reply. After: the coordinator approves the draft; emergencies are paged first either way.

The job today

  • Requests arrive by email, text, portal and voicemail, and someone reads each one.
  • They decide how urgent it is and which vendor to call.
  • They type up the work order and the reply to the tenant.
  • An emergency sent at 11 pm waits until somebody reads it.

How the automation runs

  1. Trigger

    1. Tenant reports it

    Portal, email or text all land in one queue, matched to the tenant and unit by sender.

    In: Portal · email · SMS

  2. AI

    2. Sort by urgency

    No heat in winter, active leaks, no power and lockouts are emergencies. The rest is urgent, routine or planned, with the reason shown.

    In: Text AI

  3. Your system

    3. Emergency paged at once

    An emergency texts the on-call person immediately, before and without waiting for approval.

    In: SMS

  4. AI

    4. Match a vendor

    From your approved vendor list for that building and trade, and only from it. No match: no vendor is invented.

    In: Vendor list

  5. A person

    5. Coordinator approves

    Approve the work order and the tenant reply, or change the vendor or the urgency.

  6. Your system

    6. Work order out

    Logged against the unit, sent to the vendor, and the tenant is updated.

    In: Buildium or AppFolio

Example tools: Tenant portal, email and SMS · Buildium, Yardi or AppFolio · Your approved vendor list. The audit confirms what you actually run.

What it checks

Before a person sees a draft, these run. A draft that fails one is held, with the reason shown.

  • Urgency is below 80% confident, or the message mentions smoke, gas, flooding or injury: treated as an emergency.
  • Vendor must be on the approved list for that building and that trade.
  • Work orders over an owner's approval limit are routed to the property manager.
  • A second request for the same unit and issue within 7 days is linked, not duplicated.
  • Tenant replies are drafted from approved wording and never promise a price, a time or a fault finding.

When something goes wrong

Edge cases are planned for, not discovered in production.

Request is vague ('something smells weird')
Treated as urgent, and a two-question reply goes to the tenant. A gas smell is advised to call the gas emergency line first.
Sender isn't a known tenant
It is held and shown to the coordinator, not turned into a work order.
Vendor doesn't confirm in 2 hours (emergency) or 1 day (routine)
The coordinator is told and the next approved vendor is suggested.
Property system is unreachable
The work order is held with a copy emailed to the coordinator, so nothing waits on a sync.

What lands, and where

Once a person approves:

Buildium or AppFolio
A work order against the unit, with the tenant's original message attached.
Email or SMS to the vendor
The job, access notes and the contact number to arrange entry.
Tenant portal or SMS
The reply, with notice of entry where it applies.

Where a person stays in charge

The coordinator approves every work order. Emergencies are never left waiting for approval: on-call gets a text at once, and the coordinator sees it in the morning.

What it would cost

An Automation Build is from $8,000, with the price fixed before work starts. What moves it for this one:

  • How many channels requests arrive through
  • Whether the property system has an API or needs a workaround
  • Approval limits by building or owner

All prices are in Canadian dollars. GST is added where it applies.

What the audit checks first

Before anything is built, the $2,500 audit measures the job in your business, including the numbers the estimate above only assumes:

  • Requests a month and how they split by urgency
  • How long from request to vendor booked today
  • Who is on call, and how they're reached now

Have a job like this one?

The AI Automation Audit is $2,500, fixed: a working session on one workflow and a written plan in 5 business days, with costed options you keep. Credited in full if you build.

Request the $2,500 audit

Not ready to pay? Get a free video teardown of one workflow.

Describe your workflow

Don't see yours? Tell us about it. If it's repetitive and lives in software, we can likely automate it.

A person replies within one business day. No obligation.

We use what you send only to reply and to see which campaigns bring real projects. We never sell it. How we handle your data

More examples

A few of the automations we build, not the full list.

Request the audit · $2,500