One place to triage every queue across your firm.
Operations is the cross-client surface. Inbound mail that hasn't auto-matched lands here for triage. Every ImmiAccount lodgement attempt across every case lives in the eLodgement queue. Admins get a live count, a search, and per-row actions — without bouncing between client pages.
Inbound mail triage
Every email forwarded into your unique inbound address that we matched to a client lands on that client's communications thread. The Operations view shows the matched-and-attached feed across every client, so admins can verify, search, and intervene if something looks wrong.
- Search by subject, client name, or email address. Date-range filter (7 / 30 / 90 days / all).
- Server-side pagination at 25 per page — no more wall-of-rows on busy days.
- Org-isolated: each row only shows mail attached to clients in your firm.
eLodgement queue
Admin onlyEvery ImmiAccount lodgement attempt across every case in your firm. Status tabs (Active / Failed / Submitted / All) carry live counts. Search by client name, case ID, or lodgement ID. Per-row actions for refresh, re-queue, and cancel.
- Refresh, re-queue a failed attempt, or cancel one stuck in queued / in-progress.
- Export the failed-attempt error log as CSV for triage and post-mortems.
- Pauses at the declaration page on every lodgement. Humans approve — bots don't.
Per-client + cross-client. One pattern, two views.
Every workflow that touches multiple clients has both a per-client view (inside the client detail page) and a cross-client view in Operations. Same server actions, two framings: agents work the case from the CRM, admins work the queue from Operations. Audit logging is identical regardless of where you triggered it from.
Same server actions
No duplicated logic between per-client UI and queue UI.
Same audit log
Every action carries the agent identity, regardless of surface.
Same role gates
Admin-only queues stay admin-only — even via the API.