From your website to an agent’s queue in seconds

Most enquiry forms end in an inbox. The visitor types their number, presses Send, and a notification lands in a shared mailbox that somebody checks after lunch. By then the person has enquired with two other companies, and one of them rang back within the hour. The form was never the problem — the distance between the form and a phone was.

Lead capture forms in LumaKol close that distance. A submission becomes a lead in your workspace immediately, with its source recorded, its stage set, its tags applied and an owner assigned, so it appears in an agent’s queue on their phone rather than in a mailbox. This post covers how the two connection methods work, what to put on the form, how assignment behaves, what happens when the same person submits twice, and the anti-spam measures that sit underneath all of it.

Two ways to connect

You can use either method, or both at once, and they feed the same queue.

The hosted page

Every form you create gets its own page with a readable address. You choose the headline, the introduction, the fields, the consent line under the button and what the visitor sees after they submit — either a short confirmation message or a redirect to a page of your own, such as a thank-you page or a brochure download. Nothing needs to be installed and nobody needs to touch your website. The link works in a WhatsApp message, an Instagram bio, a QR code on a hoarding, a print advertisement or an email signature. For teams without a developer to hand, this is the fastest route: create the form, copy the link, start collecting.

The embeddable endpoint

If you already have a form that matches your site’s design, you do not have to replace it. Each form also carries a token and a submit endpoint, and your existing form can POST to it directly. The response tells you whether the submission was accepted, and carries back the success message or the redirect URL you configured, so your own page can decide what to show. Validation errors come back named by field, which means your form can highlight the number that failed instead of showing a generic failure.

Because an open endpoint is an open endpoint, you can restrict a form to a list of allowed origins. A submission from a site that is not on the list is refused. If a token ever leaks — pasted into a public repository, left in an old page template — you can rotate it in the app, which invalidates the old one immediately without deleting the form or losing the leads it already produced.

What to ask for, and what to leave out

The form supports ten fields: name, phone, email, company, city, state, designation, address, postal code and notes. You choose which appear, what each is labelled in your own words, and which are required. A form can carry up to ten fields in total.

The temptation is to use all of them. Resist it. Every field you add is another reason to abandon the form, and most of what you want to know is answered in ninety seconds on the call anyway. The only field the system insists on is the phone number, because without it there is nothing to call — and a calling CRM with a lead it cannot ring is just an expensive contact list.

A sensible default for most enquiry-driven businesses is three fields — name, phone, and one question that helps the agent open the call. You can always add a field later; you cannot recover the person who gave up on field seven.

Who picks it up

A lead that belongs to nobody gets called by nobody. Each form carries an assignment rule, chosen when you create it and changeable at any time.

• Unassigned — the lead lands in the shared pool for a manager or a duty agent to distribute. Useful when volume is low and irregular, or when a human should look at the enquiry before it is handed out. It is the option that most needs a habit behind it: someone has to actually open the pool.
• One person — every submission goes to the same agent. This is the right choice for a form behind a specific campaign, a single branch, or a landing page owned by one salesperson.
• Round-robin — submissions are shared out in turn across the people you nominate. Nobody is starved of leads and nobody quietly accumulates a backlog. This is what most teams want for a general website enquiry form.

Assignment is per form, not per workspace, so a Hindi-language landing page can round-robin across your Hindi-speaking agents while the dealer enquiry form goes to one person, without any rule-writing. You can also set the pipeline stage a form’s leads start in — a walk-in booking form might start further along than a cold newsletter enquiry.

When the same person submits twice

People resubmit forms constantly. They are not sure the first one went through, they think of something they forgot to mention, they come back a fortnight later after seeing your advertisement again. Handled badly, this is how a CRM ends up with the same buyer as three leads assigned to three agents, all ringing the same number on the same afternoon.

LumaKol matches a submission against the existing leads in your workspace by phone number. If the number is already there, no second lead is created. Instead, a note is added to the existing lead recording that they submitted the form again, along with whatever they wrote in the notes field this time. The lead keeps its owner, its stage and its history, and the agent who already knows the file sees the new message rather than a colleague starting from scratch.

The form’s own counters separate the two cases, so you can see genuinely new leads and repeat submissions as different numbers rather than one flattered total.

Keeping the rubbish out

Any form that is reachable from the open internet will be found by automated submitters. Two measures run on every submission, and neither of them asks your visitors to prove they are human.

The first is a honeypot: a field that is present in the markup but invisible to a person, and therefore left empty by every real visitor. A bot that fills in every field it finds will fill this one too. When it does, the submission is quietly accepted and discarded — the bot is thanked and ignored. Returning an error would only teach whoever wrote it what to avoid next time.

The second is a rate limit per address per form: a burst of submissions from the same source in a short window stops being accepted. A family sharing an office connection will never reach it; a script hammering the endpoint will, within seconds.

Neither measure is a CAPTCHA, deliberately. CAPTCHAs cost you real leads — particularly on older phones and slow connections, which in many markets is most of your leads — to stop traffic that a honeypot and a rate limit already handle.

Tag the source, or your reports lie to you

Each form sets a source label and can apply tags to every lead it creates. This sounds like housekeeping. It is the difference between a report you can act on and a report you can only look at.

Give each form its own source: the site contact form, the pricing page enquiry, the Diwali campaign landing page, the QR code at the exhibition stand. Then your channel comparison is real. You can see which form brings volume, which brings leads that connect, which brings leads that reach a site visit or a demo, and which quietly produces wrong numbers all month. Without distinct sources, every one of those channels is filed as “web form” and the only honest thing you can say about your marketing is that some of it works.