SOLUTION DEMO
Property Maintenance Automation Demo
Follow a maintenance request from intake to a reviewable work order, with vendor coordination and staff approval kept visible.
This is a static, fictional scenario, not client work or a live dashboard. No vendor is contacted, no tenant message is sent and no timer, repair or system update actually runs.
Fictional portal request · MAINT-DEMO-001
A tenant reports a leak
“Water is leaking under the kitchen sink and getting worse.”
Sample portal context: Example Property A, Unit DEMO-02. These are invented record labels, not a real address or verified tenant identity.
Flagged for staff assessment
The description suggests a plumbing issue and warrants staff attention in this scenario. The demo cannot determine whether a situation is safe, diagnose the cause or replace an emergency response process.
Do not wait for a demo timer or automated classification to handle a real emergency.
Illustrative work-order snapshot
Scenario stage: dispatch requestedThis snapshot assumes a staff member has reviewed the request and authorized a vendor contact. Every status below is simulated.
- Classification
- PlumbingSuggested category; staff review required.
- Urgency
- High priorityIllustrative flag, not a safety assessment.
- Property / unit
- Example Property A / DEMO-02Matched from fictional portal context only.
- Vendor
- Example Plumbing VendorFictional approved-list entry; acceptance pending.
- Dispatch
- Requested (simulated)Not accepted, scheduled or completed.
- Tenant update
- Sent (simulated)Acknowledgment only; no arrival promise.
- Escalation timer
- Started (simulated)15-minute sample window; no live countdown.
- Owner
- Example maintenance coordinatorResponsible for follow-up and exceptions.
Illustrative tenant acknowledgment
“Your request has been recorded for staff review. We have not confirmed a visit time. The property team will update you when arrangements are confirmed.”
Example wording only. A real message needs your approved contact and urgent-response instructions.
How the status could change
Read these as successive storyboard stages, not live progress or completed actions. Moving to the next stage depends on the checks described.
- Received
Portal request recorded
The sample request is attached to the fictional property and unit records. No tenant identity or address is shown.
- Review required
High priority suggested
A plumbing category and high-priority flag are suggested. Responsible staff must assess the situation using their own response procedure.
- Dispatch requested
Staff authorization assumed for illustration
The scenario assumes staff has checked the request and authorized contacting Example Plumbing Vendor from an approved list. A dispatch request is not vendor acceptance.
- Awaiting acknowledgment
Sample escalation timer started
An illustrative 15-minute acknowledgment window starts. If no response arrives, the task escalates to staff. This is a demo setting, not a recommended emergency-response target.
- Scheduled
Vendor acceptance and access assumed
A later scenario assumes the vendor accepts and staff confirms access and a visit window. Only then could a schedule update be sent.
- Completion review
Vendor report received in the scenario
Staff check the report and any required confirmation. An unresolved issue keeps the ticket open.
- Closed after approval
Invoice checked separately
The illustrated end state assumes staff confirms completion and approves the record update. Invoice extraction and reconciliation do not authorize payment.
Human checks do not disappear
- Staff assess urgency and follow the property's response procedure.
- Vendor availability, spending authorization and access permission are confirmed separately.
- An acknowledgment is not a confirmed appointment or a repair.
- Completion needs the agreed evidence and review; unresolved issues remain open.
- Invoice details can be extracted for checking, but no payment is authorized by this demo.
Map this to your maintenance process
Use a free 30-minute workflow review to discuss your request channels, systems and handoffs. Do not include tenant records, entry codes or credentials in the booking or contact form.