Online Lead Forms: Fields, Arabic, Phone and CRM Setup

What makes an online form work for sales?

A form works for sales when people finish it and the lead reaches one named owner in the CRM without anyone retyping it. Lead capture usually breaks at one of those two points, so check both before you spend more on ads.

These are the failures to look for on a form you already run:

It asks for details that nobody in sales ever reads.
It looks right in English on a laptop and falls apart in Arabic on a phone.
It rejects a valid number because the customer typed 05 where the form expected +966.
Submissions land in a shared mailbox, and everyone assumes someone else replied.
Meta leads wait in Ads Manager until a person remembers to download them.

Which fields should a lead form ask for?

Ask only for what your first sales conversation or your routing needs, because everything else can wait for that conversation. GOV.UK's guidance for public services puts the test simply: know why you are asking every question. For each field, name the person who uses the answer and what they do with it. If you cannot name them, cut the field.

The starting set below is our judgment for a quote or demo request, so adjust it to your sale:

Full name in one field. W3C suggests a single field where possible because it accepts names as people write them, and Arabic names do not always split neatly into first and last.
Mobile number, if your team follows up by call or WhatsApp.
One qualifying question as a dropdown, such as the product of interest or the nearest branch. Pick the question that decides who handles the lead.
Company name, if you sell to businesses.
Email, if you actually use it or your CRM relies on it to match records.
An optional message box for people who want to explain more. Nielsen Norman Group advises keeping optional fields to one or two and labeling them clearly.

How long should a lead form be?

Keep it as short as your sales team can accept. The evidence supports that direction better than it supports any exact number, and most of it does not come from lead forms:

Live lead form test: MECLABS, MarketingSherpa's parent company, emailed about 300,000 people in 2013. The short form with one offer converted 58%, the short form with a choice of offers converted 57%, and the same choice plus a job title field converted 51%. That last version was 11.9% below the control at 99% confidence. The team warned that some recipients knew about the test and that the tabbed layout may have added friction.
Form analytics: Zuko's benchmark shows a negative relationship between the number of questions and completion rate. It is a correlation, and the page gives no sample size.
Ecommerce checkouts: Baymard Institute counted an average of 11.3 fields in 2024, says most sites need only 8, and argues that field count affects usability far more than step count. Those shoppers have already decided to buy, which a person answering an ad may not have.
Surveys: a randomized 2025 study of 4,000 Austrian households compared 182 and 274 questions. The shorter version had a 38% response rate against 34%, with comparable data quality. The effect was small, and these surveys are far longer than any lead form.
Expert advice: Nielsen Norman Group recommends keeping forms short and reports cutting one of its own from six fields to two. That article is from 2016 and is advice, so it does not measure lead quality.

How should you decide on length for your own form?

Decide with your own numbers, starting from three to five fields. That starting point is our judgment and no study we read establishes it. Add a field when its answer changes who handles the lead or how they respond. A buyer who was referred to you and wants a detailed quote will probably put up with more questions than someone who tapped an ad a minute ago.

We found no independent controlled study that measured both form completions and qualified leads afterward, so the claim that longer forms bring better leads remains unproven. Measure it yourself: change one thing, then compare completed forms and qualified leads per 100 visitors. If a longer form needs more questions, split it into steps with the easy questions first. That is also judgment, though it fits Baymard's checkout finding that fields matter more than steps.

How do you build an Arabic right-to-left form that works?

Set the whole page to right-to-left and then test it with real Arabic typing on a phone, because translated labels alone leave the layout wrong. W3C's guidance gives your developer the rules: put dir=rtl on the html tag, avoid CSS for base direction, and use start and end in the style sheet in place of left and right so the layout mirrors. For free-text fields, dir=auto sets the direction from the first strong character typed. W3C notes this is not foolproof, since a mostly English line that begins with an Arabic word will be treated as right-to-left.

The rest of this list is practical advice from us:

Translate every string a customer sees, including error messages, the submit button, the thank-you message and any confirmation email.
Keep email, website and phone fields left-to-right, since their content reads that way even on an Arabic page.
Save Arabic and English dropdown answers to the same CRM value. Otherwise الرياض and Riyadh become two cities in your reports.
Write the Arabic yourself or have a native speaker review it. A machine-translated form makes a poor first impression on a buyer you paid to reach.
Test on an iPhone and an Android phone with an Arabic keyboard, then test again with the form embedded in your real website, since the host page can affect the layout.

How should the phone number field work?

