Strategy

Helpdesk Software in the UAE: Shared Inbox, Ticketing or CRM Module

SKIMBOX Team

Most UAE teams running support from a shared inbox and WhatsApp buy one category too big. Here is where the boundary sits between a shared inbox, a true ticketing helpdesk and a CRM service module, what the platforms publish as their prices, and what a setup engagement costs. A helpdesk setup starts from around AED 2,500. Final pricing depends on scope.

Helpdesk Software in the UAE: Shared Inbox, Ticketing or CRM Module

Support in a small UAE business almost always starts the same way. One email address that three people can open, and one phone with WhatsApp on it. That works, right up to the morning somebody asks a plain question and nobody can answer it: what is still open, and who owns it.

That question is the spine of this guide. Not headcount. Not ticket volume. If your team can answer it in ten seconds, you probably do not need to buy anything yet. If it takes a scroll through an inbox and a shout across the room, you have outgrown your tools.

The category is also more confusing than it needs to be. Four quite different products are sold under one word, at prices that differ by a factor of ten, and most buyers pay for a category above the one they needed. This guide covers where those boundaries sit, how WhatsApp gets billed now, what the platforms publish as their prices, what UAE data protection means for a ticket archive, and what a setup engagement should cost.

We set up and configure business systems for UAE companies from our Dubai and Bengaluru teams [23]. We are not lawyers and none of this is legal advice.

Shared inbox vs helpdesk vs CRM module vs ITSM

Helpdesk software in the UAE is sold as four different products: a shared inbox, a ticketing helpdesk, a CRM service module, and an ITSM platform.

Shared inbox. A team mailbox with assignment, internal notes and collision detection layered on top. It still looks and behaves like email. Help Scout frames its own free plan around a single inbox allowance, which tells you how that vendor thinks about the shape of the product [13]. There is no formal ticket object, no status everyone trusts, no clock.

Ticketing helpdesk. Every conversation becomes a ticket with a status, a priority, one assignee and a timer. Freshdesk describes an SLA policy as a rule that automatically starts a timer on every new ticket for first response and resolution [9]. That timer is the mechanical difference between the two categories. Zendesk Support, Freshdesk, Zoho Desk and Help Scout paid tiers sit here.

CRM service module. Ticketing that shares a database with sales and marketing, so a ticket and a deal hang off the same contact record. HubSpot presents Service Hub ticketing as sitting inside the wider HubSpot CRM platform for that reason [11]. Zoho Desk plays the same role beside Zoho CRM.

IT service management. Built on the ITIL practice framework. Axelos, which owns ITIL, defines the service desk practice as the single point of contact between a service provider and its users, covering incident resolution and service requests [18]. Freshservice, Jira Service Management and ServiceNow live here. This is employee facing IT support with change, problem and asset management attached, and it is far heavier than a customer inbox needs.

Most buyers do not pick the wrong brand. They pick one category too high, because a demo showed them something impressive and nobody drew the boundary first.

When to move to a ticketing helpdesk

The trigger for a ticketing helpdesk is not agent count or ticket volume; it is whether anyone can say what is open and who owns it. Ask three questions and answer them honestly.

  1. Can anyone in the business say, right now, how many customer issues are open?
  2. For each of those, is there exactly one name against it that everyone agrees on?
  3. Would you know if one had been sitting untouched for two days?

Three clear yeses and you do not have a software problem. Keep your money.

A no on the second means duplicate replies and dropped customers are already happening, whether or not you have noticed. A no on the third means you cannot catch a slow failure, and slow failures are the ones that cost you the customer. Either is the moment a ticketing helpdesk earns its licence fee.

A fourth question decides between a standalone helpdesk and a CRM service module. Does a support conversation need to change what sales or renewals do next? If a complaint should pause a renewal push, or a repeat issue should surface before an upsell, keep tickets and deals on one record. If support is its own workstream, a dedicated helpdesk is narrower and cheaper. Our CRM implementation guide covers the other half of that decision.

When a shared inbox is still the right answer

A shared inbox is still the right answer for a small team with low volume, no external response time commitments, and one person who genuinely knows the state of everything. That is a fine place to be, and buying a ticketing platform for it adds process without adding clarity.

Free tiers make this cheap to test. Zoho Desk publishes a free plan for a small number of agents [15], HubSpot publishes a free Service Hub tier [10], and Help Scout publishes a free plan capped at five users and one inbox [13]. Any of these will show you whether ticket structure helps or just adds clicks.

