Skip to content

Service

AI agents

Chat and messaging assistants for websites, WhatsApp and other channels, built on your own content and rules, with a clear path to a person.

Problems this solves

  • Your team answers the same questions about hours, prices, availability and orders all day.
  • Enquiries arrive outside working hours and wait until someone is back.
  • Useful details (name, need, timing) are missing when a person finally picks up the conversation.
  • Customers write in Arabic and English, and replies are inconsistent between the two.

What we typically deliver

  • A conversation design: what the assistant handles, what it never answers, and when it hands over.
  • A knowledge base from your approved content, kept separate so you can update it.
  • The assistant connected to your channel (website chat, WhatsApp Business or similar).
  • Hand-over to a person with the conversation summary attached.
  • A test set of real questions, reviewed with you before launch.
  • A short guide for your team on reviewing conversations and updating answers.

How it can work

An assistant that answers common questions from approved content, captures the details you need and hands over to a person when it should.

  1. A customer asks

    In chat or WhatsApp, in Arabic or English.

  2. The assistant answers from approved content

    It does not guess. Anything outside its scope is flagged.

  3. It captures what you need

    Name, request, preferred time, and anything else your team asks for every time.

  4. A person takes over when needed

    With a summary, so the customer never repeats themselves.

Is it a good fit?

A good fit when

  • You receive many similar questions through chat, WhatsApp or email.
  • The answers already exist somewhere: a price list, a policy, a FAQ.
  • Someone on your team can review conversations for the first weeks.

Probably not the right fit when

  • Every conversation needs expert judgement (medical, legal or financial advice).
  • You have very few enquiries and they are all different.

How we work

From first conversation to support

Small, visible steps. You see working pieces early and decide what comes next.

  1. Discover

    We look at how the work happens today, where it gets stuck and what a good result would look like for you.

  2. Define

    We agree what to build first, what is out of scope, and how we will both know it works.

  3. Build and test

    Short iterations using real examples from your business. You see working pieces early.

  4. Launch and support

    We go live with a clear hand-over, then adjust as real use shows what to improve.

Ways to work together

Engagement options

We agree scope and price for each piece of work after a first conversation. There are no fixed packages.

  • Focused project

    One clearly defined piece of work with an agreed scope and finish line.

    Good for
    A single assistant, workflow, landing page or tool.

    Includes

    • Short discovery and written scope
    • Build, testing and launch
    • Hand-over notes
  • Phased build

    A larger goal split into phases, each one usable on its own before the next begins.

    Good for
    Connecting several processes, or a website plus automation and an assistant.

    Includes

    • A roadmap with agreed phases
    • A review at the end of each phase
    • Freedom to stop or change direction between phases
  • Ongoing support

    Regular care for what we have built: monitoring, small changes and improvements.

    Good for
    Assistants and automations that need tuning as your business changes.

    Includes

    • An agreed monthly allowance of time
    • Monitoring and fixes
    • Suggestions based on real use

Questions

It is limited to your approved content and told what not to answer. We test it with real questions before launch, and it hands over to a person when it is unsure. Reviewing conversations in the first weeks is part of the work.

We agree this before building: which platform and model provider are used, what is stored, for how long, and who can see it.

Yes. We write, design and test in both, including right-to-left layouts and replies that read naturally in each language.

It depends on scope, so there are no fixed packages. After a first conversation we send a written scope and price for the first piece of work.

Start an AI agent project

Describe what you have today and what you want to change. A short message is enough to start.

Other services

  • Business automation

    Problem
    Work moves between tools by copy and paste, and things get missed.
    Outcome
    Connected workflows that capture, route and follow up on their own, with a clear record of what happened.
  • Websites and landing pages

    Problem
    Visitors cannot tell quickly what you do or what to do next.
    Outcome
    A fast, clear site in two languages that explains what you offer and makes the next step obvious.
  • Custom tools and integrations

    Problem
    Your tools do not talk to each other, and off-the-shelf options almost fit.
    Outcome
    A small purpose-built tool or integration that fills the gap and stays maintainable.