Every request owned. Every job tracked to closure.
Connect tenant requests, meter-detected issues, approvals, technicians and vendors in one traceable workflow from first signal to verified completion.
Please enter a valid email address.
Requests
Capture the issue where the tenant finds it.
Give tenants one structured route for the description, location and evidence. The property team sees the request in the building record instead of reconstructing it from calls, chats and forwarded photos.
- Capture the affected site, unit, category, description and permitted attachments.
- Acknowledge receipt, so the tenant knows the request landed.
- Approve, reject or request more information before creating work.
Work orders
Give every job an owner and expectation.
Route approved work by site and service category, then keep priority, due date, assignee and evidence on the same record. Managers see blockers; technicians see what they own next.
- Assign default responsibility by site, asset or service category.
- Track priority, due date, status and attachments on the task.
Next to the data
Show the technician what the building saw first.
A leak, failed schedule or silent meter can create the work order with its readings already attached. The technician investigates the likely cause; the manager verifies whether the building returned to normal.
- Link the triggering meter, alarm, location and recent history to the task.
- Record diagnosis, action, parts, cost and completion evidence on the task.
- Surface repeated failures and reopened work instead of treating each ticket as isolated.
Keep the service team. Give everyone one record.
Volts does not require a new contractor model. Internal technicians and authorised vendors work from the same building context, while ownership, access and evidence remain controlled by your organisation.
FAQ
Maintenance without the shared-inbox gap
Can tenants submit requests themselves?
Yes. A tenant can submit a request, with a location, a category and attachments, through the access provided for that tenant and unit.
Does every request become a work order?
No. An authorised user can approve, reject or request clarification. Only approved requests become work with an owner, due date, priority and tracked status.
How does work reach the right person?
Routing can use site, service category and a default responsible user per category. Exceptions remain visible for manual assignment rather than disappearing into an unowned queue.
Do we need the full property module?
It becomes more useful when tenant, location, meter, expense and billing context are available in the same operating record.
Can external vendors use the system?
Yes. What a vendor can view and change is set when their access is created.
Can we track response and resolution SLAs?
Reports distinguish first response from completed and verified work, which is the split an SLA is measured on.
How is a job verified as complete?
Closure can require a completion note and attachments, so “done” means the agreed evidence exists.
Can Volts identify recurring failures?
Yes, when tasks share consistent site, asset and category data. Volts can surface repeat incidents, reopened work and the related meter history.
Bring one lost request. Map its path to closure.
Show us how a tenant issue or meter alarm moves today. We will map the owner, approvals, evidence and closure step, then demonstrate the same workflow in Volts.