The failure mode of a shared inbox is not that it breaks. It degrades quietly. Agreements about labels decay in weeks. A status field does not.

WhatsApp customer support: where the budgeting goes wrong

If your customers already message you on WhatsApp, that channel drives most of the cost and complexity of this project. Four things matter.

You cannot connect the number yourself. Meta requires an approved intermediary, which its own documentation names as a Solution Partner or a Tech Provider [4]. Most buyers avoid this by choosing a helpdesk with a native WhatsApp channel.

The number leaves the consumer app. Once a number is connected to the WhatsApp Business Platform, it can no longer be used in the standard WhatsApp app [5]. Decide early whether you are moving the number your customers already know or starting a new one.

Pricing changed on 1 July 2025. Meta moved from conversation based pricing to per message pricing, and charges when a template message is delivered [1][2]. Marketing templates are charged whenever delivered. Utility and Authentication templates are charged only when sent outside an open customer service window [1]. That window is a twenty four hour timer starting when a customer messages or calls you, during which ordinary free form replies are free [3]. Rates vary by category and recipient country, volume tiering exists, and Meta revises rates on a rolling basis, so we are not printing a figure. Read Meta's current rate card [1]. The old conversation based page is marked deprecated [2], and a lot of UAE content still describes that retired model as current, which is why so many circulating WhatsApp cost estimates are wrong.

The channel is usually gated by plan. Zendesk documents WhatsApp as a native channel in the agent workspace, where each inbound message creates a ticket, and gates it behind Suite plans rather than the entry level Support tier [5][6]. Freshdesk documents its WhatsApp integration as available on Growth, Pro and Enterprise [8]. Do not budget the cheapest published seat price and assume WhatsApp comes with it. Our WhatsApp Business API guide covers the setup path in more detail.

SLAs, queues and the knowledge base

An SLA policy starts a timer on every new ticket and measures first response and resolution against a target, configurable by priority and business hours [9]. Start with two policies, not eight. Elaborate SLA structures written at setup rarely survive contact with a real queue.

First response time and resolution time fail for different reasons. Slow first response is usually routing or staffing. Slow resolution is usually process, or a dependency outside the support team. Report them separately or you will hide both. If you want a formal reference point, ISO 18295 is the international standard covering customer contact centre requirements [19]. It does not hand you a public numeric target, and we are not going to invent one.

On the knowledge base, one warning. Every deflection percentage and self service ratio circulating in this market comes from vendor marketing or search optimised blog content. The figures contradict each other and none is independently verified, so this guide publishes none of them. Even the definition is vendor specific: Zendesk counts a deflection when a self service article is viewed and no ticket is opened within twenty four hours of that view [17]. That is a fine internal measure, and it is not comparable to another vendor's number.

What works is unglamorous. Write your ten most repeated answers as articles, link them in replies, and watch your own ticket mix over a quarter. If you are considering a chat layer on top, our chatbot cost guide covers where that helps and where it annoys people.

What helpdesk software costs

Published helpdesk pricing starts from around 19 USD per agent per month and rises to around 115 USD for full omnichannel tiers, per each vendor's own pricing page in US dollars on annual billing. They change often.

PlatformPublished entry priceNotes
Zendesk Support TeamFrom around 19 USD per agent per month [6]WhatsApp needs a Suite plan [5]
Zendesk Suite TeamFrom around 55 USD per agent per month [6]Multi channel entry point
Zendesk Suite ProfessionalFrom around 115 USD per agent per month [6]Voice is a separate bundle [6]
Freshdesk GrowthFrom around 19 USD per agent per month [7]WhatsApp from this tier [8]
Freshdesk ProFrom around 55 USD per agent per month [7]
Freshdesk EnterpriseFrom around 89 USD per agent per month [7]
HubSpot Service HubFree tier, Starter from around 20 USD per seat [10]See the promo trap below
Help ScoutFree for five users on one inbox, Standard from around 25 USD per user [13]Shared inbox shape at entry
IntercomFrom around 29 USD per seat per month [14]AI resolutions billed separately [14]
Zoho DeskFree tier plus paid tiers; pricing varies by region [15]Check the page from the UAE

Three traps worth naming.

The struck through price. HubSpot displays its Service Hub Starter seat price with a lower figure struck through against the standard rate, plus a note that the discount is for new customers only and available for a limited time [10]. The low number is the promotion. Budget on the standard one.

