Migration Agent Website Intake Forms: Ask Enough to Help, Not Enough to Lose the Lead

What the first form should do

The first form has three jobs: identify the person, understand the broad reason for contact, and create a clear next action. Useful fields can include name, email/phone, broad visa/service category, current location/time zone, a short description and urgency where relevant.

Capture the marketing source automatically where possible rather than asking the client “how did you hear about us?” and then relying on inconsistent free text.

What can wait until pre-consult intake

More detailed immigration history, employment chronology, family/dependent information, prior refusals, document uploads and other sensitive information can often wait until the person is booking or preparing for a consultation.

That staged approach reduces friction and supports data minimisation.

Use conditional questions

If a person chooses employer sponsorship, show employer/sponsorship questions. If they choose partner/family, show relevant relationship context. Do not make every prospect scroll through every question for every practice area.

Conditional forms are easier for the client and produce cleaner structured data for the agent.

Connect the form directly to the CRM

The submission should create a contact/opportunity, source, timestamp and next action automatically. Staff should not have to copy the email into another system before anyone can respond.

If the person books a consultation, keep the original enquiry linked to the booking rather than creating a second duplicate contact.

Give clients confidence about data handling

On the form itself, confidence comes from three small things: a sentence saying who is collecting the information and why, the practice’s name and a registered agent’s MARN beside the submit button (the Code requires the MARN on the business website, s25), and not asking for anything the next step does not need. The OAIC’s APP 3 guidance recommends a data-minimisation approach; on a form, that simply means every field should earn its place.

The wider intake process, from first form to consult notes, is covered in our guide to the migration agent client intake process.

Hosted form vs embedded widget

A hosted booking or intake page is easiest to deploy and maintain. An embedded widget keeps the experience visually inside the agent’s own website. Either can work if the underlying data flows into the same private practice CRM.

Whichever you choose, check that the provider does not require access to your website or server administration just to run the form, and that you can export the submissions if you change systems.

Should the intake form ask which visa subclass the client needs?

You can ask for a broad category or the subclass they believe applies, but do not assume the client already knows the correct pathway. Include an “unsure” option.

Should a website form request passport scans?

Only if genuinely needed at that stage and the upload process is appropriately secure. Most first-touch enquiry forms can work without identity-document uploads.

Can I embed an intake form without changing my website hosting?

Yes. A hosted widget or iframe/script can usually be embedded in common website builders while the software provider hosts the underlying application.