Lead capture integrations

A lead form builder that publishes without a web developer

The lead form builder in DigiPix Flow lets your sales or marketing team design an enquiry form inside the CRM, decide which lead field every answer fills, and publish it as its own page or as a snippet for your site. Edit it later and the change reaches every place the form is used.

  • Built in the CRM, published in a click
  • Each answer saved where it belongs on the lead
  • One form, shared as a link or embedded
An example of the DigiPix Flow Leads page as a website enquiry arrives. Priya Sharma sends the Kitchen consultation form embedded on a kitchen company's website and appears as a new lead tagged Embedded. Her campaign tags, Google click ID, landing page and consent are saved with the lead, the spam and duplicate checks pass, assignment rules give the lead to Kavya Iyer, and the form's SMS auto-reply is queued to her phone number.
field types to build a form from
12
fields a single form can hold
40
lines of code for the hosted page
0

What you set on every form

  • Ready-made fieldsName, email, phone, company, message, consent
  • Field rulesRequired, lengths, limits and patterns
  • Choices from the CRMYour lead sources and tags as options
  • Lead mappingWhich lead field each answer fills
  • Consent boxPurpose, channels and the notice
  • Publish stateDraft until you say it is ready
THE PROBLEM

Why enquiry forms built outside the CRM fall short

See how it's fixed
  1. Every form change waits for the website team

    Marketing wants a budget question added before Saturday's campaign. The form lives in the website's code, the agency that built it replies on Tuesday, and the campaign runs with the old form, collecting answers nobody can use.

  2. Answers that arrive as one long paragraph

    A generic contact form emails a block of text: name, phone, city and requirement run together. Someone retypes it into a sheet, fields get swapped, a digit in the mobile number goes missing and the lead is unreachable before anyone has called it.

  3. A campaign with no form to send people to

    The Instagram post is ready and the WhatsApp broadcast is drafted, but there is no page to collect replies. So enquiries come back as DMs, screenshots and missed calls, and half of them never reach the CRM at all.

BUILD THE FORM

Start from ready-made fields, then shape the rest

Open a new form and add the fields that decide whether a lead is usable: name, email, phone, company, a message box and a consent tick. Each ready-made field is already set up and pointed at the right lead field. Then add your own questions from twelve field types, put them in order with the up and down buttons, and check the preview beside the builder as you go.

  • Six ready-made fields, each removed from the menu once used
  • Twelve types, from short text to multiple choice
  • Up to 40 fields, reordered with up and down buttons
  • A preview of the form shown beside the builder
An example of a DigiPix Flow website form's protection settings: published as an embedded form, with the hosted page and signed server-to-server options beside it, a honeypot field, a per-IP rate limit and Cloudflare Turnstile switched on, and the UTM tags, Google and Facebook click IDs and referring page saved with every lead.
FIELD RULES

Rules on every field, checked twice

Give each field a label, placeholder and help text, mark it required or optional, and set the limits that make an answer usable: a minimum and maximum length, a range for numbers, or a pattern such as a six-digit PIN code. The form checks the answers in the browser before sending them, and the server checks them again when they arrive. The builder also refuses a form that could never become a lead, such as one where name, email and phone are all optional.

  • Required or optional, with placeholder and help text
  • Length limits, number ranges and custom patterns
  • At least one of name, email or phone must be required
  • The same rules enforced again on the server
An example of adding a lead custom field in DigiPix Flow: the field Budget (₹) with the nine field types to choose from — text, long text, number, date, select, checkbox, URL, email and phone — with Number selected, and a value check that accepts 45,00,000 and rejects the words forty five lakh because the field must be a number.
WHERE ANSWERS GO

Every answer lands in the right lead field

For each question, choose the lead field its answer fills: lead name, first or last name, email, phone, company, message, lead source or tags. Anything you leave unmapped is still kept with the submission. Dropdowns can take their choices from your own lead sources or tags, read fresh each time the form loads, so renaming a source in the CRM changes the form without republishing it.

  • Nine lead fields an answer can be saved into
  • Unmapped answers kept with the submission
  • Dropdown choices taken from your lead sources or tags
  • A renamed source shows on the form without republishing
An example of lead sources in DigiPix Flow's CRM masters: Website, Meta Lead Ads, Property expo, Site hoarding, Walk-in as the default and an inactive Newspaper insert, each with its code and lead count; Hoarding has been renamed Site hoarding and its 214 leads updated, and a website form and a Meta form are each set to one of these sources.
DRAFT AND PUBLISH

Hosted lead capture forms that go out when you say so

A new form starts as a draft, so you can build and check it before anyone sees it. Publish it and its link and snippet start accepting entries; unpublish it and they stop until you publish again. The hosted page needs nothing from your website: it shows the form's name as the page title, sits in a single card sized for a phone, and follows the visitor's light or dark setting. Or paste one script tag into a page you already have.

  • Drafts accept nothing until published
  • Unpublish to pause a form without deleting it
  • A hosted page sized for phones, kept out of search results
  • One script tag for your own site, carrying only the form key
