How ImmiIQ works, page by page.

1. Click the search bar at the top of any page or press "/" on your keyboard to focus it.
2. Start typing an occupation name, ANZSCO code or keyword (e.g. "nurse", "261313" or "engineering").
3. Results appear instantly as you type. Each result shows the code, title and skill level.
4. Click any result to open its full occupation detail page.

You can search by partial codes too. Typing "2613" shows all occupations in that unit group.

1. Skill level and ANZSCO classification hierarchy (Major Group down to Occupation).
2. Which skilled occupation lists the occupation appears on (MLTSSL, STSOL, ROL, CSOL) and any caveats.
3. Assessing authority details and links.
4. State and territory nomination availability.
5. Median salary data sourced from Jobs and Skills Australia.
6. Related courses and qualifications from training.gov.au.
7. Direct links to the relevant government source pages.

1. All occupation data is sourced from the Australian Bureau of Statistics (ABS).
2. Skilled occupation lists come from the Department of Home Affairs.
3. Salary and employment data comes from Jobs and Skills Australia.
4. State nomination data is sourced directly from each state and territory government.
5. Our automated pipeline checks for updates daily. No figure, code, course or list entry is ever AI-generated or guessed - if a government source does not publish it, we do not show it.
6. Some pages carry short written summaries of that data, generated and labelled as ImmiIQ commentary. They summarise the sourced figures; they are never presented as a government publication.

1. Go to the "SOL Lists" page from the main navigation.
2. You'll see all occupations grouped by list: MLTSSL, STSOL, ROL and CSOL.
3. Use the filter buttons at the top to show only one list at a time.
4. Click any occupation to view its full detail page.

1. Go to the "States" page from the main navigation.
2. Select a state or territory (NSW, VIC, QLD, SA, WA, TAS, NT, ACT).
3. You'll see all occupations that state currently has open for nomination.
4. Each listing shows the visa subclass, any special conditions and whether the occupation is open or closed.

1. Use the ANZSCO Version Toggle in the app header or on the search page.
2. Choose between ANZSCO v1.3, ANZSCO v2022 or OSCA v1.0 catalogues.
3. The selected version filters all occupation search results, detail pages and related data.
4. Full correspondence tables are available for cross-referencing codes between versions.

OSCA v1.0 launched December 2024 as the eventual ANZSCO replacement. Both systems are supported during the transition.

1. Go to the "Authorities" page from the main navigation.
2. Browse all 41 assessing authorities with 123 assessment pathways.
3. Each pathway shows fees, processing times, required qualifications and document requirements.
4. Click any authority to see all occupations it assesses and their specific pathway details.
5. Authority and pathway data is also shown on individual occupation pages under the Authorities tab.

1. Go to the "Labour Agreements" page from the app sidebar.
2. You’ll see a searchable database of 5,000+ Australian employers with active labour agreements.
3. Search by company name using the search bar at the top. Results filter in real time.
4. Use the Agreement Type dropdown to filter by DAMA region, ILA industry, Company Specific, GTS or Skilled Refugee Pilot agreements.
5. Use the Status dropdown to filter Active or Expired agreements.
6. Each row shows the company name, agreement type, start/end dates and active status.
7. DAMA and ILA types link to their respective occupation eligibility pages for deeper analysis.

This is essential for 482/494 sponsor checks. Verify if an employer holds an active labour agreement before advising clients on Labour Agreement stream visa applications.

1. Open any occupation detail page.
2. Scroll to the "Workforce Snapshot" section.
3. You'll see current employment level, projected 5-year growth %, median age, median weekly earnings, female share, full-time share and unemployment rate.
4. All data is sourced from Jobs and Skills Australia (JSA) and updated quarterly.
5. Use this to advise clients on demand, realistic salary expectations and career prospects.
6. The page also shows state distribution bar chart, age profile breakdown, top industries ranked, education mix and 8-10 typical tasks per occupation - all interactive.

Projected growth is shown with green (positive) or red (negative) colour coding for quick scanning.

1. Open the occupation detail page.
2. Scroll to the Workforce Snapshot section.
3. Find the 'State Distribution' chart showing percentage of workers in each state (NSW, VIC, QLD, SA, WA, TAS, NT, ACT).
4. Use this to advise clients on state nomination strategy - e.g. if 38% of software engineers work in VIC, Victoria nomination is the strongest pathway.
5. Data sourced from Jobs and Skills Australia.

Pair this with the state nomination page for each state to see which specific states sponsor this occupation.

1. Open the occupation detail page.
2. Scroll to the 'Typical Tasks' block below the description.
3. See the 8-10 specific tasks sourced from JSA - much more concrete than generic ANZSCO descriptions.
4. Useful for explaining the role to visa applicants, matching client experience to the occupation or writing nomination statements.

Tasks are verbatim from Jobs and Skills Australia's quarterly occupation profiles - authoritative and up-to-date.

1. Open any occupation detail page.
2. Find the "Qualification Pathway" section - it shows the matching AQF level.
3. You'll see the level name (e.g. "AQF Level 7 - Bachelor Degree"), typical study duration and typical qualification types.
4. Expand to read full Knowledge, Skills and Application descriptors straight from the AQF Second Edition.
5. Covers all 10 AQF levels from Certificate I through to Doctoral Degree.

Useful for explaining to clients exactly what their overseas qualification maps to in the Australian framework.

1. Go to the "EOI" page from the main navigation.
2. The dashboard holds every monthly SkillSelect snapshot ImmiIQ has imported.
3. View per-subclass cards (189, 190, 491) with queue-ahead counts and state breakdowns.
4. Use trend charts to understand how the backlog is changing over time for specific occupations.
5. Firms with the Raw EOI data add-on (A$29/month) can access EOI Raw Data for advanced search, filtering and export.

EOI backlog data helps agents advise clients on queue competitiveness and the best time to submit or update an EOI.

1. Occupation Intelligence is a premium ImmiIQ feature that scores every Australian occupation (3,230 ANZSCO and OSCA codes) on a single Opportunity Score from 0 to 100.
2. The score is an invitation-chance number built from SkillSelect and the skilled lists: how low the minimum invited points are, the invited-to-submitted rate and which skilled lists the occupation is on. Shortage, projected demand, ceilings and workforce figures sit beside it as their own columns.
3. No government body publishes this combined view. It is unique to ImmiIQ.
4. Access it inside the app at /intelligence.

The Occupation Intelligence page also has a marketing overview at /features/occupation-intelligence. Sign up for the free trial to access the full interactive dashboard.

1. The Opportunity Score (0-100) weighs three parts, each on its own 0 to 100 scale and each shown as its own sortable column, so every score can be explained.
2. Points (45%): how low the minimum invited points are in recent SkillSelect rounds. 65 points scores 100 and 100 points scores 0.
3. Rate (40%): the ratio of invitations issued to EOIs submitted - the competition gap. A higher rate scores higher.
4. List (15%): skilled-list membership, since a wider list means more visa pathways.
5. Workforce signals - shortage status, projected demand, the occupation ceiling, employment size and salary - are deliberately kept out of the score and shown as separate columns. An occupation with no EOI activity has no score rather than a zero, so it sorts last.

1. Go to /intelligence in the app. The default view is a sortable, filterable table of all 3,230 occupations with their Opportunity Score.
2. Sort by any column: Opportunity Score, minimum EOI points, shortage status, projected growth or salary.
3. Filter by visa list (MLTSSL, STSOL, ROL), shortage status (nationally or per-state), skill level, ANZSCO major group or score range.
4. Switch to Card Gallery view for a visual layout - each occupation is a card showing the score, top signals and a quick-open action.
5. Use the search bar to find a specific occupation by name or code. The table and gallery both respond to the same filters.
6. Click any row or card to open the detail drawer with the full signal breakdown for that occupation.

1. The Top Opportunity spotlight appears at the top of the /intelligence page and highlights the single highest-scoring occupation for the current filtered view.
2. It shows the occupation code and title, the overall Opportunity Score and a summary of the strongest signals driving that score.
3. Use it as a quick starting point when advising a client on which occupation gives them the best statistical chance of a visa invitation.
4. The spotlight updates dynamically as you apply filters - for example, filter to shortage-listed occupations only to see the top opportunity within that subset.

1. Lenses are pre-configured filter presets that highlight specific strategic angles across the occupation dataset.
2. Example lenses include: 'Easiest EOI invitation' (lowest recent minimum points + high invited-to-submitted rate), 'High demand, low competition' (shortage-listed + low EOI backlog), 'Growing occupations' (top 10-year projected growth) and 'High salary, high score' (above-median salary + score 70+).
3. Select a lens from the toolbar to instantly filter and re-sort the table or gallery to that view.
4. Lenses are a fast way to identify opportunities without manually configuring multiple filters.
5. You can still apply additional filters on top of a lens to narrow the results further.

Use lenses as a conversation starter with clients - e.g. show the 'High demand, low competition' lens to explain why a particular occupation pathway may be stronger right now.

1. Click any occupation row or card to open the detail drawer on the right side of the screen without leaving the table.
2. The drawer shows the Opportunity Score with a visual breakdown of each contributing signal and its individual weight.
3. You can see the exact SkillSelect data used: recent minimum points invited, number of invitations issued and the invited-to-submitted ratio for each visa subclass.
4. Shortage list status is shown nationally and for each state and territory.
5. 10-year projected employment figures and JSA workforce data (employment size, median salary) are displayed in context.
6. The DHA occupation ceiling for each skilled list is shown, giving a sense of how many invitation slots exist.
7. A direct link to the full occupation detail page (code, visa lists, assessing authorities, state nominations) is included for deeper research.

1. SkillSelect (Department of Home Affairs): EOI invitation round data including minimum points invited and invitations issued per subclass. Updated after each monthly round.
2. Jobs and Skills Australia - Occupation Shortage List: national and per-state shortage classifications. Updated annually.
3. Jobs and Skills Australia - Employment Projections: 5-year and 10-year projected employment growth by occupation. Updated annually.
4. Department of Home Affairs - occupation ceilings: the annual programmatic ceiling for each occupation on the skilled lists.
5. Jobs and Skills Australia - workforce data: current employment levels and median salaries from the latest quarterly release.
6. All data is sourced via ImmiIQ's automated pipeline from official government publications. No figure is AI-generated or estimated. Written summaries of that data are generated and labelled as ImmiIQ commentary, never as a government publication.

