Document chasing that captures consent first
When a client doesn't reply about their birth certificate, Immi Flow follows up — only after consent is recorded for AI-assisted communication. Every nudge is logged.
The automation layer for Australian immigration practices.
From first-contact FAQs to guided document collection, automatic client reminders, and unified case communication — Immi Flow runs the rote work across the full client journey, in any language your clients message you in. Licensed-agent work stays with the licensed agent.
Example audit export
manifest.json cases/ (142 records) consent_records/ (142 records) agent_attestations/ (8 records) ai_events/ (3,847 records) date_range: 2025-04-15 → 2026-04-15
Trust
Built for the regulatory environment Australian RMAs actually work in.
Immi Flow is built around OMARA's compliance obligations, MARN-verified agent identity, and MIA professional membership conventions. We assume you know your registration; we make sure your software respects it.
OMARA
Built around OMARA compliance obligations.
MARN
MARN-verified agent identity.
MIA
Compatible with MIA membership conventions.
Compliance
Four compliance commitments, named in plain English.
- 01
7-year retention
Every case event, document upload, AI interaction, and consent record is retained for seven years and surfaced in your retention notice. Default policy; configurable per agency.
- 02
14-day audit export
When OMARA asks, you have 14 days. Immi Flow exports a single ZIP — case events, AI interactions, consent records, agent attestations — with a top-level manifest reconciling counts and date ranges.
- 03
Human-in-the-loop attestation
Every agent attests, per OMARA's March 2026 mandate. Every AI-drafted reply is logged as aiOutputReviewed when an agent sends it. Per-agent status visible on the Compliance page.
- 04
Written consent capture
No AI processing of applicant data without recorded written consent. Consent is captured at the start of every chatbot session, persisted with timestamp and version, and surfaced as a coverage metric on the Compliance page.
ImmiAccount coexistence
Your clients still lodge through ImmiAccount. Immi Flow handles everything before that.
Immi Flow does not lodge applications. It manages intake, documents, client communication, AI-assisted drafting, consent, and audit history — then hands the prepared case to your existing ImmiAccount workflow. You keep the lodgement system you already trust. We replace the spreadsheets, the email chases, and the PDF folders.
Immi Flow
Intake → drafting → consent → audit
- Intake
- Documents
- Client communication
- AI-assisted drafting
- Consent capture
- Audit history
Department of Home Affairs
ImmiAccount
Lodgement remains in ImmiAccount. Immi Flow does not replace it.
Day-to-day workflow
The day-to-day work, with the audit log written for you.
Case management with an OMARA-shaped audit trail
Every case event — created, document received, status changed, AI summary generated — is written to the audit log in the format the export ZIP expects.
AI drafting with attestation, not hands-off
AI drafts; the agent reviews and sends; the system writes aiOutputReviewed. The agent stays in the loop because OMARA requires it and because the audit log proves it.
Templates tied to your visa types
Document templates per agency per visa type. Update the template, sync it to existing cases.
Competitive positioning
Compared with Migration Manager and Officio, where Immi Flow is different.
Migration Manager and Officio are case management systems built for migration practices. They both work. Immi Flow is built for what changed in 2025 and 2026: AI-assisted client communication, OMARA's HITL mandate, and the audit-export expectation. If your current system was designed before those obligations existed, this is the gap we close.
Case management
- Migration Manager
- ✅
- Officio
- ✅
- Immi Flow
- ✅
AI-assisted client communication
- Migration Manager
- ❌
- Officio
- Partial
- Immi Flow
- ✅
OMARA HITL attestation per agent
- Migration Manager
- ❌
- Officio
- ❌
- Immi Flow
- ✅
14-day audit export ZIP (OMARA-shaped manifest)
- Migration Manager
- ❌
- Officio
- ❌
- Immi Flow
- ✅
Written consent capture for AI processing
- Migration Manager
- ❌
- Officio
- ❌
- Immi Flow
- ✅
ImmiAccount integration
- Migration Manager
- Coexists
- Officio
- Coexists
- Immi Flow
- Coexists
Document chasing automation
- Migration Manager
- Manual
- Officio
- Partial
- Immi Flow
- ✅
Pricing transparency
Per-seat pricing, no surprise compliance fees.
Immi Flow is priced per agent seat. Compliance features — audit export, consent capture, attestation — are included in every plan, not gated behind an enterprise tier.
Ready to see how Immi Flow handles your next OMARA audit?
Pre-demo questions
Five questions we hear before every demo.
- Does Immi Flow replace ImmiAccount?
- No. ImmiAccount remains your lodgement system. Immi Flow handles intake, documents, AI-assisted drafting, consent, and audit history, then hands the prepared case to your ImmiAccount workflow.
- How does Immi Flow handle the OMARA AI human-in-the-loop mandate?
- Every agent records a personal attestation. Every AI-generated reply is logged as aiOutputReviewed when an agent sends it. The Compliance page shows per-agent attestation status and the recent audit-event feed.
- Where is my agency's data stored?
- Australian region. Immi Flow stores agency data, case events, AI interactions, and consent records in Australian-region infrastructure. Detailed data residency answers are available on request before signing.
- What does the 14-day audit export actually contain?
- A ZIP archive with case events, AI interactions, consent records, and agent attestations, plus a top-level manifest that reconciles record counts and date range. Available synchronously for small ranges and via async email delivery for larger ranges.
- What does Immi Flow cost?
- Per agent seat, with all compliance features (audit export, consent capture, attestation logging) included on every plan. See the pricing page for current per-seat pricing.