Explore website forms
An example of a DigiPix Flow lead record's source and consent: the lead came from a website home-loan form with its own custom source, its UTM tags, Google click ID and landing page are saved, and consent was granted on 16 September 2026 at 10:42 IST, with the notice shown first and the box not pre-ticked, recorded in the consent history.
AFTER SUBMIT

From a filled-in form to a lead with an owner

Each entry joins the same intake as every other source: it is compared with the leads you already have, a likely duplicate is flagged for a person to review, and your assignment and scoring rules pick an owner. Per form, you can switch on a Cloudflare Turnstile check using your own keys, and an SMS auto-reply from a published template that goes once to each new lead with a phone number.

  • Duplicate checks and assignment rules on every entry
  • Cloudflare Turnstile, switched on form by form
  • An optional SMS auto-reply from a published template
  • No text to numbers on your do-not-contact list
Explore duplicate management
An example of DigiPix Flow's assignment rules: four rules run in order — weighted by source, least loaded by score, fixed by tag and round robin by segment — with a round-robin fallback when no rule matches, a follow-up task created on assignment, and a new lead just assigned by the first rule.
HOW IT WORKS

From a blank form to a published one, in five steps

  1. STEP 01

    Add the fields

    Start with the ready-made ones, then add your own questions in the order you want.

  2. STEP 02

    Set the rules

    Mark what is required, add limits and point each answer at a lead field.

  3. STEP 03

    Add consent

    Choose the purpose and channels, and write the notice that sits above the box.

  4. STEP 04

    Publish

    Share the hosted link or paste the snippet once the draft looks right.

  5. STEP 05

    Follow up

    Each entry becomes a lead, checked for duplicates and handed to its owner.

THE DIFFERENCE

The CRM form builder vs a generic contact form

What it coversA generic contact form that emails your teamDigiPix Flow
Changing a questionA request to whoever built the websiteAn edit in the CRM, shown wherever the form is used
What an entry looks likeOne block of text in an emailTyped answers saved into named lead fields
Bad answersWhatever the visitor typed, uncheckedLengths, ranges and patterns checked twice
Dropdown choicesCopied by hand and soon out of dateRead from your lead sources and tags
ConsentA ticked box nobody can traceA notice, a purpose and channels on record
A campaign with no website pageReplies scattered across DMs and callsA hosted page with its own link
Pausing a formDelete it and rebuild it laterUnpublish, then publish again when ready

Lead form builder questions, answered

What is a lead form builder?

A lead form builder is a tool for designing an enquiry form, choosing its questions and rules, and publishing it so that every entry becomes a lead. In DigiPix Flow the builder sits inside the CRM, so each answer is saved straight into the lead record rather than arriving by email.

How is this different from the website forms page?

It is the same forms feature seen from the other end. This page is about building a form in the CRM and publishing it with no developer. The website forms page covers the routes in detail: the embed, the hosted link, signed posts from your own server, campaign tracking and spam checks.

Do I need a website to collect leads with it?

No. Every published form has a hosted page with its own link, which you can share in a WhatsApp message, a social bio, an email or a QR code. If you do have a site, the same form can also be placed on any page with one script tag.

Can I change a form after it is published?

Yes. The hosted page and the embed both load the form from DigiPix Flow each time they open, so an edit appears everywhere the form is used without re-pasting anything. To stop entries for a while, unpublish the form; its links answer again once you publish it.

Which field types can I use?

Short text, long text, email, phone, number, date, website address, dropdown, single choice, multiple choice, checkbox and consent checkbox. A form can have up to 40 fields, and a choice field up to 200 options, typed in or read from your lead sources or tags.

Where do the answers end up?

In the lead fields you chose: lead name, first and last name, email, phone, company, message, lead source or tags. Answers you did not map are kept with the submission. Answers are not saved into custom fields.

Can I change how the hosted page looks?

Not beyond the form itself. The hosted page shows your form's name and fields on a clean card that follows the visitor's light or dark setting. There is no theme, logo or colour setting, and it is not a landing-page tool.

Can a form send people a confirmation?

Yes, by SMS. Switch on the auto-reply for a form and choose a published SMS template; each new lead that left a phone number gets one text after it has been assigned. Numbers on your do-not-contact list are skipped, and there is no email auto-reply.

Who can see a form before it is published?

Only your team, inside DigiPix Flow. A draft form's link and snippet accept nothing, so you can build, preview and correct it before a single visitor reaches it.

Something we haven't covered? Talk to an expert

Build the enquiry form your next campaign needs

Talk to an expert — bring the questions you ask every new enquiry, and see them become a published form in DigiPix Flow.

  • A real person, not a bot
  • Bring your current questions
  • See your form published
Talk to an expert