1. Click the chat bubble icon in the bottom-right corner of any page or navigate to /ai directly.
2. Type your question in plain English. For example: "Is 261313 eligible for a 189 visa?"
3. Harper will respond with a sourced answer, referencing the exact government data behind it.
4. You can ask follow-up questions in the same conversation for deeper analysis.

1. Visa eligibility questions: "Can a registered nurse apply for a 190 visa in NSW?"
2. Points requirements: "What points do I need for a 189 invitation as a software engineer?"
3. Occupation analysis: "What's the difference between 261313 and 261312?"
4. Pathway comparison: "Compare 189 vs 190 for accountants."
5. Document checklists: "What documents do I need for a 482 visa application?"
6. Salary and demand data: "What's the average salary for software engineers in Australia?"
7. Course finder: "What qualifications are required for 261313?"

1. Yes. When viewing a client's profile, you can ask Harper to draft an email or SMS with full client context.
2. Harper uses the client's case details, pipeline stage and history to write personalised communications.
3. AI-drafted messages include appropriate merge variables and maintain your organisation's professional tone.
4. Review and edit the draft before sending - Harper creates the starting point, you have final control.

1. Harper can generate a structured analysis of any client's case with a single click.
2. The summary includes key details: occupation match, points estimate, visa pathway options, assessment status and risk factors.
3. Case summaries are generated using RAG (Retrieval-Augmented Generation) with the client's actual data injected into the analysis.
4. Use case summaries for quick client reviews, team handoffs or as a starting point for detailed assessments.

1. Yes. Harper, the in-app AI, collects bug reports and feature requests. On the website, Nova puts you straight through to our founder on WhatsApp.
2. Describe the issue or suggestion naturally - the system will detect whether it's a bug or feature request.
3. You'll be asked for steps to reproduce (bugs) or business impact (features) and a contact email.
4. Reports are sent directly to the development team for review and follow-up.

1. Yes. Harper's answers are grounded in verified government data, not general AI knowledge.
2. The underlying data is sourced from ABS, Home Affairs and Jobs and Skills Australia.
3. Data is checked for updates daily by our automated pipeline.
4. Harper will tell you when information is uncertain or when you should consult a registered migration agent.

Harper provides information, not legal advice. Always confirm critical decisions with a Registered Migration Agent.

1. Be specific. Include the occupation name or code, visa subclass and any relevant details.
2. Mention the person's circumstances: age range, experience level, English test scores.
3. Ask one question at a time for the clearest answers.
4. Use follow-up questions to drill deeper into a topic rather than starting a new conversation.

1. Go to the "Reports" page from the app sidebar.
2. Select the report type you want to generate.
3. Configure the report parameters (e.g. select an occupation, enter client details, choose comparison criteria).
4. Click "Generate" to create the report. It will be ready to view in seconds.
5. Click "Download PDF" to save a copy or share it directly with a client.

1. Occupation Report - detailed analysis of a single ANZSCO code including lists, authorities and pathways.
2. Points Report - full breakdown of a points calculation with all categories and totals.
3. Eligibility Report - comprehensive visa eligibility assessment for a specific client.
4. Comparison Report - side-by-side comparison of two or more occupations.
5. Client Summary - overview of a client's case status, documents and timeline.
6. Financial Report - billing summary with invoices, payments and outstanding amounts.
7. Engagement Letter (CSA) - Costs Service Agreement built around the OMARA Code of Conduct, with default clauses, optional digital signing and a Certificate of Electronic Signing. Each clause is configurable per-org (see the CSA Template Editor entry below).
8. Plus 8 more specialised report types, all included in Pro.

1. Yes. Custom branding is included in Pro.
2. Go to Settings > Branding to upload your logo and set your brand colour.
3. Your logo will appear in the header of every generated PDF.
4. You can also add a custom footer with your ABN, contact details and disclaimer text.
5. Both plans also support sending outbound client email from a verified sender email domain you own, configured via DKIM, SPF and DMARC alignment.

1. Go to /clients/templates/csa from the app sidebar. You'll see the default clauses, built around the OMARA Code of Conduct, that make up every engagement letter your firm issues.
2. Click any clause to open the WYSIWYG editor and override the body text for your organisation. Your version is sanitised and stored per-tenant, so it only applies to your firm.
3. Use the toggle on each clause to control whether it gets included in the final CSA. Even mandatory clauses can be turned off - you'll see a warning so you understand the trade-off before saving.
4. The right pane shows a live preview of the assembled CSA as you edit, so you can confirm tone and flow before it goes to a client.
5. Defaults stay available behind every override. Hit Reset on a clause to restore the original ImmiIQ-supplied wording at any time.

All edits are stored as sanitised HTML scoped to your organisation. Other firms on ImmiIQ never see your wording.

1. Yes. ImmiIQ supports multi-scope engagement letters - select Skills Assessment, Visa Lodgement, Migration Review or any combination on a single CSA.
2. When you generate the engagement letter, the scope-specific clauses for each selected service are bundled into one document. You don't need to issue separate letters per service.
3. Full Service is exclusive: if you pick Full Service, the narrower scopes (Skills Assessment / Visa Lodgement / Review) are not selectable alongside it - Full Service already covers them.
4. Each scope's fee, scope description and obligations appear in their own section of the assembled CSA so the client sees exactly what each line covers.

Use multi-scope letters for end-to-end mandates - one signature covers the full engagement instead of chasing three separate signed PDFs.

1. If your firm is under the A$75,000 GST-registration threshold, open the engagement letter generator and switch GST off on the fee table.
2. With GST off, the fee table drops the GST row entirely - the subtotal becomes the total and the clause wording adapts so it no longer references GST as a separate line.
3. With GST on (the default for GST-registered firms), the table shows the subtotal, the 10% GST line and the total inclusive of GST.
4. The setting is per-letter, so if your registration status changes during the year you can flip it without rewriting the template.

Confirm your firm's GST status with your accountant - the A$75,000 threshold is set by the ATO and applies to your projected annual turnover.

1. Open the engagement letter report for a client and click "Send for Signature".
2. The client receives a magic-link email sent from your firm’s verified sender domain, plus a 6-digit access code they enter to open the signing session in their browser.
3. Inside the signing screen they review the full CSA, then sign in-browser with a signature pad (mouse, finger or stylus).
4. The signed PDF is generated with two extra pages: a "Signed Acknowledgment" page showing the signer's name, signature image and date and a "Certificate of Electronic Signing" page showing the signer's IP address, user agent, timestamp and a SHA-256 hash of the signed document.
5. Both you and the client receive the final signed PDF by email. The case file keeps the audit certificate attached for your records.

Digital signatures collected this way are legally valid under the Electronic Transactions Act 1999 (Cth). The SHA-256 hash on the Certificate of Electronic Signing lets you prove the signed PDF has not been altered since the moment of signing.

1. Navigate to the "Clients" section from the app sidebar.
2. Click the "New Client" button in the top-right corner.
3. Fill in the client's details: name, email, phone, nationality and visa subclass.
4. Click "Save" to create the client record.
5. The client will appear in your pipeline under the "Lead" stage.

1. The pipeline is a visual Kanban board showing all your clients across 7 stages.
2. The stages are: Lead, Assessment, Lodged, Additional Info, Granted, Refused and Closed.
3. Drag and drop client cards between stages as their case progresses.
4. Each stage shows a count of active clients. Click any card to open the full client detail view.
5. Pipeline changes are logged automatically in the client's activity timeline.

1. Open a client's detail page by clicking their name in the pipeline or client list.
2. Go to the "Communications" tab.
3. Click "Compose" and choose Email or SMS.
4. Write your message or select a template. Merge variables (like client name and visa subclass) are inserted automatically.
5. Click "Send" to dispatch the message. It will appear in the client's communication history.

1. Go to CRM Settings (gear icon in the CRM sidebar).
2. Click "Templates" to view your template library.
3. Click "Create Template" and choose Email or SMS.
4. Write your template using variables like {{client_name}}, {{visa_subclass}} and {{agent_name}}.
5. Save the template. It will be available when composing messages from any client's Communications tab.

System templates are provided for common scenarios like welcome emails, document requests and status updates. You can duplicate and customise them.

1. Open a client's detail page and go to the "Documents" tab.
2. Click "Upload" to add files. You can drag and drop multiple files at once.
3. Categorise each document into one of 9 categories: Passport, Skills Assessment, English Test, Qualification, Employment Reference, Financial Evidence, Health Examination, Police Clearance or Other.
4. Set expiry dates on documents like passports and English tests to receive automatic alerts before they expire.
5. Documents are stored securely with encrypted, access-controlled storage and accessible to anyone on your team with client access.

Each organisation gets 30 GB of encrypted document storage on Pro. Documents are accessible via time-limited signed URLs that expire after 1 hour.

1. Open a client's detail page and go to the "Billing" tab.
2. Click "Create Invoice" to start a new invoice.
3. Add line items with descriptions and amounts (e.g. "Migration Assessment - $500").
4. GST is auto-calculated at 10% for Australian businesses.
5. Click "Save" to create the invoice. You can then send it to the client via branded PDF email or download a PDF.

Invoices are generated as branded PDFs with your organisation's logo and details and can be emailed directly to clients.

1. Tasks are automatically created when a client moves between pipeline stages (e.g. moving to 'Lodged' creates a task to submit documents).
2. You can also create manual tasks from the client detail page or the Tasks dashboard.
3. Each task has a title, description, due date, priority level and assigned team member.
4. Task status updates are logged in the client's activity timeline.
5. View all tasks across clients from the Tasks page in the sidebar.

1. For partner or dependant visa applications, you can link related clients into a family group.
2. Open a client's detail page and look for the Family Group section.
3. Link the primary applicant with their partner and/or dependants.
4. Linked clients share case information and timeline events, making it easy to manage multi-applicant cases.

1. Record the outcome of a client's skills assessment (positive, negative or pending) in their profile.
2. Set the assessment expiry date to receive automatic alerts before the assessment expires.
3. Track which assessing authority conducted the assessment and the reference number.
4. Assessment status is visible on the client card in the pipeline for quick reference.

1. When a client moves to a new pipeline stage, the system automatically creates relevant tasks for that stage.
2. Email notifications are sent to the assigned team member when stage changes occur.
3. You can configure which notifications trigger for each stage in your organisation settings.
4. Automation saves time on repetitive admin tasks so you can focus on case strategy.

