Platform
Same three agents. Every department.
Voice, customer-facing and ops-facing agents apply across a full business, not just the front desk. Sales, Operations and Marketing are live; the rest are built for your business, not a shelf product.
Owner / CEO
Built to orderSynthesizes every department's digest into one state-of-business view
Touches: Aggregated rollups across departments, read-only
Access: Read
New — same reconciliation logic pointed at more tables
Sales
LiveLead intake, qualification, booking
Touches: Leads, bookings
Access: Read/write
Live — Mia + customer-facing agent
Operations
LiveJob/ticket triage, dispatch, completion tracking
Touches: Jobs, tickets, maintenance
Access: Read/write
Live — the ops-facing agent, proven on the PropOps property system
Finance
Built to orderOverdue invoice flags, per-client/per-building profitability, reconciles bookings against payment
Touches: Invoices, payments
Access: Read-only; drafting a reminder requires approval
Built to order — same DB-read-and-report shape, pointed at a payments table
Logistics
Built to orderParts-to-job matching, reorder flags, vendor assignment
Touches: Inventory, vendor tables
Access: Read/write
Built to order
Marketing
LiveAd performance digest, budget reallocation recommendation, executes on approval
Touches: Ad-platform / attribution data only
Access: Read + act on approval
Live — Oravio's performance and update agents
HR / Staffing
Built to orderShift coverage, certification/renewal tracking, compliance gaps
Touches: Staffing/compliance tables, tightly scoped
Access: Read-only
Built to order — the most sensitive data domain
Compliance
Built to orderIntake audit trail, consent logging, escalation record
Touches: Append-only audit log
Access: Append-only, never edits
Earned per client, not built speculatively
| Department | Agent does | Data it touches | Read / act | Status |
|---|---|---|---|---|
| Owner / CEO | Synthesizes every department's digest into one state-of-business view | Aggregated rollups across departments, read-only | Read | New — same reconciliation logic pointed at more tables |
| Sales | Lead intake, qualification, booking | Leads, bookings | Read/write | Live — Mia + customer-facing agent |
| Operations | Job/ticket triage, dispatch, completion tracking | Jobs, tickets, maintenance | Read/write | Live — the ops-facing agent, proven on the PropOps property system |
| Finance | Overdue invoice flags, per-client/per-building profitability, reconciles bookings against payment | Invoices, payments | Read-only; drafting a reminder requires approval | Built to order — same DB-read-and-report shape, pointed at a payments table |
| Logistics | Parts-to-job matching, reorder flags, vendor assignment | Inventory, vendor tables | Read/write | Built to order |
| Marketing | Ad performance digest, budget reallocation recommendation, executes on approval | Ad-platform / attribution data only | Read + act on approval | Live — Oravio's performance and update agents |
| HR / Staffing | Shift coverage, certification/renewal tracking, compliance gaps | Staffing/compliance tables, tightly scoped | Read-only | Built to order — the most sensitive data domain |
| Compliance | Intake audit trail, consent logging, escalation record | Append-only audit log | Append-only, never edits | Earned per client, not built speculatively |
Built on scoped access, not blanket access
Each department agent runs on a scoped role with row-level security (Postgres RLS on Supabase) — a department's agent can only see its own rows. Every agent defaults to read-and-recommend; writing or sending anything requires explicit approval. This is a technical fact, not marketing language — it's how the agents are actually built.