Frequently asked questions

Modern models handle Iraqi dialect well in most cases, and we test on your customers’ real conversations before launch to fix weak spots.

Yes, like any system — so we constrain it to your data and specific tools, require human approval for sensitive actions, and audit conversation samples regularly.

It works best taking the repetitive questions so staff can focus on cases needing human judgement and relationships.

WhatsApp, Telegram, Messenger, Instagram, your website, your app and internal staff tools.

We choose providers and settings that don’t train on your data under their published terms, or run an open-source model on your servers.

Yes, and we recommend it: one task, one channel and clear metrics, then expand.

Usually yes after migrating it to the API, but it then won’t work in the regular app the same way; we plan the move with you.

Bans usually come from unofficial tools or bulk-messaging people who didn’t opt in. We use the official API and follow Meta’s policies.

A simple menu bot can take around two weeks after verification completes; an AI bot connected to your systems 3 to 6 weeks for a pilot.

Only to opted-in customers and via approved templates; anything else risks restrictions on the number.

Yes, in your system, with retention and permissions you define, linked to the customer record.

Yes. The contract transfers source-code ownership to you on payment, delivered in a repository under your organisation’s name.

Yes, and we recommend it. We start with the highest-impact module and add others based on real usage.

Yes. We clean and map the data to the new structure and test the migration before launch.

On your own servers or a cloud you choose; we help you weigh the two based on data sensitivity and budget.

The support agreement covers fixes; new changes are estimated and scheduled with you as clearly priced change requests.

Yes. We prepare the listings, descriptions and screenshots and follow the review through to approval, published under your organisation’s account.

Yes. We integrate the local gateways available to your business once your merchant account is approved, alongside cash on delivery.

Yes. We build multilingual from the start with both text directions; Kurdish is added on request.

You do. Store accounts are in your name and the source code is handed over under the contract.

Yes, through monthly or yearly support plans covering fixes, OS updates, monitoring and backups.

A 5–10 page company site usually takes 3 to 6 weeks, depending on how ready the content and images are.

Yes. We can write Arabic and English copy after interviewing your team, built around the terms your customers search for.

We help you register the domain (including .iq) and choose hosting, and can manage hosting under a support plan.

Yes, with the local gateways available to your business plus cash on delivery.

Core modules for a mid-sized company usually take 3 to 6 months, longer with more branches, modules and customisation.

Yes. Offline mode can be enabled for POS and warehouses with automatic sync when the connection returns.

Yes — we often recommend starting with inventory and sales, then adding finance and HR.

Yes. We migrate items, customers, suppliers and opening balances after cleaning and reconciling them.

We apply fine-grained permissions, encrypted connections, scheduled and tested backups, and an audit log for every action.

Yes, via the official WhatsApp Business API, so chats are saved to the customer record and messages can be sent from the system.

Yes. You can start with a simple version for leads and follow-ups and expand as the team grows.

In most cases yes, depending on your current system’s data-exchange capabilities. We assess this during analysis.

A practical first version usually takes 6 to 12 weeks, depending on integrations and the field app.

Yes. It works fully offline and syncs sales and stock automatically when the internet returns.

Yes. Items can be priced in either currency and paid in both, using a rate you set daily.

Yes, through a mobile dashboard showing sales, profit and stock per branch.

Yes. We import items, prices, barcodes and balances from your old software or Excel.

In most cases yes; we integrate with the devices common in the market and verify your model before starting.

Yes. All allowance, deduction, lateness and overtime rules follow your internal policy.

Yes, via a mobile app that records attendance by location within a geofence you define.

Yes, with fine-grained permissions, encryption and an audit log of who viewed or changed data.

Yes. You can contract design alone; we deliver Figma files and the design system to your team or any developer.

A mid-sized app usually takes 3 to 6 weeks for full design with an interactive prototype.

Yes, the source design files are handed over in full.

It is defined in the SLA per plan. [Insert actual response times per plan].

It depends on your requirements: a global cloud with nearby data centres, servers inside your organisation, or a mix.

Yes. We plan, test and run the migration in a low-traffic window to minimise downtime.