1. Select multiple clients from the client list using the checkboxes.
2. Choose a bulk action: send email, send SMS or update pipeline status.
3. For bulk email/SMS, compose a single message that gets personalised for each recipient using merge variables.
4. Bulk status updates move all selected clients to a chosen pipeline stage in one action.

1. An admin turns government forms on once for the firm at Settings > Government forms by re-typing the acknowledgement that the firm checks each filled form before it is sent. The flag is off until they do, it covers every office at the firm and the audit log records who accepted it.
2. Open a client's detail page and go to the Forms tab. Each of the eight forms ImmiIQ fills - 956, 956A, 1022, 1023, 929, 1446, 80 and 1221 - shows how many of its boxes the client's file already answers and which groups of facts are still missing.
3. Tick the forms you want and answer the questions no record can answer, such as whether a 956 makes a new appointment or ends one. They are put to you in the form's own numbering.
4. ImmiIQ fetches the Department's blank, checks the page count and every mapped field name before writing anything, fills what the file answers and leaves the rest blank. Tick more than one form and they all travel in a single signing session.
5. The client opens one email, types one PIN and signs. The signature is drawn into the form's own printed declaration box, then the Signed Acknowledgment page and Certificate of Electronic Signing are appended behind it.

No filled form has been confirmed accepted by the Department yet, so each one carries an evaluation note naming the questions it leaves blank - read the PDF before you rely on it. For a form ImmiIQ does not fill, the library at /forms keeps the blank Department PDFs, each linked to its page on immi.homeaffairs.gov.au. The Forms tab generates a per-client Reference Sheet to fill it from.

1. Open the client's detail page and go to the Intake tab. Choose Send intake pack and pick the pack for their visa - your firm's own packs are listed first, then the standard packs for subclasses 482, 408, 186, 189, 190, 491, 500, 485, partner 820 and 309 and 600.
2. Tick the partner and children who are on the application. Each gets their own identity, history and language steps. The client answers for everyone through their one portal link.
3. Name the matter if there is one. Declarations are made for one application, so the declarations steps join the pack only when it is sent against a matter.
4. The client works through the steps in the order ImmiAccount asks them, on any device. They can stop and come back. A client who stalls is reminded with a link to the step they left.
5. Answers arrive step by step on the Intake tab. Accept each step to write it into the client record - Form 956, the CSA, the government forms and eLodge read it from there.

An admin copies a standard pack at Settings > Intake packs to make it the firm's own: reorder steps, hide the ones you never ask, rename them, write your own instructions and add steps of your own questions.

1. An admin opens Settings > Intake packs and chooses Import your form, then uploads the blank Word (.docx) or PDF form, up to 10 MB.
2. The screen shows what reading it will cost and the AI credits the firm has left this month before anything is charged. Reading and matching uses 1 AI credit for every 20 questions, rounded up.
3. Each of your questions is matched to where the Department asks it. Check every match, change any that are wrong and keep anything the Department never asks as your own question.
4. Name the pack, pick its visa and confirm. It becomes one of your firm's intake packs, ready to send.

A form a client has already filled in can be imported from their Intake tab. Its answers arrive as suggestions you add section by section, an answer the client already gave is never overwritten and declarations are never imported.

1. What it does: keeps a two-way sync between your Google Workspace inbox and ImmiIQ. Incoming mail lands on the matched client's timeline automatically and outgoing messages route through your own address so replies come back to you and not to the platform.
2. Before you start: sign in as an org admin. The mailbox can be a Google Workspace account or a personal Gmail account. Workspace is recommended for firm-owned control of the connection.
3. How to connect: open Settings > Integrations at /settings/integrations, find the Gmail tile under Email and click Connect. Sign in with Google, approve the read, send and label permissions and you'll return with the tile marked Connected. Recent messages backfill within a few minutes.
4. Troubleshooting: if the tile shows Reconnect required, click it and repeat the OAuth flow. If a message does not thread against a client, add the sender's address to that client's profile and future mail will match. If sends fail with an authentication error, re-authorise. If sends fail with a rate limit error, you have likely hit Google's daily send cap for your plan.
5. When to contact support: email support@immiiq.com if OAuth returns a domain-not-allowed error (usually a Workspace admin policy) or if backfill has not started 10 minutes after connecting. Full feature detail lives at /integrations/gmail.

The connection is per-user. Each team member connects their own inbox so outgoing mail always goes out under the right name.

1. What it does: a two-way delta sync between your Outlook or Exchange Online mailbox and ImmiIQ. Incoming mail lands on the matched client's timeline and outgoing messages route through your own address so clients keep replying to you.
2. Before you start: sign in as an org admin. The mailbox must be on Microsoft 365 or Exchange Online. Personal @outlook.com and @hotmail.com accounts are not currently supported.
3. How to connect: open Settings > Integrations at /settings/integrations, find the Microsoft 365 Email tile under Email and click Connect. Sign in with your work account, approve the mail read and send permissions and you'll return with the tile marked Connected. Delta sync catches historical mail up within a few minutes.
4. Troubleshooting: if your tenant requires admin consent, forward the consent URL that appears during OAuth to your IT contact and try again once they approve. If the tile stays on Reconnect required after a password change, click it and re-authorise. If sends bounce with a policy error, check that outbound SMTP is not blocked for the account.
5. When to contact support: email support@immiiq.com if consent is blocked by a conditional access policy or if backfill has not started 10 minutes after connecting. Full feature detail lives at /integrations/microsoft-365-email.

The connection is per-user. Each team member connects their own mailbox so outgoing mail always goes out under the right name.

1. What it does: a daily backup of every client and sponsor document from ImmiIQ into a folder inside a Drive account you own. You keep the master copy of every file and can revoke access at any time.
2. Before you start: sign in as an org admin. Any Google account with enough Drive quota to hold your document library will work. A firm-owned Workspace account is recommended so the folder does not sit under a personal login.
3. How to connect: open Settings > Integrations at /settings/integrations, find the Google Drive Backup tile under Storage and click Connect. Sign in with Google and approve access to the dedicated ImmiIQ Backups folder we create at the root of your Drive. The tile flips to Connected and the first run starts on the next scheduled window.
4. Troubleshooting: if backups stop, look for a Reconnect required badge on the tile (typical after a password reset or a revoked token) and re-authorise. If a run reports a quota error, free up space in the backing Drive account and the next run will catch up. If files appear missing, open the ImmiIQ Backups folder at the root of Drive. Runs only append and never delete.
5. When to contact support: email support@immiiq.com if a run has been stuck for more than 24 hours or if you need help transferring folder ownership to a different admin. Full feature detail lives at /integrations/google-drive-backup.

The folder in Drive is yours. If you ever cancel ImmiIQ, every backed-up file stays exactly where it is under your account.

1. What it does: a daily backup of every client and sponsor document from ImmiIQ into a folder inside a OneDrive account you own. You keep the master copy of every file and can revoke access at any time.
2. Before you start: sign in as an org admin. The account should be OneDrive for Business. Personal OneDrive works but is not recommended for firm data because the folder sits under a personal login.
3. How to connect: open Settings > Integrations at /settings/integrations, find the Microsoft OneDrive Backup tile under Storage and click Connect. Sign in with your Microsoft account and approve access to the ImmiIQ Backups folder we create at the root of OneDrive. The tile flips to Connected and the first run starts on the next scheduled window.
4. Troubleshooting: if backups stall, click the tile to reconnect after any password change or admin revocation. Quota errors clear once you free space in the backing account and the next run catches up automatically. If files appear missing, open the ImmiIQ Backups folder at the root of OneDrive. Runs only append and never delete.
5. When to contact support: email support@immiiq.com if a run has been stuck for more than 24 hours or if a tenant conditional access policy blocks the token. Full feature detail lives at /integrations/onedrive-backup.

The folder in OneDrive is yours. If you ever cancel ImmiIQ, every backed-up file stays exactly where it is under your account.

1. What it does: a daily backup of every client and sponsor document from ImmiIQ into a folder inside a Dropbox account you own. You keep the master copy of every file and can revoke access at any time.
2. Before you start: sign in as an org admin. A Dropbox Business team account is recommended for firm data so the archive is not tied to one person's personal login, but an individual Dropbox account works too.
3. How to connect: open Settings > Integrations > Dropbox at /settings/integrations/dropbox and click Connect. Sign in with your Dropbox account and approve the scopes ImmiIQ asks for - account_info.read, files.metadata.write, files.content.write and files.content.read. Pick the parent folder and the hour of day the run should fire in your own timezone. The tile flips to Connected and the first run starts on the next scheduled window.
4. Troubleshooting: if backups stall, open the Dropbox settings page and reconnect after any password change or admin revocation. Quota errors clear once you free space in the backing account and the next run catches up automatically. If files appear missing, open the ImmiIQ Backup folder you nominated. In Archive mode runs only append and never delete.
5. When to contact support: email support@immiiq.com if a run has been stuck for more than 24 hours or if you need help moving the connection to a different admin account. Full feature detail lives at /integrations/dropbox-backup.

Disconnecting revokes ImmiIQ from your Dropbox linked apps immediately. Every file already backed up stays exactly where it is under your account.

1. What it does: a bring-your-own connection to your Twilio account for outbound calls, SMS and WhatsApp Business messages. Calls appear in the client timeline with the recording link when Twilio recording is enabled, SMS threads inline with the rest of communications and WhatsApp messages route through your registered WhatsApp Business sender.
2. Before you start: sign in as an org admin and open your Twilio Console in another tab. You'll need your Account SID, an Auth Token or API Key and Secret pair and at least one verified sender number for the channels you plan to use.
3. How to connect: open Settings > Integrations at /settings/integrations, find the Twilio tile under Voice and messaging and click Connect. Paste your Account SID, Auth Token and default sender number then Save. The tile flips to Connected and a test message option appears at the bottom of the form.
4. Troubleshooting: when a send fails, the tile surfaces the exact Twilio error code returned by the API. Common ones: 20003 (auth credentials rejected, rotate them in the Twilio Console), 21610 (recipient opted out) and 63016 (WhatsApp template not approved by Meta yet). Fix the underlying condition in Twilio and retry from ImmiIQ.
5. When to contact support: this integration is in beta. Email support@immiiq.com with the Twilio error code and the timestamp if a send fails without an actionable error or to request a new WhatsApp template category. Full feature detail lives at /integrations/twilio.