The currency you are billed in. Zendesk, Freshdesk, HubSpot, Intercom and Help Scout all showed US dollar pricing on their standard pages [6][7][10][13][14], and HubSpot's own account documentation confirms tax is calculated on top based on company location [22]. Zoho renders pricing in the visitor's local currency by geolocation, which is why this guide publishes no Zoho Desk figure. Open that page from the UAE and read it live [15]. If you are billed in dollars, your monthly cost moves with the exchange rate.

The channel that is not included. Voice is commonly a separate contact centre bundle rather than part of a base plan [6], and social channels usually sit on the omnichannel tiers. Price the channels, not the seat.

For implementation, a helpdesk setup and configuration engagement starts from around AED 2,500. That covers connecting email and WhatsApp, building statuses and routing rules, writing one or two SLA policies, publishing a first set of knowledge base articles, and training the agents. It sits deliberately below the AED 3,500 floor we quote for a lightweight CRM implementation in our CRM guide, because a helpdesk is a narrower system: fewer objects, no sales pipeline to model, no forecasting layer, far fewer downstream dependencies.

Connecting the helpdesk to another system, such as your order database or accounting package, is priced separately from around AED 1,500 for a standard integration between two systems that both expose working interfaces, as set out in our system and API integration guide. Final pricing depends on scope.

What UAE rules mean for a ticket archive

Federal Decree Law No. 45 of 2021 on personal data protection has been in force since 2 January 2022, and the official UAE government portal states that it applies to the processing of personal data through electronic systems, inside or outside the country. It prohibits processing without the owner's consent except in defined cases, and gives individuals the right to request correction of inaccurate data and to restrict or stop processing [20].

Read that against what is inside a support ticket. Names, phone numbers, order references, sometimes an ID or payment detail. The same law that applies to your CRM records applies to your ticket archive. Practically, that means knowing where tickets are stored, how long you keep them, and whether you can action a correction request against a closed ticket. Our PDPL compliance guide goes deeper.

On messaging consent, be careful about what you read. The UAE telecom regulator directs its published consent and opt out attention at marketing electronic communications specifically [21], and Meta separates WhatsApp templates into Marketing, Utility and Authentication categories at the platform level [1]. A ticket status update is a service message, not a promotional one. That is a reasonable reading of two published sources. It is not a written exemption in UAE data protection law, and we are not presenting it as one. Confirm your own position with a qualified adviser.

On language, customer facing knowledge base support for Arabic is broadly available. Zendesk documents multi language help centre configuration [16] and HubSpot documents multi language knowledge base articles with right to left formatting applied automatically when a right to left language is selected [12]. Agent facing interface Arabic is weaker and more inconsistent, and we did not verify it vendor by vendor, so this guide names no winner. Test it in a trial: switch the agent interface language and see whether ticket views and filters genuinely render right to left.

Real client stories

These are anonymised situations from systems work we have done.

The team that did not need a helpdesk. A boutique services firm asked us to implement a ticketing platform because a competitor had one. Two people handled every enquiry, both knew the state of everything, and there were no external response time commitments. We ran the three visibility questions and all three answers were clean. We set up assignment and internal notes on the mailbox they already had, wrote six repeated answers as saved replies, and stopped. They spent a fraction of the budget and nothing broke.

The number nobody could account for. A retailer ran support from a shared inbox plus a WhatsApp handset on the counter. Nobody could say how many issues were open, and two customers had been promised replacements twice by different staff. The fix was not a bigger platform. It was moving WhatsApp onto the business platform through the helpdesk, giving every inbound message a status and one owner, and writing a single SLA policy for first response. Duplicate replies stopped in week one, because they became impossible rather than discouraged.

The category one size too big. A company came to us mid procurement for an IT service management platform, complete with change management and an asset register, to handle customer emails and WhatsApp messages. Nothing about their support work was internal IT. What they actually did was answer product questions and process returns. We moved them to a mid tier ticketing helpdesk with a WhatsApp channel and a knowledge base. They kept the SLA reporting they wanted and dropped most of the cost.

How SKIMBOX approaches support systems

We start with the visibility questions, not a product demo. If the answers say your shared inbox is still working, we will tell you that and we will not sell you a platform. If they say you have outgrown it, we shortlist inside one category rather than showing you four and letting the biggest one win.

