Customers now expect a quick answer at any hour, whether they ask about a service, an order, or an appointment. Many of those questions repeat, and they can be answered accurately when the information is organized. At Al-Narjis we design intelligent chatbots that understand formal Arabic and the Saudi dialect, and that rely on information your organization has approved, so they answer your customers clearly and politely.
The bot we build is a front for information you have accepted: the service guide, the policy, and the questions people ask again and again. If the question leaves that scope, the bot stops guessing.
The value is taking the repeated question off the employee, not hiding the employee from the customer. These are the uses we usually build, after the approved text is agreed.
We take care that the bot reflects your identity and tone: formal when it should be, warmer when that fits. We build its answers on sources you approve, such as the service guide, the policies, and the frequently asked questions, so it does not present inaccurate information. When it does not find a reliable answer, it says so and hands the question to your team instead of guessing.
Tone is not decoration added at the end. We agree the words you use, the words you do not want, and when a reply should be short. The approved source is reviewed before launch, because the bot will repeat it. Handover to a person is part of the design: a complaint, an exception, or a request outside the approved text is passed on, with enough context for the employee.
Gathering the knowledge: we collect the information the bot will rely on and put it in one source you can update.
Designing the conversation: we set the scenarios, the tone, and when a person takes over, including a path for when the bot does not know, so the customer is not stuck in a loop.
Build and connection: we build the bot and connect it to your site or to channels you have agreed. We do not assume a channel you have not agreed.
Testing: we test with realistic questions in formal Arabic and in the local dialect, including the incomplete question and the question that is out of scope.
Follow-up: we review anonymized conversations for questions that kept arriving without a reliable answer. The review is not a way to track a named person.
The bot tells the user it is an automated assistant, and it collects only the data the enquiry needs. We design the solution with regard to the Personal Data Protection Law in the Kingdom, and the retention policy can be set to suit your organization.
Before launch we ask what is stored, for what purpose, for how long, and who can see it. If the enquiry can be resolved without a name or a number, we do not make those fields mandatory. The customer sees that they are talking to an automated assistant from the start, not after they have sent their details.
You can try what we offer directly. The Al-Narjis bot on our site is a live example of the chatbots we build. Ask it about our services and see how it behaves. It answers from the site's information, and it hands you to email when it does not have a reliable answer.
That trial shows the shape. It is not a copy of your organization's bot. Yours is built on your knowledge, your tone, and your limits. What you borrow from the example is the behavior: a clear answer when the information exists, and an honest handover when it does not.
Because we are a Saudi team that understands how customers in the Kingdom speak. We care about the quality of Arabic in every answer, and we design the bot to be a reliable assistant rather than a source of confusion. We read the sentence as a customer in Riyadh would read it, not as a tool emits it with no review.
If a repeated question sits on top of a tiring internal procedure, such as logging a request and routing it, that is automation work and not the bot alone. We connect the two services when the connection is clearer than building two fronts that do not speak to each other.
We design and test the bot so it understands formal Arabic and expressions that are common in the Saudi dialect. The test uses realistic questions, not only a term list.
Yes. It can be added to your site, and we discuss any other channel that fits. We do not assume a channel we have not agreed.
It tells the customer, and it hands the enquiry to your team instead of offering an unconfirmed fact.
Yes. We design the knowledge sources so they are easy to update when your services or policies change. Updating is part of the design, because the text will change.
Try the Al-Narjis bot on the site and ask it to put you in touch with us, or email us.
Operated by Al-Narjs · Freelance document No. FL-272182297 · Riyadh
· AlNarjisai@gmail.com
Privacy ·
Terms ·
Data deletion ·
Refund policy ·
Pricing ·
About ·
Contact