Beta feature. It works end-to-end today. We are still gathering feedback on the credential flow and error surfacing. Send notes to support@immiiq.com so we can prioritise fixes.

1. What it does: a bring-your-own connection to your JustCall account for VOIP calling. Calls placed from ImmiIQ ring through your JustCall number and the recording pulls into the matched client's timeline once the call ends (recording must be enabled inside JustCall for the number).
2. Before you start: sign in as an org admin. You'll need a JustCall API Key and API Secret from the JustCall dashboard under Settings > Developer.
3. How to connect: open Settings > Integrations at /settings/integrations, find the JustCall tile under Voice and click Connect. Paste your API Key and API Secret then Save. The tile flips to Connected and a Place test call button appears.
4. Troubleshooting: if the test call does not ring, check that the JustCall number selected as the default sender is provisioned for outbound calling. If recordings never land in the timeline, confirm call recording is toggled on for that number inside JustCall. If credentials are rejected, regenerate the API Secret in JustCall and paste the new value into the tile.
5. When to contact support: this integration is in beta. Email support@immiiq.com with the call SID and the timestamp if a call completes cleanly on the JustCall side but the recording never reaches the client timeline. Full feature detail lives at /integrations/justcall.

Beta feature. Please send feedback to support@immiiq.com so we can prioritise fixes and features you need in the timeline view.

1. Go to Accounting > Trust from the app sidebar (admin only). Trust accounting is an add-on (A$29/month) any plan can add in Billing.
2. Fill in the name, jurisdiction, type (general or controlled), currency, bank, BSB, the last 4 digits of the account number and, if the ledger is starting part-way, the opening balance and its date.
3. Save. The account appears on the trust landing page with its balance per currency and a Settings link.
4. Settings edits the bank details at any time; currency and opening balance can change only while the account has no entries.

A firm can run several trust accounts (one per state or a controlled account for one matter). Every entry belongs to one account, one client and one currency.

1. On Accounting > Trust use Record receipt, Pay to office, Refund or Transfer; the client's Billing tab has the same Record trust receipt button.
2. A receipt asks for the client, matter, amount, date received, payer, method and reference. On save it takes the next number in sequence (TR-000001, TR-000002 ...) and you can print or email the trust receipt straight away.
3. Pay to office settles one of the client's issued invoices from their trust balance and marks the invoice paid. Refund returns money to the client. Transfer moves money between two clients' ledgers on the same account.
4. A ledger row is never edited or deleted. To correct one, use Reverse on the ledger row, give a reason and a linked reversal row is posted. A receipt already paid out cannot be reversed.
5. A double click or a retry never posts twice - the same submit returns the row already posted.

1. In Settings > Organisation > Trust, set the dual-authorisation threshold. Any payment to office or refund at or above it needs an approved authority before it posts.
2. Go to Accounting > Trust > Authorities and Request one: client, account, amount, purpose and, for a client-signed authority, Send for client signature - the letter goes to the client's portal as a document to sign.
3. A firm approval is approved by a second administrator, never the person who requested it. Refuse records the reason.
4. The payment or refund dialog lists the client's approved authorities above the threshold; the one you pick is marked used in the same transaction as the posting.

1. Go to Accounting > Trust > Reconcile, open the account and import the bank statement CSV (CommBank, Westpac, NAB and ANZ layouts, with or without a running balance). A file already imported is refused rather than doubled.
2. Auto-match pairs each bank line with a ledger entry by amount, sign and date within five days. Match or unmatch the rest by hand - one line to one entry.
3. Start the month, type the bank closing balance (or accept the last imported running balance) and check the three-way figures: cashbook, ledger total and adjusted bank balance with unpresented receipts and payments listed.
4. Close month is enabled only with zero variance, cashbook equal to the ledger total, no unidentified bank line and a signatory - a second person when the firm requires it. The reconciliation report is generated at close and every entry in the period is stamped with it.
5. A closed month never changes and nothing can be posted into it. A daily check warns your administrators when last month is still open or a receipt has sat unbanked longer than the firm's limit.

1. Go to Accounting > Trust > Statements. For a client statement pick the client and the period, then choose Email to send it with the PDF attached and Share to portal to show it on the client's Trust tab.
2. The statement carries receipt numbers, references, payer and method, the invoice each payment settled, the account's bank details and opening and closing balances per currency.
3. The account documents - account statement, trial balance at a date, month-end pack, financial-year pack (1 July to 30 June, with a CSV) and the audit CSV of every ledger column in posting order - are administrator only.
4. Every run is recorded with who generated it, when and to whom it was emailed and can be downloaded again from the run history.

The client's Financial Summary report prints the same per-account, per-currency figures under Money Held in Trust.

1. Open the account's Settings page. Close account is enabled only when every client balance is zero, every entry is matched to a bank line and no month is in draft; until then the reasons are listed.
2. Closing sets the retention date from the firm's retention years (Settings > Organisation > Trust). The account becomes read-only, its ledger stays available for the retention period and it never reopens.

1. Document Templates lets you turn any reusable document (Costs Service Agreement, Statement of Services, sponsor letter, Genuine Student statement, ART submission) into a template whose placeholders fill from the client record.
2. Upload a PDF or DOCX you already use in your practice. The AI reads it, identifies the values that change per client (names, dates, fees, MARN, occupation, visa subclass) and converts them into reusable placeholders.
3. Then you instantiate the template per client. Placeholders auto-fill from the client record, you review the draft, render the final PDF and send for in-house e-signature.
4. There is no quota and no per-template fee. Upload as many documents as your firm reuses. Included with every Pro subscription.
5. ImmiIQ ships the AI engine and 10 starter templates built around the OMARA Code of Conduct with Pro at A$49 per month billed annually.

Visit /clients/document-templates inside the app to see your library and upload your first document.

1. From the app sidebar, open Clients then Document Templates.
2. Click "New template" and drop a PDF or DOCX (up to 10 MB) into the upload zone.
3. The AI scans the document and proposes a title, a category (Engagement, Sponsorship, Skills, Review, Compliance, Client comms) and a list of detected placeholders.
4. Review the suggestion. Accept it, rename the title, change the category or edit the placeholder names.
5. Click "Save" and the template lands in your library. It is now ready to instantiate against any client.

1. Ten starter templates built around the OMARA Code of Conduct are seeded into every new organisation on day one.
2. The starter pack covers: Costs Service Agreement (CSA), Statement of Services, Form 956 cover letter, Privacy Notice and Consent, Generic document request letter, Genuine Student statement (Subclass 500), Position description (Subclass 482 / 186), Skills assessment cover letter, AAT / ART submission cover and Status update letter.
3. Every starter uses the same placeholder engine so client data auto-fills the moment you instantiate.
4. You can clone a starter and edit it into your own house style. The original stays available as a fallback.

Open any starter template to see exactly which placeholders it uses before you build your own.

1. Open your client's detail page, go to the Documents tab and click 'New from template'.
2. Pick the template you want. The placeholders are listed with the values pre-filled from the client record.
3. Review the auto-filled values, override anything that needs adjusting (e.g. a custom fee for this engagement), then click 'Generate PDF'.
4. Send the PDF via the built-in e-signature flow: magic-link email from your verified sender domain, in-browser signature pad, signed PDF returned with a Certificate of Electronic Signing.
5. The signed document lands back in the client's Documents tab with a tamper-evident audit trail attached.

1. The 10 starter templates were drafted with input from a registered migration lawyer and follow the OMARA Code of Conduct where applicable.
2. The CSA in particular reflects the mandatory disclosure structure (Scope, Professional Fees, Refund Policy, Complaints, OMARA Registration, Privacy) that the Code requires.
3. Treat them as defensible starting points. Always review the wording against your own firm's risk position and the specific client matter before sending.
4. The 'No Guarantee' and 'Conflict of Interest' clauses on the CSA template are flagged as recommended and surface a warning if you toggle them off.

If you fork a starter and remove a clause, the override is per-org. Other firms still see the original starter wording.

1. Open the template in the editor (Clients then Document Templates then pick the template).
2. Click any placeholder badge in the document body. A side panel opens with the placeholder token (e.g. {{client_full_name}}), the field it maps to in the client record and a description.
3. Rename the token, change the mapped field or remove the placeholder if the AI got it wrong.
4. Add new placeholders by highlighting any text in the editor and clicking 'Convert to placeholder'.
5. Save the template. Future drafts use the updated placeholder structure.

Use {{snake_case}} for placeholder names. Spaces, hyphens and capitals break the substitution engine.

1. PDF (any text-based PDF up to 10 MB) and DOCX (Microsoft Word) are supported on upload.
2. Scanned PDFs without an OCR layer will not extract placeholders reliably. Run OCR first or upload the original DOCX.
3. The AI extracts both the body text and any inline tables. Headers, footers and footnotes are preserved.
4. Rendered output is always PDF, regardless of the source format. PDFs are the standard for e-signature and client delivery.

1. From the Document Templates library, click the preview icon on any template row.
2. The preview opens with sample client data filled into every placeholder so you can see the final rendered output.
3. Use the 'Test with a real client' button to instantiate the template against an actual client record without sending anything.
4. Once the preview reads correctly, you can send the real draft from the client's Documents tab.

Previews are read-only so you cannot accidentally send a test draft to a client.

1. Go to Settings > Team from the app sidebar.
2. Click "Send Invite" in the top-right corner.
3. Enter the team member's email address and select their role (Admin or Member).
4. Click "Send". They'll receive an invitation email with a link to join your organisation.
5. Once they accept, they'll appear in your team list with full access to shared clients and data.

1. Admin - full access to everything, including team management, billing, organisation settings and all CRM data.
2. Member - full access to CRM clients, reports, Harper AI and all core features. Cannot manage team members, billing or organisation settings.
3. On top of role, every member can be tightened further with three permission axes: data scope, module access and named role templates.

1. Go to Settings > Team and click Access on any member row.
2. Pick a Data Scope: "All clients" (default - sees every record), "Their team" (only clients assigned to anyone in their team) or "Assigned only" (only their own assigned clients/cases).
3. Toggle off any of ten Module Access switches: clients, cases, communications, AI, documents, invoices, reports, billing, settings, team management. Defaults follow role rules; flip a switch to block.
4. Click Save access. Restrictions take effect on the member's next request - server-side filtering, not just UI hiding.