Use one field that accepts whatever people type, checks the number, and stores it with the country code. GOV.UK's pattern says to let people use a familiar format with spaces, hyphens, brackets and country codes, to validate the number, and to avoid input masks. On the web, type=tel brings up a phone keypad on many mobile browsers, as MDN notes, though it checks no format, and GOV.UK advises autocomplete=tel so browsers can fill the number in.

Google's libphonenumber library, which GOV.UK suggests for validation, lists all three countries with 00 as the international prefix and 0 as the national prefix. So your form should expect the same number written several ways:

Saudi Arabia (+966): 0512345678, +966512345678 or 00966512345678.
Jordan (+962): 0790123456, +962790123456 or 00962790123456.
Iraq (+964): 07912345678, +9647912345678 or 009647912345678.
Arabic digits such as ٠٥١٢٣٤٥٦٧٨. The libphonenumber FAQ says the library can read native digits, so convert them before you save the number.
Valid does not mean reachable. The same FAQ warns against treating validation as proof that a number is assigned or in service. A code sent to the phone proves more, but it adds a step, so we would keep it for forms with a real fake-number problem.

Who should be notified when a form comes in?

Alert one named owner right away, and give that alert enough detail to act on from a phone. What follows is our practical advice. The research on response speed is in our guide on how to manage and qualify leads, and it is the reason to write your target down.

Route by a rule the form can answer, such as product or city, or rotate leads across a named group.
Put the name, number, answers, source and a link to the CRM record in the alert, so the owner can call without opening anything else.
Decide who covers evenings, weekends and leave, and name a second person for leads left untouched.
Tell the customer what happens next on the thank-you message: who will contact them, by which channel, and roughly when. Then keep to it.
Send yourself a test submission each month. A changed password or mail filter can stop alerts with no warning.

How do you connect web forms and Meta Lead Ads to the CRM?

Connect both directly, so each submission creates or updates a CRM record with no file in between. For a web form, a form built into your CRM is the simplest route. A separate form tool can work through a connector or an API, but ask what happens to a submission when that link fails. Whichever you use, map each field to a CRM property, save the source and UTM values, and decide what happens when the phone or email already exists.

Meta Lead Ads collect answers on an Instant Form inside Facebook or Instagram, and Meta says name, email and phone may be prefilled. Meta's documentation explains why these leads get lost. When a lead arrives, Meta sends a notification holding only IDs, with a delay of up to a few minutes, and your system must then fetch the answers. The app must be installed on the Page, and the access token must come from a person who can advertise on that Page. Meta's help pages add that a CRM without leads access receives no real-time updates, and that access problems show up in its lead ads testing tool.

Meta also says leads can be downloaded for 90 days from submission, and it recommends regular exports or a CRM. This checklist covers the usual gaps:

Connect the Page and each Instant Form, using an account your company will keep, because an integration tied to one employee's access can stop working when that access changes.
If your business has customized leads access, assign the CRM in Leads Access Manager.
Map custom questions as well as name and phone. For Arabic ads, set the form locale to AR_AR, which Meta's reference lists, so its standard questions appear in Arabic.
Send a test lead and check the owner, source and alert in the CRM.
Compare the lead count in Meta with the count in your CRM every week, so a broken link shows up long before 90 days pass.
If you get many low-quality leads, try the option Meta's API calls is_optimized_for_quality. It adds a step where people review and confirm their answers before submitting. Here you are adding friction on purpose, so judge it by qualified leads.

How do you stop spam without blocking real leads?

Start with checks people never see, and add a visible challenge only if spam keeps coming through. A W3C draft note says traditional CAPTCHAs often stop people with disabilities from completing a task. It also reports that honeypots, which are hidden fields that bots fill in and people never see, appear fairly successful, and that well-tuned background checks can match a visual CAPTCHA. W3C does not endorse the draft, so treat it as informed guidance. Cloudflare says its Turnstile product works without showing visitors a CAPTCHA, which is one example of a background check.

The following order is our judgment:

Add a honeypot field and validate phone and email on the server.
Block specific domains that keep sending junk.
Keep flagged submissions somewhere your team can review them, and do not delete them automatically. Check that folder weekly, because filters catch real people too.
Think hard before rejecting free email addresses. Plenty of small business owners run their company from a Gmail account, and you may be turning away a real buyer.
Treat fake ad leads as a separate problem, since real people mistyping or tapping by accident will pass a bot check. A review step or a phone code is the better tool there.

What consent should a lead form collect?

