When a resident reports a problem in Buildium, Occupella builds the card, pulls the unit’s history and drafts the reply and the work order. You edit them, pick the vendor and send.
A resident reports a problem in Buildium. Occupella verifies the webhook and builds a readable card from the record: title, address and unit, who reported it and who it is assigned to.
The task, the unit, the active lease and its tenants, and ninety days of prior tickets at that address. Any number it shows is checked against the record first, like the third HVAC ticket in 90 days.
A reply to the resident, a work order for the vendor, a note about the pattern. Each is written out with the reason it was suggested, and you can edit every word.
One work order in Occupella, with example data.
Occupella writes to your Buildium account too. For maintenance, these are the changes it can make.
A completed work order can’t be reopened. Buildium locks it, and no API can undo that, so Occupella doesn’t offer it.
The approval card for a new work order, with example data.
The Today strip at the top of your Inbox counts open work orders with no update in 7 days, and groups overdue tasks by property so a messy week is one line per building.
Two Inbox reminders, with example data.
“Has this unit done this before?” “Who did we use last time?” Typed into the card and answered there, with the property, unit and task already in context.
“We use Redbud for anything electrical.” It keeps that for your company and brings it back the next time an electrical request comes in.
“What is overdue?” lists open tasks (new, in progress and deferred) with priority, property, assignee and due date, overdue first.
Connect Buildium and watch it handle a real work order from your account. No card to start.