1. Go to Settings > Team > Manage roles. Click "New role".
2. Name the role (e.g. Finance, Client Service, Operations), pick a data scope and tick the modules to block.
3. Save. Back on Settings > Team, click Access on a member, then pick the role from the Apply preset dropdown - the form fills in. Save to apply.
4. Bulk apply: select multiple members and apply the same role to all of them at once. The preset values are copied onto each member, so renaming or deleting the preset later never accidentally regrants access.

1. Go to Settings > Team > Manage teams. Click "New team", name it (e.g. Skilled Migration), pick an accent colour and optionally a team lead.
2. Set a Default role on the team if you want the team's data scope and module rules pre-applied to anyone you add.
3. Click Members on the team to add users. The "Apply default role to this user" checkbox is on by default - admins can untick to add to the team without applying the role.
4. If you later edit the team's default role, hit Sync now in the Members drawer to re-apply across every current member in one click.
5. Members assigned data scope = "Their team" can see clients/cases assigned to anyone in any of their teams - useful for pod-style firms where a small group shares case visibility but the wider firm does not.

1. Go to Settings > Team from the app sidebar.
2. Find the team member you want to remove and click their name to open their profile.
3. Click "Remove from Team" and confirm the action.
4. Their access is revoked immediately. Client data they created remains in your organisation.

1. Go to Settings > Profile from the app sidebar.
2. Click "Edit" next to your name to update it.
3. Click your avatar to upload a new profile photo.
4. Changes are saved automatically and reflected across the platform.

1. Go to Settings > Organisation from the app sidebar.
2. Edit your organisation name, website URL and contact details.
3. Upload your organisation logo (used in reports and the client portal).
4. Click "Save" to apply changes.

1. Each team member sends client email from their own address on your firm's verified sender domain - e.g. priya@your-firm.com - so clients always see the actual case officer in the From line.
2. The local-part of each user's address is derived directly from their signup email. Free-text local-parts are deliberately not allowed - this prevents impersonation (a member cannot self-assign founder@your-firm.com if they signed up as priya@your-firm.com).
3. If a team member signed up under a foreign domain (e.g. a personal Gmail), an admin sets a default local-part for them in Settings > Team > Access. That local-part is paired with your verified sender domain.
4. Admins can also set an org-level default signature (WYSIWYG) that gets appended to every outbound message from any user without their own signature configured.
5. Each member can override the org default with their own per-user signature (also WYSIWYG) from Settings > Profile - useful for individual sign-offs, MARN/legal numbers and direct phone lines.

Per-user sender identity requires your firm's domain to be verified via DKIM/SPF/DMARC. See the branding entry under Reports & PDFs for the sender-domain setup process.

1. Go to Settings > Preferences from the app sidebar.
2. Toggle email notifications on or off for different event types (new client, case updates, team invites).
3. Set your default timezone and date format.
4. Click "Save" to apply your preferences.

1. Every Pro firm can switch the platform interface to 9 languages: English, Chinese, Hindi, Arabic, Korean, Japanese, Vietnamese, Tagalog and Bengali.
2. Go to Settings > Preferences and select your preferred language from the Language dropdown.
3. The interface - navigation, labels, buttons and system text - will switch to your chosen language immediately.
4. All government data (occupation names, visa details, SOL lists) remains in English to preserve accuracy.

The multi-language interface is included in Pro.

1. Pro firms can set a default Australian state or territory in preferences. This pre-filters occupation search results and highlights your state on the nominations page.
2. Go to Settings > Preferences and select your state from the Default State/Territory dropdown.
3. Once set, occupation search results will prioritise your state's nomination data and the nominations page will highlight your state by default.
4. You can change or clear your default state at any time from the same preferences page.

Default state filtering is included in Pro. It does not hide other states - it simply pre-filters and highlights your preferred state for faster workflows.

1. Yes. The Webhooks add-on (A$19/month) sends real-time notifications to your systems when events occur - like new clients, case updates or invoice payments.
2. Go to Settings > Integrations to configure webhook endpoints and select which events to subscribe to.
3. Supported events include: client.created, client.updated, case.status_changed, invoice.paid and document.uploaded.
4. Each webhook includes a signing secret for verifying payload authenticity.
5. An admin adds Webhooks in Billing. The change is prorated and applies immediately.

Webhooks are an add-on any plan can hold, built in Billing alongside the rest of your plan.

1. Yes. Pro includes appointment booking forms that you can embed on your website alongside standard lead capture forms.
2. Booking forms include date and time selection, allowing prospective clients to schedule consultations directly.
3. Submissions flow straight into your CRM pipeline as new leads with the appointment details attached.
4. You can customise available time slots, booking duration and confirmation messages from your form settings.

Appointment booking forms come with custom branding, which is included in Pro.

1. With custom branding, included in Pro, embedded forms automatically detect and inherit your website's font family for a native look.
2. No additional CSS or configuration is required - font adaptation happens automatically when the form loads.
3. This applies to all form types: lead capture forms, appointment booking forms and search widgets.
4. If your website uses a custom web font, the form will match it as long as the font is loaded on the page.

Font adaptation is on by default and can be switched off in the form settings.

1. Firms with the Practice analytics add-on (A$29/month) get a form analytics dashboard over the last 7, 30 or 90 days showing performance metrics for all embedded forms.
2. The dashboard tracks views (how many visitors saw your form), submissions (how many completed it) and conversion rates.
3. Geographic data shows where your form visitors are located, helping you understand your audience.
4. Referrer data reveals which pages and sources drive the most form traffic.
5. Device breakdowns show the split between desktop, mobile and tablet visitors.

Form analytics comes with the Practice analytics add-on, which any plan can add in Billing.

1. Go to Settings > Integrations > Backup from the app sidebar.
2. Pick a destination tile: Google Drive, Microsoft OneDrive, Dropbox or Customer S3 bucket (also covers Cloudflare R2, Backblaze B2, Wasabi and MinIO via the endpoint override).
3. For Google Drive / OneDrive / Dropbox, click Connect - you'll be redirected to Google, Microsoft or Dropbox to authorise. ImmiIQ only requests the scopes it needs to write into the folder we create, so we can only see our own backup tree.
4. For S3, paste your bucket name, region and access keys. We issue a HeadBucket test with the credentials before saving anything.
5. Pick the backup mode: Archive (append-only - deletes in ImmiIQ never touch the destination copy) or Mirror (deletes propagate within about 15 minutes). Default is Archive.
6. Pick the hour of day the backup runs, in your own timezone. The scheduler converts to UTC on save.
7. Accept the shared liability block on the consent screen - once files land on the storage account you connect, its access policy is your responsibility.
8. Once connected, the tile shows the account/bucket, mode, hour, last-run summary and a Disconnect button. Files land under `Clients/<name>/<category>/` and `Sponsors/<name>/<category>/`.

Included on every Pro plan. Your ImmiIQ-hosted copy stays encrypted with our per-organisation key regardless - the destination copy is a second, plaintext copy you control.

1. Go to Settings > Integrations from the app sidebar.
2. Pick the tile for the tool you want to connect (Gmail, Microsoft 365 mail, Twilio, JustCall, Xero, QuickBooks, S3 backup, Stripe) and click Connect.
3. Read the shared-responsibility disclaimer inside the consent modal and tick the acknowledgement box - consent copy is version-stamped so any change re-prompts admins.
4. Follow the provider's OAuth prompt or paste the required API credentials into the inline form. Credentials are sealed with your organisation's per-tenant encryption key before they touch the vault.
5. Once the tile turns green you are connected. Use Manage to review scopes or Disconnect to revoke access in one click.

Every connect, disconnect and credential rotation writes an audit row on your organisation for compliance review.

1. Go to Settings > Integrations > Gmail or Microsoft 365 mail.
2. Complete the provider consent screen with the mailbox you want ImmiIQ to sync.
3. Reply from ImmiIQ or from your mailbox - both surfaces stay in sync from that point.
4. Add alternate email addresses to a client record to catch replies from personal, work or secondary domains.
5. Historic backfill covers the last 90 days automatically; new messages appear on the client timeline within about a minute.

Provider-sent mail leaves via your own Gmail or Microsoft 365 account and never touches the ImmiIQ monthly email quota. Only the fallback path (no mailbox connected) counts against the limit.

1. Go to Settings > Integrations, pick JustCall or Twilio Voice, click Connect.
2. Paste your API credentials (JustCall API key + secret or Twilio Account SID + Auth Token; any firm can add a Subaccount SID for tenant isolation).
3. Copy the ImmiIQ webhook URL shown on the connection card and paste it into your provider's voice webhook settings.
4. Pick a default caller ID from your Twilio or JustCall numbers and tick Record every call if you want dual-recording.
5. Reload the app. The softphone pill appears bottom-right; click any phone number on a client detail page to place a call or hit Cmd+Shift+D to open the dialpad.

Recordings are re-encrypted with your per-organisation key before they hit ImmiIQ storage and streamed through 5-minute signed URLs, so cross-org playback is architecturally impossible.

1. In the Twilio Console go to Messaging > Senders and register your WhatsApp Business sender.
2. In ImmiIQ, go to Settings > Integrations > Twilio and click Connect.
3. Paste your Account SID and Auth Token, pick your Messaging Service SID and pick your WhatsApp Business sender.
4. Open any client record and click Send WhatsApp Business.
5. Reply freeform if the client has messaged in within 24 hours; otherwise pick a Meta-approved template from the library grouped by utility, marketing or authentication.

Meta's 24-hour session-window rule is enforced server-side. WhatsApp Business is metered on your Twilio account and does not count against the ImmiIQ SMS quota.

1. Archive (recommended): append-only. Files land on your destination on the daily schedule and stay there even if you delete them in ImmiIQ. Best for firms that want a safety net against accidental deletes and a permanent second copy for OMARA / firm record-keeping.
2. Mirror: the destination reflects live state. If you delete a file in ImmiIQ, the corresponding copy on your Drive / OneDrive / Dropbox / S3 gets deleted within about 15 minutes on the next drain cycle. Best for firms that want the destination to always match what's in ImmiIQ.
3. You can flip modes at any time from Settings > Integrations > Backup - the change is audit-logged. Archive → Mirror stops propagating deletes from that moment (files already on the destination stay). Mirror → Archive starts propagating them from that moment (previous history remains).

