Features

Previous: Technician App UI
Next: Architecture

This page summarizes what is implemented now, based on the current repositories.

A) Ticketing and lifecycle

• Ticket CRUD and list/detail APIs.
• Lifecycle actions for tenant and technician confirmation/decline/start/complete.
• Worklog updates including materials_used.
• Media attachment upload and ticket-linked retrieval.
• CSV export and ticket report/PDF endpoints.

B) SLA and escalation

• Priority-based SLA deadline computation (response_due_at, resolution_due_at).
• sla_status progression: on_track, at_risk, breached.
• Escalation level tracking and breach views.
• Administrative SLA override endpoint for controlled operational handling (POST /api/tickets/{ticket_id}/force-breach).

C) AI-assisted intake

• AI chat intake endpoint that can create tickets.
• Vision processing path for uploaded media.
• Fusion of text + vision output.
• AI decision log writeback (ai_logs) and feedback endpoint (PATCH /api/ai/logs/{log_id}/feedback).

D) Admin and operations

• Building/apartment/user/technician management APIs.
• Technician bulk update/delete.
• System config endpoints.
• Audit logs and metrics (/api/metrics/system, /api/metrics/sla-compliance-trend).

E) Dashboard

• KPI cards/charts for jobs, SLA, and AI confidence.
• Jobs table with filtering/actions/export.
• Chat, user management, system config, and audit pages.
• Manager-scoped building visibility and operational controls.

F) Mobile App Coverage

• Technician app: job execution, status updates, messaging, and profile/availability workflows are integrated with backend endpoints.
• Tenant app: ticketing, chat, account, and request tracking workflows are integrated with backend endpoints.

G) Deployment

• Debian/Ubuntu installer and Docker Compose deployment path are implemented.
• Runtime mounts persist uploads and model artifacts.

Previous: Technician App UI
Next: Architecture