Qmakes Solutions

AI agents for operations

Your busiest work, done by an AI that isn't allowed to make costly mistakes.

We build AI agents that run your CRM, customer service, email, chat and daily operations. The AI does the work. Hard limits in the software stop it from doing damage. Anything unclear comes to a person.

English and Arabic. Remote, worldwide.

52%of a 7-person team's work, done by one agent in high season
50–300live bookings handled a day
~10%handed to a human, each for a real reason
0wrong actions in its last 4 months in production

What we automate

If your team does it the same way every day, an agent can do it.

We connect to the tools you already use. No API? We build the connection ourselves, so even an old CRM or web system can be automated.

CRM work

Tagging, updating, pricing and routing records, under rules you set per city, team or client.

e.g. tag every new booking and adjust its driver offer within a safe range

Customer service

An agent answers on WhatsApp, chat or email, books and changes orders, and sends payment links.

e.g. a WhatsApp agent that quotes, books and confirms in English or Arabic

Email and inboxes

Read, sort, draft and reply. Urgent or unusual messages go straight to a person.

e.g. rate every enquiry Hot, Warm or Cold and alert sales on the hot ones

Live operations

Watch timers and live cases, notify drivers or staff, and escalate before something is late.

e.g. a flight is delayed: warn the customer, get consent, recheck the driver

Team tools

Slack, Google Sheets, Intercom and webhooks, joined into one flow instead of copy and paste.

e.g. a case closed in the CRM posts to Slack and logs to a sheet

Systems with no API

A browser extension that works inside your existing web system, the same way your staff do.

e.g. LiveOps, below, ran inside a CRM that had no automation at all

Proof

LiveOps: an operations agent that ran in production for months.

Our founder, Q, built LiveOps while working live operations for an international airport-transfer company (under NDA, so names and data are blurred). It worked inside the company's CRM, which had no API for this, and tagged and priced bookings across dozens of cities.

Results
  • 50–300 bookings a day, depending on the season.
  • 52% of the team's tags in high season. The other 6–7 people together did 48%.
  • Zero wrong actions over its last 4 months in production, after the initial build-and-training phase. Not because the AI never errs, but because the software won't let an error through.
  • About 10% escalated (5–30 cases a day), each for a real reason.
  • It learns from every escalation. One plain instruction ("from now on, close any assigned transfer") is written by the AI into its own instructions and examples.
  • Supervised from a phone through a paired Android app: see every case, pause the agent, or step in.
LiveOps auto-tag history: each booking with its city, result (Tagged, AI Tagged, Filtered) and a one-line reason for the decision
Every decision is logged with its reason. "Filtered" cases were held back for a person.
Per-city rules editor with price tiers, car types, time windows and a safety limit
Rules per city, with a safety limit the AI cannot go past.
Escalation chat: the AI asks for review, the supervisor answers, the AI records the reason and closes the case
An escalation: a person answers once, and the AI states its reason and acts.
LiveOps Remote Android app showing the live dashboard and one open booking with its price plan
The remote app: the live dashboard in a pocket.
Next

Ops Agent Core: the agent and the CRM, built together

LiveOps had to work around a CRM it didn't control. Ops Agent Core is the next step: a WhatsApp customer-service agent with its own CRM, built for a transfer business. The AI talks; the CRM decides prices, payment links, bookings and driver dispatch. A customer who tricks the AI still can't get a discount, a fake payment link or someone else's booking.

It includes a flight-delay flow where the customer's "yes" is checked by the CRM, not the AI, and a live console for staff. Every action goes through an API, so it plugs into your other systems.

Status: working demo, all automated tests passing; first live run this month.

Why it's safe

The AI talks. The system decides.

An AI on its own will eventually make a mistake. So the limits don't live in the AI's instructions. They live in the software around it, where it can't talk its way past them.

  1. Hard limits outside the AI.It never lowers a value below the current one, never raises it above a ceiling, never overrides a person.
  2. Unsure means ask, not guess.A broken or unclear action is rejected, nothing runs, and the case goes to a person with the reason.
  3. Facts come from your system.Prices, links and booking details are filled in by your CRM, never typed by the AI.
  4. Everything is logged.Every action has a one-line reason you can read, so you can audit it any time.
  5. You stay in control.Pause it, override it, or change a rule from your phone.

How we work

Start small, prove it, then grow.

1. Free call

20 minutes. You show us the task that eats your team's day. We tell you honestly if an agent fits.

2. Fixed-price setup

We build the agent, the limits and the connections to your tools, priced up front.

3. Supervised start

It runs on your real work with a person checking, until the numbers say it's ready.

4. Monthly running

A monthly fee covers running, monitoring and new rules as your business changes.

Who we are

A small team of software engineers who have done the work our AI agents now automate.

Qmakes is led by Yasser Gad (Q), an AI and automation engineer: computer engineering, years in IT, sales and customer support, then live operations, where he built LiveOps to do his own job better. We've been on both sides: the people doing the repetitive work, and the people automating it. We build with our own team of AI agents, and a person on our side is accountable for everything that ships. English and Arabic.

Get in touch

Tell us about the task your team repeats every day.

A short email is enough: what the task is, which tools you use, and roughly how many a day. We reply within one working day.