What happens to a UAE enquiry after the form: the CRM integration gap

What happens to a UAE enquiry after someone presses send?

Many UAE websites described as "connected to the CRM" do one thing well: they move a submission from the form into a record. That is the visible half of a CRM integration. The other half is whether the record arrives in a state a salesperson in Dubai can act on, with an owner, a callable number and a known source. Moving data closes the gap between two systems on paper. In practice the gap just moves inside the CRM.

The pillar on the path from enquiry to record describes how the flow should run. If enquiries never reach an inbox at all, start with the contact form that sends to nobody. This piece looks at the next step: the enquiry did arrive, and something still went wrong.

What does CRM stand for?

CRM stands for customer relationship management. In Zoho's own definition, businesses use CRM software as a repository that brings sales, marketing and customer support together in one place. For this piece the meaning is narrower: the CRM is where a website enquiry should end up as a record that a named person works on.

Who owns the record when nobody decided?

Web forms in Zoho CRM exist to import website data into the CRM, and the vendor documentation is plain about what happens if setup stops there: "By default, all incoming records are assigned to the administrator." (Zoho CRM help, web forms) The administrator is often whoever set the system up. Sometimes that is an agency that left long ago.

Say a real estate agency in Dubai Marina connects its listing enquiry form on a Thursday. The test lead arrives, everyone is pleased, and the project is closed. Weeks later the sales manager asks why nobody followed up on the villa enquiries. They are all sitting under the admin user, who gets no task and opens the CRM when something breaks.

Assignment is a decision, not a setting. The software will route by round robin, by emirate or by language. Someone in the business has to choose, and write the choice down.

Why does the same customer show up twice?

The second failure is quieter. A customer in Dubai sends the website form on Monday and a WhatsApp message on Wednesday. Is that one person in your pipeline, or two?

Most CRMs answer with a duplicate check on a single field. In the Zoho CRM API the operation is called upsert, which "allows you to insert a new record or update an existing one based on duplicate check field values", and for leads the system default field is Email (Zoho CRM API, upsert records).

That holds until the email differs. A typo, a personal address on the form and a work address on the follow-up, and the check sees a stranger. The fix is not a second CRM. It is deciding which field identifies a person in your business. In the UAE that is often the mobile number, because the real conversation happens on the phone.

Is +971 50 the same number as 050?

To a person, yes. To a duplicate check, no. The international format for phone numbers comes from ITU-T Recommendation E.164, "The international public telecommunication numbering plan" (ITU-T E.164). In that format a UAE mobile starts with the country code. A visitor typing into a free text field writes whatever they are used to: a leading zero, spaces, a plus sign or none.

Here is what that looks like for one person who got in touch three times, as an illustration: "050 123 4567", "+971501234567" and "971 50 123 4567". Only the second spelling is in the international form the E.164 numbering plan describes. To the CRM these are three leads with no match between them. Click to call and WhatsApp links tend to fail on the local spelling too, because they expect the international one.

The cure sits between the two systems. Normalise the number before the record is written, then run the duplicate check on the normalised value. That one step is the difference between moving data and integrating it.

Where did this enquiry come from?

Ask the owner of a UAE SME which channel brings the best clients and the answer is usually a feeling. Often the data existed for a moment. A visitor arrives from a newsletter link that carries campaign parameters in the URL, such as utm_source, utm_medium and utm_campaign, which Google documents as the referrer, the marketing medium and the campaign (Google Analytics help, URL builders). Analytics sees them. The form usually does not, so the CRM record says "Website" and nothing more.

Take a clinic in Abu Dhabi promoting a new treatment. It can see the visits in analytics and the bookings in the CRM, but it cannot join the two, because the thread between them was dropped at the form. Carrying those parameters into hidden fields, and from there into the lead source, is a small piece of work. Without it, no sales pipeline report can tell you which spend produced which deal.

What does a finished hand-off look like?

A record is ready for the sales pipeline when four things are true, not one:

• It has an owner who receives a task, not the admin account.
• The phone number is stored in international format, and the duplicate check runs on it.
• Source and campaign travelled from the URL into the record.
• The consent the visitor gave on the form is stored with the record, with its date.

In practice the last line is the easiest to forget, and the one you will want when a customer asks what you hold about them and why. None of this needs a new system. A small trading company in Sharjah on a simple CRM and a group on a large suite face the same four questions. If you are still choosing the system itself, the page on CRM software in the UAE is a better starting point than any feature list.

When someone tells you the website is "integrated", ask for one test. Submit an enquiry with a local mobile number through a tagged link, then open the record together and read it field by field. What arrived is your integration. What did not is the gap.

How the website build and the connection to your CRM are set up as one piece of work is described on our services page.