If you're unsure, keep Archive - it's the safer answer to 'what happens if a team member deletes the wrong file in ImmiIQ?'

1. Open Network > Colleges from the sidebar and click 'Add college'.
2. Enter the CRICOS provider code (e.g. 00123A). The importer prefills the provider name, legal entity, campuses and course catalogue from the government CRICOS dataset.
3. Confirm the campus list, then pick the primary contact for commission statements. This is the address statements are emailed to and the person you can @-mention on enrollment records.
4. Set the default commission agreement: base rate, payable-on trigger (enrolment / start / retention window) and any per-course overrides. You can edit this later from Network > Colleges > Agreements.
5. Click 'Save college'. The college now appears in the enrollment picker across every client record.

If the CRICOS code returns nothing, the provider is likely an RTO. Switch the 'Provider type' toggle to RTO and enter the RTO code instead - the same pipeline importer covers both.

1. Open the client record, scroll to the 'Enrollments' block and click 'Record enrollment'.
2. Pick the college from the searchable dropdown. Campus and course lists filter to that college's live CRICOS catalogue.
3. Choose the course. Duration, tuition and CRICOS course code populate automatically.
4. Enter the start date and the amount invoiced by the college. Commission is calculated from the college's active agreement and shown inline.
5. Save. The enrollment feeds Network > Ageing so you can watch payable dates approach and Network > Statements so incoming reconciliation matches on this row.

1. Go to Network > Colleges > pick a college > Agreements tab.
2. Set the base rate as a percentage of tuition invoiced (e.g. 20%) or as a fixed dollar amount per enrollment.
3. Add segments for exceptions: postgraduate courses at a different rate, direct-enrolment vs referral or a bonus band above a volume threshold. Segments stack in order and the first match wins.
4. Set clawback terms: the retention window (usually 12 or 24 weeks), whether the clawback is full or pro-rated by weeks completed and whether it passes through to your sub-agent partner if one was credited.
5. Save. The next enrollment recorded against this college uses the new agreement automatically. Historical enrollments keep the agreement version they were created under.

1. Download the monthly statement from the college portal as a CSV.
2. Go to Network > Statements and click 'Upload statement'.
3. Drop the CSV. The reconciler previews the mapping: student name, course code, invoice amount, commission amount and paid date columns.
4. Confirm the mapping (it remembers per-college). ImmiIQ auto-matches each line to an open enrollment on student name plus course plus start date, with a confidence score.
5. Review the auto-matches. Green rows match exactly, amber rows need a manual pick, red rows have no candidate. Click through any row to accept, edit or split-match.
6. Post the statement. Matched enrollments update to 'commission received', partner shares are queued and any variance between expected and received commission is flagged for follow-up.

Statement imports are idempotent. Re-uploading the same CSV does not double-post - the reconciler dedupes on the college + statement-period key.

1. From 1 March 2026, education providers cannot pay commission to an agent on a student who transfers to a new provider while onshore in Australia, if the transfer happens inside the first 6 months of the student's principal course.
2. The Network module enforces this at three points:
3. 1. On enrollment record: if the student's most recent enrollment shows an onshore transfer inside the guard window, ImmiIQ flags the new enrollment as 'commission ineligible' before you save it.
4. 2. On statement reconciliation: any inbound statement line that would post commission to a flagged enrollment is held for review with the rule reason attached.
5. 3. On partner payout: partner shares for flagged enrollments are excluded from the next Stripe Connect Transfer run.
6. You can override an individual flag if the transfer meets an exemption (e.g. provider default, student welfare). Overrides are logged for audit with reason and timestamp.

Keep the guard on by default. The rule sits inside the National Code and non-compliance risks provider registration - the audit trail matters if a regulator asks.

1. Open Network > Partners and click 'Invite partner'.
2. Enter the partner's business name, primary contact email and the commission share percentage they earn on referrals they source.
3. Choose their portal scope: view own referrals only or view own referrals plus statement status. Partners never see other partners' data or your firm's full CRM.
4. Send the invite. The partner gets a magic-link email into the sub-agent portal - no password to set up, no separate account.
5. The partner accepts, sets a display name and can start entering referrals or watch existing ones you attributed to them.

You can revoke a partner's portal access from Network > Partners > [partner] > Access. The Stripe Connect linkage stays intact so historical payouts remain traceable.

1. Partners sign in via magic link at the portal URL. Every session is single-device and audit-logged the same way as agent sign-ins.
2. Landing view: their commission balance, upcoming payable dates and a searchable list of every enrollment they were credited on.
3. Each enrollment row shows the college, course, start date, invoice amount and their share (net of any clawback pass-through). They can drill in to see the reconciliation status - matched, pending statement or paid.
4. Partners can submit new referrals from the portal. Referrals arrive in your Network > Referrals inbox where an agent claims one, opens the CRM record and converts it to a real client.
5. Partners cannot see other partners, cannot see client PII beyond their own referrals and cannot see your firm's college-agreement rates.

1. In the sub-agent portal, the partner clicks 'Connect Stripe' and completes Stripe's hosted onboarding. Their Stripe account is now linked to your firm's platform.
2. When commission from a college statement is posted and partner shares fall due, ImmiIQ queues a payout run. Go to Network > Payouts to review.
3. The payout run groups all cleared commissions per partner. Preview the total, the enrollments included and any withholding for pending clawbacks.
4. Click 'Run payouts'. Each partner receives a Stripe Connect Transfer from your platform balance to their connected account. Zero platform fee - the money moves directly.
5. Every transfer is receipted in the partner portal and in your Network ledger. Reversal is one click if a clawback comes in later.

Stripe Connect Transfer uses the same infrastructure ImmiIQ already uses for client card payments. Your existing Stripe account is the only one you need.

1. If a college claws back commission because the student withdrew inside the retention window, that money leaves your ledger.
2. If a sub-agent partner was credited on the enrollment, the pass-through setting on the college agreement decides whether the partner also loses their share, at what ratio and on what schedule.
3. Full pass-through means the partner refunds their share in full. Pro-rated pass-through means the refund is proportional to the weeks not completed.
4. ImmiIQ handles the mechanics: it creates a negative ledger entry against the partner, holds it against their next commission payout and if the balance is still negative at month-end it issues a Stripe Connect payment request.
5. The partner sees every clawback event in their portal with the source enrollment, the withdrawal reason and the refund amount so there is no dispute over what happened.

Set pass-through terms up front in the partner agreement. Retrofitting clawback rules after the fact is where partner relationships break down.

1. Yes. Open Settings > Integrations > External storage backup. You will see four connect tiles side by side: Google Drive, Microsoft OneDrive, Dropbox and Customer S3 (AWS, Cloudflare R2, Backblaze B2, Wasabi or self-hosted MinIO via the endpoint override).
2. Pick one and complete the blocking consent modal - it asks you to pick Archive (safer, deletes on ImmiIQ never touch the destination) or Mirror (destination reflects live state and mirrors deletes within about 15 minutes), pick your daily backup hour in your local timezone (we convert to UTC on save) and read the shared-liability disclaimer.
3. Tick the acceptance checkbox and click Connect. Google Drive, OneDrive and Dropbox redirect through OAuth; S3 opens a credentials form that runs a HeadBucket test before saving.
4. Once connected you get one card showing the destination, mode, backup hour, last-scan timestamp and the count of queued / succeeded / failed rows this week. You can flip mode, shift the hour or disconnect from that page any time.
5. Files land in a folder tree: `ImmiIQ Backup / Clients / {Lastname Firstname (ID N)} / {category} / {YYYY-MM-DD}_{filename}` for client docs, `ImmiIQ Backup / Sponsors / ...` for sponsor docs.
6. Your ImmiIQ-hosted copy stays encrypted with our per-organisation key regardless. The destination copy is plaintext - that is the point of an off-platform backup - and how the destination is configured (folder sharing, bucket policy, MFA) is entirely your responsibility. The consent modal spells this out.

Restore is one-way in v1 - you pull files from your destination yourself if you ever need to. Archive mode keeps deleted files on the destination as a safety net; Mirror mode does not.

1. Xero is live. Open Settings > Integrations > Xero and click 'Connect Xero'. You are redirected into Xero's OAuth consent screen where you pick the organisation to connect and authorise the ImmiIQ scopes (contacts, invoices, bills, accounts).
2. After consent, Xero returns you to ImmiIQ and the connection status flips to Connected. The org name, tenant ID and connected-by user are shown so multi-org firms can see exactly which Xero file is wired.
3. The connection uses refresh tokens so re-auth is only needed if you revoke access from Xero's side or the token is idle for 60+ days.
4. Disconnect at any time from the same page. Disconnection stops future sync but leaves already-synced invoices in Xero untouched.

You need a Xero user role with permission to create invoices, bills and contacts (Standard or Adviser). Read-only Xero users cannot complete the OAuth grant.

1. When you raise an invoice in ImmiIQ (client billing tab or sponsor billing tab), the invoice is pushed to Xero as a draft sales invoice against the mapped contact.
2. When you record a payment against an invoice in ImmiIQ, the payment is pushed to Xero and the invoice status flips to Paid on both sides.
3. When an invoice is paid inside Xero (bank feed reconciliation, manual mark-as-paid), the paid status is pulled back into ImmiIQ within 15 minutes and posted to the client's invoice timeline as 'Reconciled in Xero'.
4. Void or delete an invoice in either system and the other side flips to Void with the reason attached.
5. Sync direction is symmetric so whichever system your bookkeeper works in stays the source of truth for that invoice's lifecycle.

1. Open /settings/integrations/xero/mapping. The page lists every ImmiIQ revenue category (professional fees, disbursements, government fees, sponsorship fees, education commission, refunds) plus every custom category your firm has added.
2. For each category, pick the Xero account code from the dropdown. The dropdown is populated live from your connected Xero file so you always see the current chart of accounts.
3. Set a default tax rate per mapping (GST on Income, GST Free Income, BAS Excluded). The mapping is applied on every push so BAS-time reconciliation stays clean.
4. Save. Changes take effect for future syncs; historical invoices keep the account code they were pushed under.
5. The page also lets you set the default 'Branding Theme' - the Xero-side invoice template that gets applied on push.

