Skip to main content

​
Prerequisites

  • Maintenance Automation module enabled.
  • Vendor pools configured with skills and coverage.
  • Notification channels (email/SMS/webhook) set up.

​
Steps

1

Ingest tickets

  • Connect your portal/email/API to /api/v1/maintenance.
  • Map fields: ticket_id, unit_id, description, photos, contact.
    Tickets appear with “New” status.
2

Classify severity and category

  • Enable AI classification for severity (emergency/urgent/standard) and category (HVAC, plumbing, electrical, etc.).
  • Add rules for safety-critical flags.
    Tickets show severity and category tags.
3

Dispatch vendors

  • Set SLA by severity (e.g., emergency 4h).
  • Assign vendor pools with availability windows.
  • Enable auto-dispatch with confirmation requirements.
    Vendor assigned; ETA generated.
4

Notify tenants and track status

  • Enable tenant notifications with acknowledgements and ETA.
  • Log status updates and completions to CasaBoard.
    Tenant received ETA; status updates visible.
5

Verify completion and costs

  • Require completion notes/photos.
  • Capture cost/time for SLA and finance rollups.
    Ticket closed with completion data recorded.

​
Example API payload

{
  "ticket_id": "mnt_10021",
  "unit_id": "unit_7C",
  "description": "Water leaking under the kitchen sink for two days",
  "photos": ["https://files.casaai.dev/img/leak1.jpg"],
  "priority_hint": "high"
}

​
Tips

  • Start with manual dispatch + notifications, then enable auto-dispatch.
  • Add vendor skills and blackout windows to avoid misroutes.
  • Use webhooks to push work orders into your field ops or ticketing tool.

​
Troubleshooting

Check vendor pool criteria (skills/region) and SLA thresholds; ensure at least one vendor matches.
Require attachments in intake forms; validate URLs are accessible.
Confirm channel configs and webhook retries; monitor CasaBoard activity log.