Maintenance and vendors
The request follows its vendor, its status and its answer back to the occupant. In a condominium, it is also what lets somebody answer a board member without opening ten email threads.
Hopem
An emergency call in a building does not wait for an integration. The request is written into Zenvox, attached to an address and a unit; at Hopem, no operation is validated.
7 days, 20 answered calls, no card
Where your emergency call lands
The request is written into Zenvox: address, unit, occupant, the nature of the emergency sorted under your written rules — water damage, heating failure, elevator, front door — and what the occupant said, in their own words. The person on call is alerted. Hopem keeps the truth of leases and accounting: nothing is written there today.
On access, the research is explicit: no operation is validated here, vendor documentation and your agreement remain to be obtained, and a reference to another platform establishes nothing for this one. That absence calls for a request, not a conclusion, and nothing is asked of you meanwhile.
Hopem is a property management system born here: buildings, units, occupants, leases and the accounting of owners or of the syndicate. Your phone rings at the worst moment — evenings, weekends, during a storm.
Read, create, update, cancel
The status below reflects low-confidence research and access that is not established. Documentation obtained from the vendor is what will move it.
| Action | Status | What that means |
|---|---|---|
| Read | To qualify | The needs are named: units, occupants, maintenance requests, vendor, status. No operation is validated to date; documentation and your agreement have to be obtained from the vendor. |
| Create | Zenvox native mode | While no operation is established, the maintenance request is created inside Zenvox, complete — building, unit, occupant, nature, urgency — and your team carries it into the software. |
| Update | Zenvox native mode | Assigning a vendor or changing a status commits the mandate and its spending ceiling. With no verified operation, assignment stays a management decision, recorded with its time. |
| Cancel | Zenvox native mode | Closing a request assumes reconciliation between work done, invoice and the report to owner or syndicate. It belongs to your team, and Zenvox stops its follow-ups at the same moment. |
What is included, what needs an add-on
Answering after hours, attaching the call to an address and a unit, applying your urgency sorting and alerting the on-call person belong to your real estate base. Vendor tracking and spending approval are named add-ons.
The authorisation, and what holds the truth
While access is not established, your management rules hold — and they get written down before the first night on call.
- Zenvox asks for no password and does not sign into your software on your behalf
- Access documentation is requested from the vendor, with your customer agreement: the only honest route
- Your software stays the system of record for unit, occupant and accounting
- Urgency sorting is written with you: what wakes somebody, what waits for morning, and who gets called
- An operation is confirmed to an occupant only after a validated write in the system of record
A January night, twenty below outside. An occupant calls the management line. No data from the software is read.
OccupantHi, there is no heat in my apartment and it is getting really cold in here.
ReceptionistLet me take your name, a callback number, the building address and your unit number. As far as you know, do your neighbours have heat?
ReceptionistI am filing this as an emergency under the management rules and alerting the person on call right now. They will call you back; I cannot confirm a visit time myself.
The on-call line gets the alert with building, unit, occupant, nature of the failure, a hint that the problem may be building-wide, and the time of the call. The manager knows which mandate applies before opening a computer.
When access is not established
That is today status, and the service runs fully in Zenvox native mode.
- The request is created inside Zenvox with building, unit, occupant and nature of the problem
- Urgency sorting follows your written rules and raises the on-call alert
- Calls from condominium board members are routed against your list, with no disclosure to anybody outside it
- You find the call, its transcript and its reason in the app
- The day the vendor supplies documentation and access, the matrix changes line by line
Questions about this connection
Is there a connection to Hopem?
No operation is validated here: vendor documentation and your agreement remain to be obtained, and a reference to another platform establishes nothing for this one. Nothing is written into Hopem today.
Who decides what wakes somebody up at night?
You do: urgency sorting is written with you — what wakes somebody, what waits for morning, and who gets called. The on-call line receives the alert with building, unit, occupant, nature of the failure and time of the call.
Does the receptionist assign a vendor?
No. Assigning a vendor or changing a status commits the mandate and its spending ceiling; with no verified operation, assignment stays a management decision, recorded with its time.
Condominium board members call too — how is that filtered?
Their calls are routed against your list, with no disclosure to anybody outside it. The request keeps building, unit and occupant, and the occupant is told only after a validated write in the system of record.
What changes once the vendor supplies access?
The matrix changes line by line, and your setup stays put. Meanwhile nothing is asked of you: no password, no key, no connector to program.
Where to next
See the practice concerned, or the full list of software studied.
Hopem