Hilla · Babil · Iraq
Nawah builds Arabic-first systems — not translated interfaces, and not imported products that ask a local shop to adapt to them. We start from how an Iraqi customer actually behaves, then write the system around that.
هلو، شكد سعر الجاكيت الجينز الأزرق؟
أهلاً بيك. الجاكيت الجينز الأزرق بـ 35 ألف دينار، متوفر قياسات M و L و XL. التوصيل داخل بغداد 5 آلاف ويوصلك خلال يومين.
وإذا أريد أرجّعه بعد شهرين؟
Escalated — the return window is 14 days and this falls outside it. Needs your decision.
Our first product
A bot that answers Instagram and Facebook messages and comments on behalf of shop owners in Iraq. It builds its knowledge from the shop's own posts and past conversations, and shows that knowledge to the owner in a dashboard to review and correct — before a single customer sees a reply.
The platform is in testing with a limited number of shops. We open seats gradually so we can watch reply quality in each vertical before scaling — because a bot that answers your customer wrongly costs more than it saves.
Why Nawah
Building a bot that replies to a message takes a week. Building one you would trust with your customers' conversations is a different problem — and these are the decisions that separate the two.
We do not rely on a developer remembering to add a filter to every query — forgetting is a matter of time. Isolation is enforced by the database itself: a policy on every table that stops a single row from crossing between shops, and an application account with no power to disable or bypass it.
FORCE ROW LEVEL SECURITY · no BYPASSRLS
Every model call is written to a permanent ledger. The application's rights on that ledger are insert and read only — no update, no delete — enforced in the database rather than promised by us. A log its owner can erase is not a log.
usage_ledger — INSERT + SELECT only
The difference between a clothing shop, a restaurant and a services office lives entirely in one row of data: the instructions, the examples, the order fields, the escalation rules, the word for what you sell. A new vertical is a new row — not a new release, and not a month of waiting.
industry_packs — a row, not a release
When the answer isn't in your shop's knowledge, it doesn't invent one. It stops itself, escalates the conversation to you, and flags it as needing a human. An invented price or an imagined return policy costs you a customer; a two minute delay costs you nothing.
action: escalate | unknown
How it works
Connect a Facebook Page or Instagram account in one click through Meta's own login. You never share a password with us, and you can disconnect at any time.
We read your posts and past conversations and extract the products, prices and policies, then show you what we understood so you can correct it before anything else happens.
The platform stays in review mode: you see every reply before it is sent. When you are satisfied, you turn on automatic sending — and turn it off any moment.
What we build
We don't hand over a system we wouldn't run ourselves. The standard is the same on every project: automated tests that pass before any deploy, data isolation enforced at the database, and operational documentation good enough to hand the system to another team.
Platforms serving many customers with isolated data, and Arabic admin panels a business owner can use without training and without a manual.
iOS and Android from design through store approval — including the review requirements, privacy policies and support pages that apps are usually rejected over.
Language models placed inside a real workflow: answering customers, extracting knowledge from existing content, and clearing repetitive work — with a ledger of every call and what it cost.
Contact
We normally reply within one business day. For questions about data and privacy, see the Privacy Policy.