We check vendor pricing pages with you rather than for you, from a UAE session, so you see the currency and the promotional terms yourself. We connect the channels you use, write the smallest SLA policy set that reflects a promise you can keep, and build the first knowledge base articles from your own repeated answers rather than a template pack. We quote no deflection percentages, because nobody can verify them.

We are not lawyers. Anything that turns on UAE data protection obligations goes to a qualified adviser or to the official government sources, and we build around what they tell you.

A helpdesk setup and configuration engagement starts from around AED 2,500. Connecting it to another system starts from around AED 1,500 for a standard integration. Final pricing depends on scope.

See our core business operations services and business consulting services, or contact us to talk through your support setup. Our digital transformation guide for UAE SMEs covers how these decisions fit together, and our data analytics and business intelligence guide covers what to do with the ticket data.

References

[1] Meta - WhatsApp Business Platform pricing. developers.facebook.com/documentation/business-messaging/whatsapp/pricing

[2] Meta - Updates to WhatsApp Business Platform pricing. developers.facebook.com/docs/whatsapp/pricing/updates-to-pricing/

[3] Meta - Send messages, customer service window. developers.facebook.com/documentation/business-messaging/whatsapp/messages/send-messages

[4] Meta - Solution Partners and Tech Providers overview. developers.facebook.com/documentation/business-messaging/whatsapp/solution-providers/overview

[5] Zendesk - Adding WhatsApp channels to the Agent Workspace. support.zendesk.com/hc/en-us/articles/4408842821786-Adding-WhatsApp-channels-to-the-Agent-Workspace

[6] Zendesk - Pricing plans. zendesk.com/pricing/

[7] Freshworks - Freshdesk pricing. freshworks.com/freshdesk/pricing/

[8] Freshdesk - WhatsApp for Freshdesk business integration. support.freshdesk.com/support/solutions/articles/238137-whatsapp-for-freshdesk-business-integration

[9] Freshdesk - Understanding SLA policies. support.freshdesk.com/support/solutions/articles/37626-understanding-sla-policies

[10] HubSpot - Service Hub pricing and plans. hubspot.com/products/service

[11] HubSpot - Ticketing system. hubspot.com/products/service/ticketing-system

[12] HubSpot - Create knowledge base articles in multiple languages. knowledge.hubspot.com/knowledge-base/create-knowledge-base-articles-in-multiple-languages

[13] Help Scout - Pricing. helpscout.com/pricing/

[14] Intercom - Pricing. intercom.com/pricing

[15] Zoho - Zoho Desk pricing. zoho.com/desk/pricing.html

[16] Zendesk - Configuring your help center to support multiple languages. support.zendesk.com/hc/en-us/articles/4408827609882-Configuring-your-help-center-to-support-multiple-languages

[17] Zendesk - Tracking essential self service metrics. support.zendesk.com/hc/en-us/articles/4408894139930-Getting-started-with-self-service-Part-6-Tracking-essential-self-service-metrics

[18] Axelos - ITIL 4 Practitioner: Service Desk. axelos.com/certifications/itil-service-management/itil-practices-manager/itil-4-specialist-monitor-support-and-fulfil/itil-4-practitioner-service-desk

[19] ISO - ISO 18295-1:2017, Customer contact centres. iso.org/standard/64739.html

[20] U.AE Official UAE Government Portal - Data protection laws. u.ae/en/about-the-uae/digital-uae/data/data-protection-laws

[21] TDRA, UAE - Marketing short message service. tdra.gov.ae/en/initiatives/marketing-short-message-service

[22] HubSpot - Understand HubSpot order totals, billing and charges. knowledge.hubspot.com/account-management/understand-hubspot-order-totals-billing-and-charges-frequently-asked-questions

[23] SKIMBOX - Internal experience implementing and configuring business systems for UAE companies, 2026. skimbox.co

