Most immigration consultancies have a website and a CRM, and no connection between them. The website collects an enquiry, emails it to an inbox, and somebody retypes it into the CRM an hour later — or a day later, or never. Every step in that chain loses information, and the leak is invisible because nobody sees what never arrived.
This guide covers what a properly connected website looks like, what the enquiry form must capture, and the specific mistakes that quietly cost consultancies their best leads.
What "connected" actually means
A connected website does not email you an enquiry. It writes the enquiry directly into the CRM as a record, then notifies you. The difference matters more than it sounds:
- Nothing is retyped, so nothing is mistyped. Phone numbers survive intact — and a wrong digit in a phone number is a lost client.
- The enquiry exists whether or not anyone reads the email. Inboxes fail. Records do not.
- It arrives with a source attached, so you can tell which channel produced it.
- The clock starts immediately. Assignment and follow-up reminders fire from the moment it lands, not from when someone notices.
If your form only sends mail, everything downstream depends on a human checking an inbox on a busy day. That is not a system.
What the enquiry form must capture
Long forms lose people. Short forms lose information. For immigration work the balance sits at about five fields:
- Name and phone number, with the country code. Make the country code explicit rather than hoping people include it. Most of your follow-up will be by phone or WhatsApp, and a number you cannot dial is a dead record.
- Email. Secondary for contact, essential for matching duplicates later.
- Destination country or service. One dropdown. This is what routes the enquiry to the right counsellor.
- A free-text box. People explain their situation in ways no dropdown anticipates, and that text is often what tells you whether the case is worth pursuing.
- Consent. A clear checkbox for being contacted, stored with the record and a timestamp.
Resist adding passport numbers, dates of birth or document uploads to a public form. That belongs behind a login, in a client portal, after the person becomes a client. Asking for it upfront both scares people off and creates a data-protection problem you did not need.
Capture the source, or you are spending blind
The single most valuable field on a connected form is the one the visitor never sees: where they came from.
Your website knows whether someone arrived from a Google ad, an organic search, Facebook, a JustDial listing or a partner's referral link. Passing that into the CRM as a hidden field takes minutes to set up and answers the question every consultancy argues about: which channel actually produces paying clients, not just enquiries.
Tag your campaign links with UTM parameters, store them with the enquiry, and after three months you will know that one channel produces twice the enquiries and half the conversions. That single fact usually changes where the marketing budget goes. Pair it with visitor tracking inside the CRM and you can also see which pages a lead read before they filled the form — often the pricing page, which tells the counsellor exactly how to open the call.
The email trap that catches almost everyone
Two specific configuration mistakes account for most "we never received the enquiry" incidents.
The form sends as the visitor. Many contact forms set the From address to whatever the visitor typed. That means your server is sending mail claiming to be from gmail.com, which fails Gmail's authentication checks and lands in spam. Always send from your own domain and put the visitor's address in Reply-To. If your enquiry notifications go missing, this is usually why — our guide on business emails going to spam covers the fix in detail.
Notifications go to one person's inbox. When that person is on leave, enquiries pile up unseen. Notifications should go to a shared address and, more importantly, should be a convenience rather than the actual delivery mechanism. The record must already be in the CRM.
Speed decides who wins the client
Immigration is a considered purchase, but the shortlist forms fast. Someone researching a study visa fills in three or four consultancy forms in an evening. The one that responds first has an enormous advantage — not because they are better, but because they are the only one the person has actually spoken to.
A connected website makes this achievable without anyone watching a screen:
- An automatic acknowledgement to the enquirer within seconds, from your domain, with your branding.
- Immediate assignment to a counsellor by destination country or round-robin, so nobody has to allocate it manually.
- A follow-up task created automatically, with a due time, so an unworked enquiry becomes visible rather than forgotten.
- An alert to the assigned counsellor on the channel they actually watch.
None of that requires anyone to be at a desk. It requires the enquiry to be a record rather than an email.
WhatsApp, handled properly
Most Indian consultancies get more first contacts on WhatsApp than through any form, and no amount of website design changes that. What you can change is whether those conversations leave a trace.
Use click-to-chat links on your website with a pre-filled message that identifies the page — "Hi, I'm enquiring about the Canada study visa page". The counsellor then knows what the person was reading before they typed. Log the enquiry in the CRM at first reply, not at the end of the conversation, so the record exists even if the chat goes cold.
The realistic split is conversation on WhatsApp, records in the CRM. Trying to force clients into a portal for messaging fails; capturing what happened does not.
Deduplicate on phone number, not name
The same person will enquire twice — once from a Facebook ad, once from your website a month later. Names are spelled inconsistently across scripts and staff, so match on phone number instead. It is close to unique, and it prevents the situation where two counsellors call the same lead about the same case, which looks disorganised to exactly the person you are trying to impress.
The connected-website checklist
- The form writes to the CRM database, not only to an inbox.
- Phone numbers are captured with a country code.
- A hidden source field records where the visitor came from.
- Notification mail sends from your domain, with the visitor in Reply-To.
- The enquirer gets an automatic branded acknowledgement.
- The enquiry is assigned and given a follow-up task on arrival.
- WhatsApp links pre-fill a message naming the page.
- Duplicates are matched by phone number.
- No sensitive documents are requested on a public form.
- Consent is stored with the record and a timestamp.
If you are building or rebuilding a site, connect it to the CRM from the start — retrofitting a form into a case system afterwards is always more work than doing it once. We do both sides: website design and development and the InfraBit Immigration CRM the enquiries land in. If you are still choosing a platform, our guide to the best immigration CRM for consultants covers what to look for.
Frequently asked questions
How do I connect my website enquiry form to my CRM?
The form should write directly into the CRM's database rather than only sending an email, either through the CRM's own form endpoint or an API call that creates the enquiry record. Email notification is then a convenience on top, not the delivery method. The practical test: switch off your email for a day, submit a test enquiry, and check whether the record still exists in the CRM. If it does not, the form is not connected.
What fields should an immigration enquiry form have?
Name, phone number with country code, email, destination country or service, a free-text box for the person's situation, and a consent checkbox. That is enough to route and qualify the enquiry without losing people to a long form. Do not ask for passport numbers, dates of birth or document uploads on a public page — collect those behind a client portal login after the person becomes a client.
Why do enquiries from my website go to spam?
Usually because the form sends mail with the visitor's address in the From field, so your server appears to be forging their domain and fails authentication. Send from your own domain and put the visitor in Reply-To. Missing SPF, DKIM or DMARC records on your domain cause the same result and are worth checking at the same time.
Should I track where each enquiry came from?
Yes, and it costs almost nothing. A hidden field storing the referring source or UTM campaign, saved with the enquiry, tells you which channels produce clients rather than just leads. Consultancies routinely find that their highest-volume source has the lowest conversion rate, which changes where the budget goes.
How quickly should we respond to a website enquiry?
Within minutes if you can. People researching visas submit several consultancy forms in one sitting, and the firm that makes contact first is usually the only one they have actually spoken to. An automatic acknowledgement plus immediate assignment and a timed follow-up task gets you most of that advantage without anyone watching a screen.