Migration Agent Client Intake: How to Collect Better Information Before the Consultation

Stage 1: capture enough to route the enquiry

The first form should establish who the person is, how to contact them, the broad reason they are seeking help, their location/time zone and any urgency that affects scheduling. It should not try to replicate a full visa application.

The commercial objective is simple: get the enquiry into a pipeline quickly with enough information to send it to the right person and invite the next step.

Stage 2: pre-consult intake

Once a consultation is being booked, the practice can ask more structured questions relevant to the likely service area. Examples include current visa/status context, broad visa history, occupation/employment context, family composition where relevant, prior refusals or cancellations, and the outcome the person is trying to achieve.

The benefit is not automated eligibility advice. It is better preparation: the agent can see the shape of the matter before the call and spend paid consultation time on the issues that require professional judgment.

Where intake meets the Code of Conduct

Intake is also where two Code obligations start. If the first consultation runs without a service agreement (allowed under s43 of the Migration Agents Code of Conduct Regulations), the person must be told your MARN, the fee must be reasonable, and you must issue a receipt. And once the consultation happens, what you advise orally has to be recorded contemporaneously (s55) and kept on the client file (s56, 7 years).

Practically, that means the intake record and the consult notes should end up in the same place as the eventual client file, rather than in a CRM nobody exports from.

Stage 3: preserve changes instead of overwriting them

Migration matters frequently evolve. Clients remember a previous refusal, correct an employment date, add a dependent, produce a different passport spelling, or clarify information they originally summarised inaccurately.

A system that simply replaces the old answer loses context. A stronger CRM records the current value and an audit history: what changed, when and who changed it. That makes it easier for the agent to reconcile information before it propagates into forms and documents.

Reduce duplicate entry

The same basic facts often appear in several places: enquiry forms, booking forms, consultation notes, service agreements and later matter records. Re-keying creates admin and transcription risk.

The intake system should capture structured fields once and make them available to the next stage. This is one of the practical reasons CRM and practice-management integration matters more than a long feature checklist.

Privacy and data minimisation

Migration intake can involve highly personal information. Australian Privacy Principle guidance from the OAIC emphasises that collection should be limited to personal information reasonably necessary for the organisation’s functions and activities, with higher standards around sensitive information. The OAIC’s APP 3 guidance recommends taking a data-minimisation approach.

That argues against collecting every possible sensitive detail at the first anonymous website touch. Ask for what is necessary at each stage, explain why it is being collected, and move more sensitive questions into an appropriate secure context.

A practical intake scorecard

Measure whether the process works rather than whether the form looks comprehensive. Useful measures include form completion rate, time from enquiry to booked consultation, percentage of consultations with completed intake, number of repeated/basic questions agents still have to ask, number of post-intake corrections, and conversion from completed intake to paid consultation.

If a shorter staged form increases completed consultations while still giving agents enough context, it is doing more useful work than a perfect 60-field questionnaire nobody finishes.

How long should a migration-agent intake form be?

There is no universal ideal. Start with the minimum fields needed to route the enquiry, then collect visa-specific detail before the consultation. Measure completion and agent usefulness rather than chasing a fixed field count.

Should clients upload documents before the first consultation?

Only where the practice genuinely needs them and has an appropriate secure process. For many enquiries, structured facts are enough before the first call; document requests can come later.

Should an intake system score visa eligibility automatically?

That is a different and higher-risk function. A CRM can organise and flag missing information without pretending to replace the registered agent’s professional assessment.