
Most service businesses need three or four fields on a lead form: name, phone number, the service wanted as a choice from a list, and a fourth field only if sales needs it before the first call, such as the city. Every extra field asks more of a visitor on a small screen, so it has to change something your team does when it calls.
The field count is half the problem. The other half is how the form behaves on a phone: which keyboard appears, whether autofill works, whether the phone number is accepted the way people type it, what the error says, and what happens after the tap. This article gives you a rule for choosing fields, the phone field set up for Egypt and Saudi Arabia, and a test to run yourself on two phones before you pay for ads.
Choose lead form fields from the first sales call
Pick the fields from the questions asked in the first two minutes of a sales call, not from a wish list. Sit with whoever answers your leads and write down what they actually ask before deciding how the call goes. Then put one question to every field: would we act differently if we knew this before calling? If not, drop the field or ask it on the call.
| Field | Keep it when | Drop or postpone it when |
|---|---|---|
| Name | Always, as one field | Never split it into first and last name |
| Phone number | You follow up by call or WhatsApp, the most common route in what we see in Egypt and Saudi Arabia | You follow up by email only |
| Service wanted | You sell several services and a different person handles each | The page is about one service, so you already know |
| City or area | You serve set areas or route leads by branch | You serve everyone the same way |
| You will send a quote or file by email | You will not use it before the first call | |
| Company name | You sell to companies and the offer depends on their size | You sell to individuals |
| Budget range | Large deals, and your team turns down work under a set amount | You will ask on the call anyway |
| Free-text message | Optional, for people who want to explain | Required, where many people stop |
Write "optional" next to optional fields instead of putting an asterisk on required ones. Visitors do not always know what an asterisk means, and the word needs no explanation.
The budget question divides people most. My view is that it earns its place only when you have a clear minimum and a small team with no time for small requests. Offer it as a choice of ranges, never a box for a typed number. How to word each field label and the reason you ask for it is covered in how to write a landing page that turns visitors into leads.
The phone number field for Egypt and Saudi Arabia
Accept the number however the customer types it, then clean it on the server and store it in one international format. This is the most important setting on the whole form, because a wrong number is a lead nobody reaches. Whoever builds the form needs to know what a number looks like in each country:
| Item | Egypt | Saudi Arabia |
|---|---|---|
| Country code | +20 | +966 |
| Mobile number length as written locally | 11 digits, per the NTRA presentation at a 2024 ITU workshop | 10 digits; the example on the CST numbering page is 0551234567 |
| After the country code | The leading zero is dropped | The zero is dropped, so the number starts with 5 followed by eight digits, per Saudi Arabia's notice to the ITU |
Real customers write the same number many ways: with the local zero, with +966, with 00 in front, or with spaces. Some type Eastern Arabic digits, the ones used in Arabic script. So:
- Keep the number in one field instead of splitting it into boxes. web.dev advises a single input for telephone numbers so browsers offer autofill.
- Accept spaces, dashes and symbols, and strip them yourself on the server.
- Convert Eastern Arabic digits to Western digits before checking, instead of rejecting them.
- Default the country code to the campaign's country, and let people change it if their number is from elsewhere.
- Set the field to left-to-right even on an Arabic page, since a phone number reads that way.
- Check length and prefix after cleaning, and tell the customer what is wrong if the number does not fit.
Say why you need the number next to the field, for example "Only to call you about your request". In its research on the phone field, Baymard reports that some participants in its usability tests entered a false number or abandoned checkout when a site required a phone number with no explanation, and that 14% of the 1,026 online shoppers in its survey said they would never give an online store their number. That research looked at store checkouts, which differ from a service request form, but the reason carries over: people hesitate when they do not know why you want their number.
Input type and autofill decide how fast people type on a phone
Two settings in the form's code save visitors most of the typing: the input type and the autocomplete attribute. Owners never see them in a design, so ask your developer for them by name.
| Field | Type | Autocomplete value |
|---|---|---|
| Name | text | name |
| Phone number | tel | tel |
| Company name | text | organization |
MDN notes that type tel may make mobile browsers show a keypad built for phone numbers, and that it does not check the format by itself because number formats vary so much around the world. Checking stays your job on the server. MDN also explains that correct autocomplete values let the browser offer the saved name and number, and warns against switching autocomplete off or inventing values.
Put a permanent label above every field instead of relying on the grey text inside it (the placeholder). That text vanishes with the first keystroke, so people forget what was asked and cannot review what they typed. Nielsen Norman Group reports that user testing keeps showing placeholders in form fields hurt usability more than they help, and recommends visible labels outside the field. Keep placeholder text for a short example only, such as the number's format.
Error messages that tell visitors what to do
A good error message sits next to the field and says what went wrong and how to fix it. This is what the WCAG accessibility standard asks for in its error identification criterion: identify the field in error and describe the error to the user in text.
- Weak: "Invalid data" at the top of the form. Stronger, under the phone field: "This number is too short. Saudi mobile numbers have 10 digits and start with 05."
- Weak: "Required field". Stronger: "Enter your name so we know who to ask for."
- Check a field when the visitor leaves it, and do not flash errors on every keystroke.
- Keep everything the visitor typed when an error appears. A form that clears itself after one mistake loses people who had already started.
- If sending fails because of the network or the server, say so plainly and keep the data in place for a retry.
Consent and the privacy notice under the button
Under the button, add one line saying what you will do with the data, who will get in touch and how, with a link to your privacy policy. For example: "We will use your number to contact you about this request by phone or WhatsApp. Privacy policy." The line answers the visitor's question before the tap and records what they agreed to.
If you want to send offers or marketing messages later, give that its own checkbox, unticked by default. Asking for a callback and agreeing to marketing are two separate things. What the WhatsApp Business rules require is in how to build a follow-up system that never loses a lead.
Egypt has Personal Data Protection Law No. 151 of 2020, and Saudi Arabia has its Personal Data Protection Law. The details differ between them. This paragraph is not legal advice, so check your obligations with your adviser.
Spam protection that real customers never notice
Start with protection the visitor cannot see, and never put an image puzzle in front of everyone who asks for your service. Every step you add to prove a visitor is human costs your real customers too. Layer it like this:
- A hidden field (a honeypot) that people never see. If it gets filled, a bot sent the form, and the request is quietly rejected.
- A limit on how many requests one device or address can send in a short time.
- Server checks on the number and name, rejecting submissions with links in the name field.
- An invisible check if spam keeps coming. Google says reCAPTCHA v3 gives each request a score from 0.0 to 1.0 without interrupting the user, and Cloudflare describes Turnstile as verifying visitors without showing them a puzzle in most cases.
Do not reject a lead automatically because its score is low. Put it in a review list and look through it weekly, because rejecting a real customer by mistake shows up in no report.
What happens after the visitor taps send
After the tap, the visitor should see at once that the request is being sent, then land on a thank-you page, while the lead reaches the person in charge within minutes. A break anywhere in that chain loses a lead you paid for.
- Change the button to "Sending" and disable it until the reply arrives, so a double tap does not create a duplicate lead.
- Send the visitor to a separate thank-you page that states the next step and when. How to word it is in the landing page copy article linked above.
- Tie the thank-you page or successful send to a conversion event in analytics and the ad platform, as set out in how to measure conversions after privacy limits.
- Send the lead to one place the owner of the lead checks, such as a shared sheet or a CRM, instead of an inbox one person checks once in the evening.
Meta instant forms or a form on your site
An instant form inside Facebook and Instagram is faster for the visitor, and your own site form gives you more control over fields and measurement. Meta's page on instant form types lists three types, and two matter for this decision:
| Item | Instant form, More volume | Instant form, Higher intent | Your site form |
|---|---|---|---|
| Purpose according to Meta | Quick submission on mobile and more leads; the default | More intentional leads, with a review screen before sending and a note that the business may follow up | You decide |
| Where it shows | Inside the app | Facebook Feed and Instagram feed on mobile only, per Meta | Your page, whatever the traffic source |
| What the customer sees first | The ad and the form | The ad, the form and the review screen | A full page about the service |
| Where the data lands | Inside Meta until you connect or download it | Inside Meta as well | Straight into your system |
Either way, the instant form setup has a slot for a privacy policy link, and Meta says the link cannot point to a PDF, an image or a direct download. The field rules in this article apply inside instant forms too: a needless field is just as needless inside Facebook. When to use a landing page instead of an instant form in the first place is covered in what a landing page is and why your ad campaign needs one.
Test your lead form on a phone before the ads start
Test the form yourself on two phones, one Android and one iPhone, on mobile data rather than the office Wi-Fi. It takes about fifteen minutes. Record the result of each item:
- Tap the phone field. Did the number keypad appear?
- Tap the name field. Did the phone suggest your saved name?
- Type the number with the local zero, then with the country code, then with spaces, then in Eastern Arabic digits. The form should accept it every time.
- Submit the form empty. Did a message appear next to each missing field, with your typing still there?
- Can you see the send button without the keyboard covering it, or reach it easily once the keyboard closes?
- Send a real request. Did you reach the thank-you page, did the lead show up for the person in charge, and how many minutes did it take?
- Open analytics and the ad platform. Was the conversion recorded exactly once?
- Tap send twice quickly. Did you get a single lead?
Fix every failed item before launch, because it repeats for every visitor. Once the campaign runs, compare how many people started typing in the form with how many sent it, if your analytics records both events. A big gap points to a field that stops people, so start with the field you added most recently.
Your next step
Open your current form on your phone today and run the eight-item test. Then spend fifteen minutes with your sales team, put "would we act differently?" to every field, and remove the ones that fail. If the form needs rebuilding or connecting to measurement and follow-up, that is part of PlanKit's website and landing page development service.