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.

It depends on scope: a menu bot for one task usually costs far less than an AI bot connected to your order and booking system. On top of the build there’s a monthly running cost covering Meta’s fees on some messages, language-model usage and maintenance. We give you a written estimate once we understand your tasks; our pricing page explains how we price.

A bot on the official WhatsApp Business API that follows the rules is the use Meta permits. Bans usually come from unofficial programs or bulk-messaging people who didn’t opt in, and under Meta’s current policies a number can also be restricted if many users block or report it. 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.

Yes, in most everyday conversations, such as asking a price or where an order is. We test it before launch on your real customer conversations and add a glossary of your products and areas; if it doesn’t understand a message it asks a clarifying question or hands off to staff.

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.

A voice note can be transcribed, then understood and answered. We test this on samples of your customers’ messages, since background noise and fast speech can reduce accuracy, in which case the bot hands the chat to staff.

Yes. It can run only outside working hours to answer repeat questions and log orders, or all the time as the first line with handoff to staff during working hours. You choose what fits your message volume and team size.

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.

For the first three months after launch we fix any defect in what we delivered for free; after that, 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. The first three months after launch are free support to fix any defect in what we delivered; after that, monthly or yearly support plans cover 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.

It depends on the number of pages, languages, features (store, booking, customer area) and who writes the content. We send a written estimate after a short call; our pricing page explains the factors in detail.

Yes, we serve companies in every Iraqi governorate from our Baghdad headquarters.

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.

An ERP starts from $3,000, and core modules usually take 3 to 6 months. The final quote follows scope approval, as the pricing page explains.

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

Yes. Every transaction is recorded in its own currency, with revaluation, dual-currency reports and a daily exchange rate.

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

Yes. We migrate items, customers, suppliers and opening balances from legacy systems and Excel files after cleaning and reconciling them.

Yes. POS and the online store can be connected so a sale updates inventory and the accounts, as the service features describe.

Yes. The client owns the source code in full after delivery.

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

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

A sales or POS system records the sale after it happens: the invoice, the amount and the stock. A CRM manages what comes before and after: from the first WhatsApp message to the quote and follow-up, then after-sales service. Many companies need both, connected.

Yes, via the official WhatsApp Business API: chats are saved to the customer record, several staff can answer the same number, and follow-ups and reminders are sent from the system. Message fees are paid to Meta under its policy.

Cost depends on scope: the number of modules, WhatsApp and accounting integration, the field-rep app, data migration and the number of branches. You can start with a simple version for leads and follow-ups and expand later. We issue a fixed-price proposal after an analysis session, and our pricing page explains the factors in detail.

A practical first version usually takes 6 to 12 weeks, depending on integrations and the field app; the timeline is written into the proposal after the analysis session.

Yes, that is what the field-rep app is for: the rep sees the visit plan and each customer’s balance, records the visit with its location, takes the order and logs the cash collected, and management sees it as soon as the phone syncs, without waiting for the rep to return to the office.

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.

No. It is deployed in the cloud or on the company’s server, according to the scope written in the proposal.

From $1,200 over 4 to 8 weeks for one branch, as on the pricing page. Biometric hardware is set out in the proposal.

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 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.