If you add a new revenue category in ImmiIQ, an amber banner appears on the mapping page until you assign it a Xero account. Unmapped categories block push until you resolve them.

1. On first invoice push, ImmiIQ looks up the client (or sponsor or partner) in Xero by email address first, then by legal name.
2. Exact match: the invoice is pushed against the existing Xero contact.
3. No match: a new Xero contact is created with the ImmiIQ-side name, email, ABN (where held), primary address and phone. The Xero ContactID is stored on the ImmiIQ record so subsequent syncs skip the lookup.
4. Fuzzy match (name-similar but email different): the invoice is held with an amber flag on the client's billing tab so you can pick 'Use existing Xero contact', 'Create new' or 'Skip'.
5. Delete a contact in Xero and the next sync recreates it - the ImmiIQ record retains the historical ContactID for audit.

1. Every invoice on ImmiIQ has an activity timeline showing the full lifecycle: created, sent, viewed, paid, refunded.
2. Xero events are auto-reconciled onto the same timeline with a Xero badge so it is obvious which side the action came from.
3. Events include: pushed to Xero (with the Xero invoice number), viewed by contact in Xero, marked paid in Xero, voided in Xero, refunded in Xero.
4. Each event carries a deep-link to the Xero-side invoice so you can jump straight into the source-of-truth record with one click.
5. The timeline is the single audit trail regardless of which system a bookkeeper worked in.

1. Record a refund in ImmiIQ (client billing tab > invoice > Refund) and the refund is pushed to Xero as a credit note against the original invoice.
2. The credit note is applied to the invoice automatically so the paid balance reduces to the net amount received.
3. Record a credit note in Xero and the credit is pulled back into ImmiIQ as a refund event on the invoice timeline.
4. Partial refunds are supported both directions - the amount is applied against the specific invoice line, not the whole invoice.
5. Refunds fully reverse the revenue attribution and MRR calculations, so your Analytics > Revenue attribution numbers stay honest on refund.

Refunds on trust-account transactions must be recorded through Accounting > Trust > Refund, not the invoice refund. Trust refunds sync to Xero as bank transfer entries not credit notes to preserve the segregation your regulator expects.

1. Open Analytics > Cohorts. Contacts are grouped by the month they first signed up (or were captured on a form).
2. The retention grid shows what percentage of each cohort remained active month-on-month for the following 12 months.
3. 'Active' is defined per your firm - default is any client status change, invoice, message or portal login within the month.
4. Hover any cell for the raw counts (active / total in cohort) and a link to the underlying contact list for that month.
5. Use it to see whether a specific onboarding change, seasonal intake or pricing tier improved retention over baseline.

Cohorts are exclusive - a contact belongs to exactly one signup month, so the diagonal always adds up cleanly.

1. Open Analytics > Funnel. The funnel shows conversion count and rate across your CRM pipeline stages: Lead > Assessment > Lodged > Additional Info > Granted.
2. For every stage transition, the funnel also shows the median number of days a client spent in the upstream stage before advancing.
3. Filter by date range, RMA owner, source (form / referral / import) or visa subclass to isolate a segment.
4. Click any stage bar to open the list of clients currently in that stage - ranked by days in stage descending.
5. Compare two date ranges side by side to see whether a workflow change improved conversion or shortened cycle time.

Median (not mean) is used deliberately - a single outlier case that sat in Assessment for 400 days would skew the mean and hide the real cadence.

1. Open Analytics > Bottlenecks. The view ranks every current open case by how long it has been sitting in its current stage.
2. The top rows are your worst offenders - cases that have been in one stage far above the median for that stage.
3. Each row shows the client, the current stage, days in stage, the median for that stage across your firm and the RMA owner.
4. Click any row to open the client detail page and see the pipeline history so you know exactly when it stalled.
5. Set a firm-wide alert threshold (e.g. any case > 30 days in Assessment) and the bottleneck view will email the assigned RMA when a case crosses it.

1. Open Analytics > Sponsor billing. The tab shows invoice volume, paid vs outstanding and average time-to-pay across every sponsor account.
2. Group by sponsor, by RMA or by month. Each grouping keeps the same three-metric layout so comparisons stay honest.
3. The outstanding-invoice list ranks sponsors with the largest overdue balance first - the collections priority queue in one view.
4. 'Hidden from sponsor' invoices are counted in the totals but are visually marked so you can spot how much of your revenue is internal-only.
5. Export the underlying invoice list as CSV for reconciliation with your general ledger.

1. Open Analytics > Revenue attribution. The report attributes every paid invoice to the source that brought the client in and the RMA who owned the case.
2. Sources are captured from the original contact record: website enquiry form (with UTM breakdown), referral partner, cold list, manual entry, sub-agent portal.
3. Toggle between 'by source' and 'by RMA' views. The stacked bar chart shows revenue over time; the table underneath shows totals, client count and revenue per client.
4. Filter by date range and visa subclass to isolate a market segment.
5. Attribution is fixed at the client level so a client's lifetime revenue always accrues to their original source and their currently assigned RMA.

If you reassign a case mid-flight, revenue attribution follows the new RMA from that point forward. Historical invoices stay with the original owner.

1. Open Analytics > Harper cost. The tab shows every Harper AI query grouped by RMA, by case and by query type (chat, case summary, email draft, document extraction).
2. For each grouping you see total queries, total token spend and the running dollar cost against your plan's Harper allowance.
3. The daily and monthly time series shows spend trend against the plan cap so you can see when you are heading for the ceiling before you hit it.
4. Click any RMA row to drill into their query log - useful for spotting a case that is triggering an unusual amount of AI usage.
5. Firms with extra branches see a cost overview across every branch for centralised billing.

Harper pauses at your plan's AI allowance unless an AI pack is added in Billing. The cost tab shows how close you are before you reach it.

1. Analytics has seven tabs: Clients, Sponsors, Revenue, Harper, Cohort, Funnel and Bottleneck.
2. The six chart tabs (Sponsors, Revenue, Harper, Cohort, Funnel and Bottleneck) each carry two buttons: 'Export CSV' and 'Export PNG'.
3. CSV export downloads the tab's data table, ready for a spreadsheet.
4. PNG export downloads a snapshot of the tab at twice the pixel density, ready to paste into a report or a slide.
5. The Clients tab exports its client and invoice reports as CSV.
6. PNG snapshots are rendered in your browser, so the analytics data never goes to an outside image service.

1. The Convert Hub is a suite of file utilities at /convert built for migration workflows: bundling exhibits, fixing rotation, hitting portal size caps, cropping passport photos and stamping signatures.
2. Every tool has its own page at /convert/<slug> with SEO metadata, an FAQ and a shareable link.
3. All processing happens in your browser. Files never leave your device.
4. There is no signup and no quota - the pages are free and public.

All processing happens in your browser. Files never leave your device.

1. Drop any number of JPG, PNG or WEBP images and download a single combined PDF.
2. Page order matches the order you drop them in.
3. Useful for bundling passport pages, payslips, evidence exhibits into one lodgement-ready PDF.
4. 50 MB per image. All processing happens in your browser. Files never leave your device.

1. Renders every page of a PDF to a 200 DPI PNG and downloads them as a ZIP.
2. Useful when a portal only accepts images, not PDFs.
3. Password-protected PDFs must be unlocked first (see Remove PDF Password).
4. All processing happens in your browser. Files never leave your device.

1. Drag in two or more PDFs and download a single merged file. Page order matches the order you arrange them.
2. Stitch separate exhibits - bank statements, employer letters, tax returns - into one lodgement bundle.
3. Originals on disk are untouched; the tool builds a fresh PDF and downloads it.
4. All processing happens in your browser. Files never leave your device.

1. Pick a page range (e.g. 1-3, 5, 7-9) and download a new PDF with only those pages.
2. Useful for redacting sensitive pages or extracting a single exhibit from a long bundle.
3. Extracts one range per run. To split into N separate files, run it N times.
4. All processing happens in your browser. Files never leave your device.

1. Rotate every page 90°, 180° or 270°. Fixes sideways phone scans in one click.
2. Rotation is a metadata flag on each page so output size is within a few bytes of the input.
3. Works on scans and text-based PDFs alike.
4. All processing happens in your browser. Files never leave your device.

1. Stamp DRAFT, CONFIDENTIAL, a client name or any custom text diagonally across every page.
2. Customise opacity and rotation. Watermark is embedded as page content.
3. Useful for marking internal drafts so a review copy cannot be mistaken for a lodged bundle.
4. All processing happens in your browser. Files never leave your device.

1. Stamp 'Page X of Y' footers on every page for clean exhibit referencing.
2. Position, font size and starting number are configurable.
3. Useful for tribunal and assessing-authority bundles where exhibits are referenced by page.
4. All processing happens in your browser. Files never leave your device.

1. Shrink a JPG, PNG or WEBP photo to fit the visa-portal 5 MB cap.
2. Targets the size you set and re-encodes with an in-browser quality search.
3. EXIF metadata is stripped by default so GPS coordinates do not leak in exhibits.
4. All processing happens in your browser. Files never leave your device.

1. Crop, resize and export a passport-spec photo at 35 x 45 mm ready for DHA online lodgement.
2. Outputs a print-ready 600 DPI JPG at the correct aspect ratio.
3. DHA reserves discretion at lodgement - the tool covers the technical checks but photo quality (background, lighting, expression) is on you.
4. All processing happens in your browser. Files never leave your device.

1. iPhones save photos as HEIC by default; lodgement portals only accept JPG or PNG.
2. Drop your HEIC files and download JPGs at 92% quality - visually identical, portal-compatible.
3. Runs on a WebAssembly decoder inside your browser tab.
4. All processing happens in your browser. Files never leave your device.

1. Add AES-256 password protection to a PDF before emailing it to a client or counterparty.
2. The password is used in-browser to derive the encryption key and then discarded - it is not stored anywhere.
3. If you forget the password, the PDF cannot be recovered.
4. All processing happens in your browser. Files never leave your device.

1. Enter the open-password and download an unprotected copy of a PDF you legitimately have the key to.
2. This tool decrypts using the password you provide - it does not crack or guess.
3. The password and the file stay inside your browser tab.
4. All processing happens in your browser. Files never leave your device.

1. Shrink an oversized PDF to fit the 5 MB lodgement cap.
2. Embedded raster images are re-encoded at lower quality; vector text stays untouched so it remains sharp.
3. Typically 50-70% size reduction on scan-heavy PDFs with no visible loss.
4. All processing happens in your browser. Files never leave your device.