Frequently asked questions

  • What is the difference between a shared inbox and a helpdesk?

    A shared inbox is a team mailbox with assignment, internal notes and collision detection layered on top. It still looks and behaves like email. A ticketing helpdesk turns every conversation into a ticket with a status, a priority, one assignee and a timer running against it. The practical difference is that a helpdesk can answer what is still open and who owns it without anyone scrolling. A shared inbox relies on people remembering.

  • Do I need a helpdesk or just a better CRM?

    It depends on where the pain sits. If your problem is that support requests go missing, a dedicated ticketing helpdesk is the narrower and cheaper fix. If the problem is that support and sales cannot see the same customer, a CRM service module keeps tickets and deals on one record. HubSpot presents its Service Hub ticketing as part of the wider HubSpot CRM platform for exactly that reason. Most small teams need the first one.

  • Is Zoho Desk the same thing as Zoho CRM?

    No. Zoho Desk is the support and ticketing product. Zoho CRM is the sales pipeline product. They are separate applications that share the wider Zoho platform, and both are included in the Zoho One suite. That matters commercially, because a business already paying for Zoho One usually already owns Zoho Desk and needs a configuration project rather than a new software purchase. Check what your existing licence already covers before you shop.

  • What is the difference between a help desk and a service desk?

    Under the ITIL framework, which Axelos owns, a service desk is the formal single point of contact between a service provider and its users, covering incident resolution and service requests. In everyday usage a help desk is the narrower customer facing support and ticketing tool. Most UAE businesses searching for helpdesk software want the second one. Buying a full IT service management platform for a customer inbox means paying for change and asset management nobody will use.

  • Do I need ITSM software or a normal helpdesk?

    IT service management tools are built for internal IT support, with formal incident, problem, change and asset management workflows. If the people raising requests are your own employees and you need approval chains and configuration records, that is the right category. If the people raising requests are your customers, arriving by email, WhatsApp and web chat, you want a customer support ticketing helpdesk instead. The two are often shown side by side and are not interchangeable.

  • Can I keep running support from a shared Gmail inbox?

    Yes, and plenty of small teams should. A shared mailbox works while one or two people handle everything and nobody is asking for response time reporting. It stops working the moment you cannot say how many issues are open, or when two people reply to the same customer because neither could see the other. That failure is about visibility, not volume. Some teams hit it at thirty messages a week and some never do.

  • What is the real trigger for moving to a ticketing helpdesk?

    Not headcount and not ticket volume. The trigger is whether anyone in the business can answer one question on demand: what is still open and who owns it. If the answer needs a scroll through an inbox, a shout across the room or a guess, you have outgrown the tool. Teams usually try to fix this with discipline first, agreeing labels and rules. Discipline decays. A status field on a ticket does not.

  • How do I connect WhatsApp to a helpdesk?

    You cannot connect a business number to the WhatsApp Business Platform on your own. Meta requires an approved intermediary, which its own documentation calls a Solution Partner or a Tech Provider. In practice most buyers use a helpdesk that already offers a native WhatsApp channel and connect the number through that vendor setup flow. Inbound messages then arrive as tickets and agent replies go back out over WhatsApp without anyone touching Meta APIs directly.

  • Does Zendesk have WhatsApp built in?

    Zendesk offers WhatsApp as a native channel in its agent workspace, where each inbound message creates a ticket carrying the conversation history and agents reply from inside Zendesk. Two conditions matter before you budget. The person connecting the number has to be an admin in Meta Business Manager, and the channel sits on the Suite plans rather than the entry level Support only tier. Confirm the current plan requirement on Zendesk pricing before committing.

  • Does Freshdesk support WhatsApp?

    Freshdesk publishes a native WhatsApp Business integration, and its own support documentation lists the channel as available on the Growth, Pro and Enterprise plans across Freshdesk and Freshdesk Omni, with more than one WhatsApp number able to be linked. As with every vendor, plan gating changes over time, so read the current documentation rather than an article. The point to carry into budgeting is that WhatsApp is rarely included on the cheapest published tier.

  • Can I still use the normal WhatsApp app after connecting to the API?

    No. Once a phone number is connected to the WhatsApp Business Platform it can no longer be used in the standard consumer WhatsApp app. This catches teams out badly when the number they connect is the one somebody has been using on a handset for years. Decide early whether you are moving the existing number or starting a new one, and if you move it, tell customers and staff before the switch rather than after.

  • How does Meta charge for WhatsApp messages now?

    Meta moved to per message pricing on delivered template messages on 1 July 2025. Marketing templates are charged whenever they are delivered. Utility and Authentication templates are charged only when they are sent outside an open customer service window. Rates differ by template category and by the recipient country code, volume tiering exists for some categories, and Meta revises the rates on a rolling basis. Read the current rate card on Meta developer documentation before you budget.

  • Is WhatsApp still billed per conversation?

    No. The conversation based model, where a twenty four hour window was billed as one unit, was retired on 1 July 2025 and Meta marks that documentation page as deprecated. A great deal of content still online describes the old model as current, which is why WhatsApp cost estimates circulating in the UAE market are often wrong. Check the publication date on anything you read about WhatsApp pricing, including cost breakdowns published by consultancies.

  • Are my WhatsApp replies to customers free?

    Free form replies sent inside an open customer service window are not charged, and Utility category templates sent inside that window are also free under the current model. Messages sent once the window has closed generally need a paid template. There is also a seventy two hour free entry point window triggered when a user contacts you through a click to WhatsApp advert. The practical effect is that reactive support costs far less than proactive outreach.

  • What is a WhatsApp customer service window?

    It is a twenty four hour timer that starts when a WhatsApp user messages or calls your business number. While that window is open you can send the service message types Meta lists, including ordinary free form replies, without a template. Every new inbound message from that customer restarts the clock. This is the single most useful thing to understand about WhatsApp billing, because it explains why answering quickly is cheaper than answering late.

  • What is an SLA in a helpdesk tool?

    An SLA policy is a rule that starts a timer on every new ticket, measuring first response and resolution against an agreed target. Freshdesk describes it in exactly those terms in its own documentation. Most platforms let you vary the target by ticket priority and by your business hours, and flag or escalate a ticket when the timer is breached. It is the feature that converts a vague promise about response times into something visible.

  • What is the difference between first response time and resolution time?

    First response time measures how long it takes an agent to send the first reply after a ticket is created. Resolution time measures how long until the issue is actually closed. They are tracked separately because they fail for different reasons. Slow first response is usually a routing or staffing problem. Slow resolution is usually a process or dependency problem. Fixing one does not fix the other, and reporting them together hides both.

  • Will a knowledge base actually reduce my ticket volume?

    Directionally it helps with repetitive how to and policy questions, which is the honest thing to say. What we will not do is quote you a percentage. Every deflection figure circulating in this market comes from vendor marketing or search optimised blog content, the numbers contradict each other across sources, and none of them is independently verified. Write your ten most repeated answers as articles, link them from your replies, and measure the change in your own ticket data.

  • How does a helpdesk count a deflected ticket?

    Definitions are vendor specific, which is part of why cross vendor deflection statistics are meaningless. Zendesk documentation, for example, counts a deflection when a self service article is viewed and no ticket is opened within twenty four hours of that view, and publishes a self service score based on help centre sessions against ticket submitting users. That is a reasonable internal measure. It is not comparable to another vendor number calculated a different way.

  • Do I need different SLAs for different customers or ticket types?

    Usually yes, and most platforms support several SLA policies rather than one blanket timer. A common pattern is a tighter first response target for urgent or high value accounts and a longer one for general enquiries, with both measured only inside working hours. Start with two policies, not eight. Complex SLA structures written at setup rarely survive contact with a real queue, and every extra policy is another thing to maintain and explain.

  • How much does helpdesk software cost per agent per month?

    On the vendors own published pricing pages, Zendesk Support Team starts from around 19 US dollars per agent per month on annual billing, with Suite Team from around 55 and Suite Professional from around 115. Freshdesk publishes Growth from around 19, Pro from around 55 and Enterprise from around 89. Help Scout publishes Standard from around 25 per user. All are quoted in US dollars, and local tax is added at checkout.

  • Is the cheapest advertised price the price I will actually pay?

    Not always, and there is a confirmed example. HubSpot shows its Service Hub Starter seat price with a struck through figure and a note that the discount applies to new customers only for a limited time. The lower number is the promotion. The higher one is the ongoing rate. Budget on the standard figure, diarise the date the promotional period ends, and check whether the published price assumes annual rather than monthly billing.

  • How much does Zoho Desk cost in the UAE?

    We are deliberately not printing a figure. Zoho pricing pages render in the visitor local currency based on geolocation, and a fetch during our research returned a currency that was neither dirhams nor dollars. That means any number quoted in an article may not be the number you see. Zoho does publish a free tier for a small number of agents plus several paid tiers. Open the Zoho Desk pricing page yourself from the UAE and read it live.

  • Will I be billed in dirhams or in US dollars?

    It varies by vendor and it is worth checking before you sign. Zendesk, Freshdesk, HubSpot, Intercom and Help Scout all showed US dollar pricing on their standard global pages during our research. HubSpot own account documentation confirms tax is calculated on top based on company location. Zoho renders pricing in a local currency by geolocation. If you are billed in dollars, your monthly cost moves with the exchange rate, so budget with headroom.

  • What does it cost to set up a helpdesk properly, not just the licence?

    A setup and configuration engagement starts from around AED 2,500 with us. That covers connecting email and WhatsApp, building the ticket statuses and routing rules, writing one or two SLA policies, standing up a first set of knowledge base articles and training the agents. It sits below our AED 3,500 CRM implementation floor on purpose, because a helpdesk is a narrower system with fewer objects and fewer downstream dependencies. Final pricing depends on scope.

  • Is there a genuinely free helpdesk option?

    Yes, several vendors publish free tiers on their own pricing pages. Zoho Desk publishes a free plan for a small number of agents, HubSpot publishes a free Service Hub tier, and Help Scout publishes a free plan limited to five users and one inbox. These are real products rather than trials, and they are a sensible starting point for a very small team. Read the limits carefully, because channels and reporting are usually what is missing.

  • Do I have to pay extra for phone or voice support?

    Generally yes. Voice is commonly sold as a separate telephony or contact centre bundle rather than included in a base ticketing plan, and Zendesk publishes its Contact Center bundle as a distinct higher priced line on its own pricing page. If phone is a real channel for your business, price it explicitly at the shortlist stage. Discovering that voice is an add on after you have signed for seats is an avoidable surprise.

  • Does UAE data protection law apply to support tickets?

    In principle yes. UAE data protection law applies to a support ticket archive. Federal Decree Law No. 45 of 2021 has been in force since 2 January 2022 and applies to the processing of personal data through electronic systems, inside or outside the country, according to the official UAE government portal. Support tickets routinely contain names, phone numbers and order details, which is personal data. The same law that applies to your CRM records applies to your ticket archive. This is not legal advice.

  • Is consent for support messages the same as consent for marketing messages?

    They are handled differently at the platform level, though you should confirm your own position with a qualified adviser. Meta separates WhatsApp templates into Marketing, Utility and Authentication categories, and the UAE telecom regulator directs its published consent and opt out attention at marketing electronic communications specifically. A ticket status update is a service message rather than a promotional one. Do not read that as a formal exemption written into UAE data protection law, because that is not what the source says.

  • What is the penalty for a data protection breach in the UAE?

    We are not quoting one. The official UAE government portal page on data protection law does not publish penalty amounts, and figures circulating on third party compliance marketing sites could not be verified against a government source during our research. If a penalty figure matters to your decision, get it from an official publication or a qualified legal adviser rather than from an article. Treat any specific dirham number you see quoted online with suspicion until you have checked it.

  • Can my customers read the knowledge base in Arabic?

    Customer facing knowledge base support for Arabic is broadly available across the major platforms. Zendesk documents multi language help centre configuration, and HubSpot documents multi language knowledge base articles with right to left formatting applied automatically when a right to left language is selected. Plan tier affects how many language variants you get. The practical work is not the switch, it is producing and maintaining genuinely useful Arabic content rather than machine translating your English articles.

  • Can my agents work in Arabic inside the admin screens?

    This is a different question from the customer facing help centre and a much weaker one. Agent facing interface language support varies between vendors and changes over time, and we did not verify it per vendor, so we are not going to tell you which platforms have it. Test it yourself during the trial. Log in as an agent, switch the interface language, and look at whether the ticket views, filters and reports genuinely render right to left.

  • How long does it take to get a helpdesk running?

    For a small team, connecting email and WhatsApp, agreeing statuses and routing, writing one SLA policy and publishing a first set of knowledge base articles is a matter of days to a couple of weeks. It is not a multi month programme in the way a CRM or ERP rollout is. The part that takes longest is usually agreement about who owns what, which is a management decision rather than a configuration task.

  • Can I migrate my old WhatsApp conversations into a new helpdesk?

    Plan for a clean cutover rather than a backfill. Historical WhatsApp chat content is not portable the way a mailbox is, so when a number is connected to the WhatsApp Business Platform you should expect history to start from that point. Export what you need for reference before the switch, pick a cutover date, and tell the team that anything before it lives in the old export and anything after it lives in the helpdesk.

SKIMBOX Team

Tech Consultancy

Get fresh writing in your inbox

One email a fortnight. No filler.

By subscribing, you agree to our privacy policy.

Want us to build something?

We work with teams across MENA, UK, USA, and India to build products, run programs, and grow.

Get in touch

Continue reading