Tell people how you will use their details, ask separately for marketing permission, and keep a record of what they agreed to. This is a general summary and not legal advice, and these rules change, so confirm your position with a local adviser.

On the form itself, we suggest an unticked marketing checkbox that is separate from the enquiry and names the channels you will use, such as WhatsApp, SMS or email, plus a link to your privacy policy. Store the date, the form, the language and the exact wording. For Meta, the lead forms reference includes a privacy policy link and a custom disclaimer with consent checkboxes, which default to required and unticked. Meta's retrieval guide says those checkbox answers are not in the normal field data and sit in a separate field called custom_disclaimer_responses, so ask whoever builds your connection to save them.

Saudi Arabia: Clyde & Co's summary of the Personal Data Protection Law regulations says consent must be freely given, separate for each purpose and documented. It also says advertising and direct marketing need consent, with an easy way to opt out.
Jordan: Clyde & Co's summary says processing generally needs prior consent that is clear, written, and tied to a specified period and purpose, and that people can withdraw it. DLA Piper notes no specific electronic marketing provisions and reads the law as allowing that marketing without prior consent. The two summaries point in different directions, so get advice before relying on either.
Iraq: a 2025 Chambers guide says Iraq has no specific data protection or privacy law. WhatsApp's policy still applies, and you may hold data on people in other countries.
WhatsApp: the policy allows contact only when someone gave you their number and agreed to receive messages, and you must honor requests to stop. You choose the opt-in method. Our guide to WhatsApp marketing campaigns covers this in more depth.

How does Repzo handle this?

Online forms in Repzo Workstation publish as a shareable link or an embed, and a submission can create or link to a lead, contact or account. You start from a template or a blank form and add fields such as phone, email, dropdown, country and checkbox across one or more steps. You can show or hide fields with conditions, preview on desktop and mobile, and map fields to Contact, Account or Deal properties.

New contacts can stay unassigned, go to a specific user or rotate round-robin across selected team members, and each form can set a lead source and channel. Each submission keeps its attribution, including page URL, UTM values and click IDs, and feeds into lead management for scoring and stages. Notifications go to the form creator by default, and you can add the contact owner, chosen teammates or outside email addresses. A submission can also start a workflow or a Repzo Send campaign.

For spam, you can block chosen email domains, reject free email providers and add a hidden honeypot field, and flagged submissions send no notifications. Each form reports submissions, conversion rate and how often each field is filled in, which helps you find fields to cut. Meta Lead Ads is a listed integration, and the Ads settings map lead forms from Meta, Google and LinkedIn so each submitted lead becomes a contact.

Three details are worth checking on your own setup. Auto-create contacts works from the email address, so test how records are created if your form has no email field. Repzo is available in Arabic and English, but the public documentation does not describe right-to-left behavior on published forms or the phone formats the field accepts. It also does not describe how a form checkbox connects to the per-contact consent that Repzo Send honors. Try these during the 7-day free trial, or ask our sales team.

Frequently asked questions

How many fields should a lead form have?

No study gives one correct number. A 2013 MECLABS test saw conversion fall from 57% to 51% when a job title field was added to the same offer, with some validity caveats, and Zuko's benchmark shows completion tending to fall as questions increase. Our judgment is to start with three to five fields and test against qualified leads.

Should the phone number or the email be required?

Require the one your team actually uses to follow up. That is our judgment, and for many sales teams that call or use WhatsApp it means the phone number. Check first whether your CRM needs an email to create or match a record.

Do I need separate Arabic and English forms?

Either setup can work, as long as both versions save to the same CRM fields and values. Two separate forms make the right-to-left layout easier to control. They also let you compare completion by language, which is a good reason to choose them.

Why are my Meta leads not reaching the CRM?

Common causes are a CRM that was never given leads access, a person's access token that no longer has permission, and a Page that does not have the app installed. Meta's lead ads testing tool can show access errors. Meanwhile, download the leads, since Meta keeps them available for 90 days from submission.

Should I add a CAPTCHA to my form?

Try a honeypot and server-side checks first. A W3C draft note warns that traditional CAPTCHAs often block people with disabilities, and any visible challenge adds a step on a phone. Add one if bots keep getting through.

Can I tick the marketing consent box by default?

We advise against it. Clyde & Co's summary of the Saudi regulations says consent must be freely given, and a box the person never touched is weak proof that they agreed. Meta's own consent checkboxes default to unticked. Confirm the wording with a local adviser.

How to build an online form people finish, with leads going straight into your CRM

The short answer

Key takeaways