1. Draw your signature (mouse or touchscreen), pick a page and position and download a stamped PDF.
2. Toggle on the audit trail to record a SHA-256 hash of the signed file - useful for proving integrity later.
3. For statutorily-binding e-signatures use the in-app CSA signing flow inside ImmiIQ instead.
4. All processing happens in your browser. Files never leave your device.

1. Open a PDF and add text boxes, highlight passages, white-out content, draw shapes, place images or signatures.
2. Reorder or delete pages from the thumbnail sidebar before exporting.
3. Text edits use a whiteout-and-retype overlay so the original layout is preserved (substitute font: Helvetica).
4. Rendering uses pdf.js and saving uses pdf-lib - both run entirely in your browser tab.
5. All processing happens in your browser. Files never leave your device.

1. Open Sponsors > Portal access from the sidebar and click 'Invite HR contact'.
2. Enter the HR contact's full name, email and the sponsoring entity they act for. Pick 'Owner' or 'HR member' for their portal role.
3. Send the invite. The HR contact receives a magic-link email plus a 6-digit access code - no password to set up.
4. They click the link, enter the code and land on their private sponsor portal scoped to that sponsor's records only.
5. From that point every nominee, obligation and document sits on their portal alongside your RMA-side view.

Invites are single-use. If the HR contact loses the email, revoke and re-send from Sponsors > Portal access > [contact].

1. Open the sponsor detail page and go to the Roster tab.
2. Click 'Import CSV' and download the sample template if you need the header shape.
3. Required columns: given_name, family_name, date_of_birth, passport_number, nationality, visa_subclass, position_title, occupation_code.
4. Optional columns: passport_expiry, visa_expiry, health_exam_date, character_check_date, salary_aud, start_date.
5. Drop the CSV. The importer previews each row, flags duplicates against existing nominees and shows any missing required columns before you commit.
6. Post the import. Each nominee lands as its own record on the roster and starts the expiries clock the moment dates are set.

The importer is idempotent on passport_number - re-running the same CSV updates matching rows instead of creating duplicates.

1. Open Sponsors > Expiries. The dashboard shows every nominee grouped by the next expiring artefact.
2. Four columns: passport expiry, visa expiry, health examination expiry and character check expiry.
3. Each column sorts nominees by days remaining with amber (30 days) and red (7 days) chips for quick triage.
4. Click any nominee to open their profile with the exact expiring document, source of truth and renewal checklist.
5. Filter by sponsor, visa subclass or country to focus the view. The dashboard is shared with the HR contact on the sponsor portal.

1. From the sidebar open Sponsors > New and click 'Upload SBS approval PDF' at the top of the form.
2. Drop the Standard Business Sponsorship approval letter. Harper reads the PDF and extracts sponsor legal name, ACN, ABN, approval date, expiry date, occupations approved and nominee cap.
3. The extracted values pre-fill every field on the /sponsors/new form. Review, correct anything that needs adjusting and save.
4. The sponsor record is created with the SBS approval attached to the documents tab as the source-of-truth artefact.
5. Autofill runs in-browser with the PDF and the extracted values held under your organisation - the SBS letter is never shared beyond your tenant.

Scanned SBS letters without an OCR layer will not autofill reliably. Use the Convert Hub 'OCR PDF' workaround or upload a text-native copy.

1. Sponsor obligations (record-keeping, salary payment, cooperation with DHA monitoring) sit on a timeline against each sponsor.
2. When an obligation deadline approaches, the platform fires nudge emails to both the RMA and the HR contact.
3. The tiers are 30 days, 14 days, 7 days and 1 day before the deadline. Each tier escalates the subject line and the CTA urgency.
4. Nudges include the deadline, the obligation reference (e.g. 482 sponsor record-keeping under s.140K) and a direct link to the sponsor's obligation tab.
5. Snooze or complete an obligation from the sponsor timeline to stop further nudges on that item.

Tier cadence is fixed to align with OMARA's expected sponsor-monitoring cycle. Missing a nudge is not a defence if DHA audits.

1. Every Monday at 08:00 AEST the platform emails a weekly digest to opted-in HR contacts summarising the sponsor's status.
2. The digest covers upcoming expiries, obligation deadlines in the next 30 days, new nominees added, invoices raised and messages awaiting reply.
3. HR contacts opt in from their sponsor portal under Notifications > Weekly digest. Opt-out is one click on any digest email.
4. RMAs get a mirror copy so both sides start the week on the same page.
5. The digest is empty-state aware - if there is nothing to report that week, no email is sent.

1. Open the sponsor detail page and go to the Billing tab. It shows every invoice raised for that sponsor with status, amount and payment history.
2. Each invoice has a 'Hidden from sponsor' toggle. When on, the invoice stays in your RMA-side view but disappears from the HR contact's portal.
3. Use it for internal charges you route through the sponsor account but do not want the HR contact to see (e.g. a partner-firm referral fee, an interim retainer).
4. The toggle is per-invoice and reversible. Flipping it does not send a notification either way.
5. The audit log records who flipped the toggle and when so there is a defensible trail.

Aggregate revenue reporting counts hidden invoices - only the sponsor portal view is filtered. Your MRR numbers stay honest.

1. Open the sponsor detail page and go to the Messages tab. It is a single threaded conversation shared between the RMA (you) and the HR contact.
2. Post a message. The HR contact sees it on their portal and receives an email nudge if they have not read it within 4 hours.
3. Attachments live inline in the thread and count against your firm's document storage cap.
4. Messages are timestamped and read-receipted so both sides know when the last reply landed.
5. Every message is stored under the sponsor's audit trail alongside document uploads and obligation actions.

The thread is scoped per sponsor. Do not use it for individual-nominee correspondence - that belongs on the nominee's own communications tab.

1. ImmiIQ supports two base roles: Admin and Member. Admins manage team, billing and org settings; members do not.
2. Layered on top, each member has three independent permission axes that admins can tighten any time without changing the underlying role:
3. 1. Data scope: all clients (default), their team's clients only or their assigned clients only. The filter applies at the database layer - direct API calls return the same restricted set the user sees in the UI.
4. 2. Module access: ten per-member switches (clients, cases, communications, AI, documents, invoices, reports, billing, settings, team management). A blocked module disappears from the sidebar and the API.
5. 3. Role templates: named presets (Finance, Client Service, Operations) that bundle scope + modules. Bulk-apply across the team. Saved as snapshots, not live bindings - deleting a preset later never accidentally regrants access.
6. Sub-teams group members for the "Their team" scope and can carry a default role that applies on add.
7. Single-session enforcement ensures each user can only be logged in on one device at a time for security.

1. Pro (A$79/month or A$49/month billed annually - save 38%): 1,000 clients, 1,000 Harper AI queries/mo, 5,000 emails/mo, 100 SMS/mo, 30 GB storage, 5 team seats and 123 features - full CRM, custom branding, branded reports and invoices, verified sender domain, ImmiAccount eLodgement with the eLodge Chrome extension (Australian firms, admin opt-in), bulk import and export, booked consultations on your own meeting link and email support. Meetings inside ImmiIQ are the ImmiIQ Live add-on.
2. Enterprise: everything in Pro, with the add-ons and packs your firm picks, built by an admin in Billing with every price shown live. Packs raise each allowance to the top of its ladder: Clients up to 25,000, AI queries a month up to 5,000, Emails a month up to 100,000, SMS a month up to 5,000, Storage up to 500 GB, Team seats up to 100. The Enterprise name grants nothing on its own - a firm pays for what it adds.
3. Add-ons on any plan, each a line on your existing subscription: Additional branch at A$19/month per extra branch; Sponsor Portal at A$29/month; Social Studio at A$29/month for 300 branded posts a month; Call notes at A$39/month; ImmiIQ Live Meetings (per agent) at A$59/month per agent (everything unlimited for the agent: meetings of up to 10, team meetings of up to 25, audio notes, transcripts, minutes and video recording); ImmiIQ Live Webinars at A$59/month (webinars and programs of up to 500 attendees, 10 webinar hours a month; needs one Meetings seat); ImmiIQ Live Large at A$149/month (in place of Webinars: up to 5,000 viewers, 30 webinar hours a month); Trust accounting at A$29/month; Accounting at A$29/month (includes both the Xero and the QuickBooks sync); Webhooks at A$19/month; Practice analytics at A$29/month; Raw EOI data at A$29/month; Priority support at A$49/month. Colleges and Partners are free on Pro - an admin switches them on.
4. Pro starts with a 7-day free trial. No credit card required.
5. A feature your plan does not include is locked, not hidden: its page renders with three sentences on what it does and one button to buy it, switch it on or ask us for it.

1. Each plan includes usage limits for AI queries, email sends, SMS sends and storage.
2. Usage is tracked in real time and visible on your dashboard.
3. When you approach a limit, you'll receive a notification. Hitting a limit does not delete data - it pauses that feature until the next billing cycle.
4. To raise a limit, an admin adds a pack in Billing. The change is prorated and applies immediately.

1. All data is encrypted in transit (TLS 1.3) and at rest.
2. Document storage is encrypted and access-controlled with time-limited signed URLs that expire after 1 hour.
3. Organisation-level data isolation ensures your clients' data is completely separated from other organisations.
4. Passwordless magic link authentication eliminates password-related vulnerabilities.
5. AI features use anonymised data (age brackets, not dates of birth) to protect client privacy.
6. Bot protection on every sign-in page prevents automated attacks on authentication endpoints.

1. The platform interface supports 9 languages: English, Chinese, Hindi, Arabic, Korean, Japanese, Vietnamese, Tagalog and Bengali.
2. The multi-language interface is included in Pro.
3. Change your language in Settings > Preferences. The switch takes effect immediately.
4. All government data (occupation names, visa details, SOL lists) remains in English to preserve accuracy.

1. All payments are processed securely through a PCI-compliant card processor - your card number, CVV and full card details never touch ImmiIQ servers.
2. Go to Settings > Billing to view your current plan, usage and payment history.
3. Click 'Manage Subscription' to access the secure billing portal where you can update your card, change plans or download invoices.
4. Annual subscriptions are billed as a single payment of A$588/year (equivalent to A$49/month - save 38% vs A$948/yr monthly).