Skip to content
Cross-client workflows

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 across every case lives in the lodgement register. Admins get live counts, a search and the trail behind each row - 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.
How inbound mail works

Lodgement register

Admin only

Every ImmiAccount lodgement across every case in your firm, made through the eLodge extension in the agent's own browser. Status tabs (Active / Failed / Submitted / All) carry live counts. Search by client name, case ID or lodgement ID. Each row shows who started it, the page it reached and the TRN once submitted.

  • Refresh a row, see which lodgements have gone quiet and cancel one that will not be finished.
  • Export the failure log as CSV for triage and post-mortems.
  • Nothing here signs in to ImmiAccount. The agent fills, reviews and submits; the register records.
How eLodgement works

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.

Operations - Workflow Automation for Migration Practices | ImmiIQ