Languages
Arabic and English
Answers from
Documents and data you approve
You decide
Where it appears and when it hands over to a person
Starts with
A list of the questions it must answer
AI Assistants & Chatbots

What it does

We build assistants for the questions your customers and staff ask every day. Each one is designed for one client: it answers in Arabic and English from the documents and data you approve, and you decide where it appears and when it hands over to a person.

A project starts with a list of the questions the assistant has to answer and the documents that answer them.

AI Assistants & Chatbots

Who it is for

  • Customer service lead

    Whose team answers the same questions every day, in two languages.

  • HR or IT helpdesk lead

    Whose staff ask about leave, policies and access, and want an answer that matches the policy.

  • Knowledge owner

    Who keeps the documents current and wants answers to follow them.

  • Website owner

    Who wants visitors to find an answer without waiting for an email.

AI Assistants & Chatbots

What we decide with you

There is no fixed feature list. These are the decisions a project settles.

What it answers from

  • Which documents, policies and pages it may use
  • Which data in your systems it may read
  • Who reviews and approves each source

How it behaves

  • Arabic and English, including right-to-left layouts
  • What it says when it has no source for an answer
  • When and how it hands over to a person

Where it lives

  • On your website, in your portal or in an internal tool
  • Who may use it: the public, customers or staff
  • How conversations are stored and who can read them
AI Assistants & Chatbots

Deployment and hosting

Where documents and conversations are processed and stored is a decision recorded in your proposal. If data must stay in the Kingdom or on your servers, say so at the start so the design begins from that.

One deployment per client

Each product runs as its own deployment for your company, with your branding, your data and your users. It is not a shared account.

Hosted by MUZN IT in Saudi Arabia

We run your deployment on servers in the Kingdom. Support levels, response times and update schedules are written into your agreement.

On your own servers

The deployment runs inside your own infrastructure. Whether your IT team or ours operates it day to day is agreed in the proposal.

In a cloud region you choose

If your organisation needs a region outside the Kingdom, we deploy there. The proposal states the location.

AI Assistants & Chatbots

How a project starts

  1. Your questions

    You list the questions it must answer and share the documents that answer them.

  2. Scoping session

    We confirm sources, channels, languages, the hand-over and where data must stay.

  3. Written proposal

    Itemised scope, milestones, how it will be tested and support terms. Nothing is charged until you approve it.

  4. Build, test and launch

    We build it, test it on your real questions with your team, then launch.

AI Assistants & Chatbots

Questions about assistants

How do we get one?

Send us the questions your team answers most often and the documents that answer them. We scope the assistant around them, and you receive a written, itemised proposal before anything is charged.

Which AI model do you use?

The model is a design decision for each project, taking account of language quality, where data may be processed and cost. Your proposal states it.

Can it give a wrong answer?

Yes, any assistant can. We limit it to approved sources, test it on your real questions before launch and design the hand-over to a person. We do not publish accuracy figures.

Where does our data go?

Which sources are used and where they are processed and stored is recorded in your proposal. If data must stay in the Kingdom or on your servers, tell us first.

Can it work in Arabic and English in the same conversation?

It is designed for both languages. How it chooses between them for your users is settled at scoping.