Why your recruitment CRM needs to understand the Middle East

I built these features because no other CRM had them

I'm the Head of Engineering at Recruitly. When we moved our executive team to Dubai in 2025, we started working closely with recruitment agencies across the Gulf. Within the first month, I had a list of 15 things that every agency needed and no Western-built CRM supported. These aren't edge cases. These are fundamental requirements for recruiting in the Middle East.

If you're running an agency in Dubai, Riyadh, Doha, or anywhere in the GCC, and you're using a CRM built in London or Boston, you're fighting the tool every day. Here's what's actually needed.

Arabic names break most CRMs

Take the name Mohammed bin Rashid Al Maktoum. Most CRMs have two fields: first name and last name. Where does "bin Rashid" go? What about "Al Maktoum"? Is that a family name or a tribal name? Arabic naming conventions don't follow the Western first/last pattern. You have the given name (ism), the patronymic (nasab, often "bin" or "bint"), the family name, and sometimes a tribal or regional identifier.

We built flexible name fields that handle this properly. You can store the full name as it appears on documents, set a preferred display name, and search across all name components. Sounds simple, but I've seen agencies store "Al Maktoum" as the last name and lose the middle parts entirely. When you're matching candidates to jobs, losing name data means losing people.

Salary packages are not a single number

In the UK, salary is one figure. In the Gulf, a salary package has multiple components: basic salary, housing allowance, transport allowance, education allowance for dependents, annual flight tickets home, and sometimes a car allowance. The basic salary is critical because gratuity and other end-of-service calculations are based on it, not the total package.

A candidate earning 25,000 AED per month might have a basic of 12,000 and allowances making up the rest. If your CRM only stores one salary field, you can't do the calculations that matter. We built component-based salary fields so agencies can break down packages properly and compare like-for-like across candidates.

Gratuity and visa tracking

Gratuity is the end-of-service benefit in the UAE. It's calculated as 21 days of basic salary per year for the first 5 years, and 30 days per year after that. Agencies need to help candidates understand their total compensation, and that means calculating gratuity based on the basic salary component. A candidate with 7 years of service and a 15,000 AED basic has significant gratuity entitlement. If you can't calculate this, you can't advise candidates properly.

Visa status tracking is equally important. Every expatriate worker in the Gulf needs a valid visa and work permit. Your CRM needs to track visa type, sponsor, expiry date, and status. A candidate whose visa expires in 30 days has a completely different timeline than one with 2 years remaining. Some candidates are on husband/father visas, which affects their work permit requirements. None of the CRMs built for Western markets track any of this.

Multi-currency across six different currencies

The GCC has six currencies: AED, SAR, QAR, BHD, OMR, and KWD. An agency in Dubai might place candidates in Saudi Arabia, Qatar, and Bahrain. Each job has a salary in a different currency. Each invoice to a client might be in a different currency. Your CRM needs native multi-currency support, not a conversion calculator on the side.

Revenue reporting across currencies is essential. You need to see total billings in your base currency while tracking individual placements in the client's currency. We handle this with currency-aware fields throughout the system.

WhatsApp is the primary channel, not email

In the UK and US, recruiters live in email. In the Middle East, everything happens on WhatsApp. Candidate communication, client updates, interview confirmations, document collection. If your CRM doesn't integrate with WhatsApp natively, your recruiters are switching between apps constantly and none of those conversations are logged.

We built WhatsApp as a first-class channel. Messages are logged against the candidate or client record. You can send bulk messages for job broadcasts. Templates handle common workflows like interview confirmations and document requests. This isn't a nice-to-have integration. In the Gulf, it's the primary communication tool.

RTL text and timezone scheduling

Arabic is a right-to-left language. If your CRM can't render RTL text properly, Arabic notes, names, and addresses display as garbled text. We built RTL support throughout the interface so Arabic text renders correctly alongside English text. This matters for agencies that operate in Arabic and English simultaneously.

Timezone management is another one that Western CRMs get wrong. A Dubai agency might have candidates in UAE (GMT+4), clients in Saudi Arabia (GMT+3), a sourcing team in India (GMT+5:30), and a client's head office in London (GMT/BST). Interview scheduling needs to show the correct local time for every participant. We handle timezone-aware scheduling across all these regions using AI-powered scheduling.

These are not nice-to-haves

Every feature I've described here is a dealbreaker for Gulf agencies. Not a wish-list item. A dealbreaker. If your CRM can't handle Arabic names, salary components, visa tracking, WhatsApp, and multi-currency, your team is working around the tool instead of with it. We built these features because we're here, in Dubai, working with these agencies daily. Read more about why we built Recruitly in Dubai or check our guide on starting a recruitment agency in Dubai. You can also explore our sourcing tools, marketplace integrations, and developer API.