Skip to content
Wakeel

Hire it, brief it, set its limits

There is no bot to build and no workflow to draw. An employee arrives knowing its job. What it does not know yet is your business - and that is what you tell it.

From hiring to the record

Step 1 of 7

One screen: a name, a voice, and what it will know, filled in from your Brain. The rest is asked on its page later.

The screens are from a sample business.

Hiring a Support Agent on one screen: a name and whether it speaks as a woman or a man, then what it will know about the business - the company, opening hours, rules, language - each filled from the Brain and saying where it came from.
  1. A name and a voice, from the role's card - yours to change.
  2. What it will know, filled in from your Brain, each fact saying where it came from.

You set the limits. The system enforces them.

Each skill an employee has sits at one of four levels, and you choose which. The limit is enforced by the platform on every action - it is not a request the AI may ignore - and each action records the level that applied and why.

  1. L0 · Suggests onlyPrepares the reply or the action, and leaves the doing to you.
  2. L1 · Drafts for approvalPrepares the work and places it in your approvals list. Nothing happens until you say yes. Refunds, invoices and messages to customers start here.
  3. L2 · Acts, then tells youDoes it, then lets you know what it did.
  4. L3 · Acts within a budgetGets on with it quietly, as long as it stays within the budget you set.
An employee's skills, each with the four levels of the trust ladder laid out across, the chosen one marked.
A level for each skill, chosen on the ladder itself.

Approve from wherever you are

Everything that needs a person waits in one list: what the employee wants to do, the order and the amount, why it is asking instead of acting, and three choices - approve, edit and approve, or decline. The same card works on your phone, and on WhatsApp if you would rather not open anything.

An approval card: the refund at its level, the order number and amount, why it is waiting, the drafted details, and Approve, Edit and approve, and Reject.
What it will do, why it is asking, and your three choices - in a sample business.
Home on a phone: the refund fills the screen, Approve, Edit and Reject under the thumb, the next decision a swipe away.
A sample business on a phone: one decision to a screen.

Test it before customers meet it

Write down what a good conversation looks like - what a customer says, and what must be true afterwards - and run it. Each check passes or fails with the full conversation beside it. Change the employee after a passing run, and you are told the result is out of date.

The sandbox: a rehearsal where nothing leaves the business. Asked for the V60 dripper, the employee answers with the price and a source; beside it, what it may do and at which level.
Try it the way a customer would. Nothing leaves the business.
A finished run of the employee's test scenarios: passed, 10 of 10, on the published version, each scenario by name - a damaged order, a request for a person, questions it should decline.
Scenarios run against the real employee, and say which checks passed.

Then see what it did

This is one row of the record, and it looks the same wherever the action appears - in a conversation, on a task, in the approvals list. One account of what happened, everywhere.

A WhatsApp conversation in the console: Reem asks how long delivery to Jeddah takes; the answer from the Brain is open beside it, with the passage it used, the document it came from and how closely it matched.
A conversation in a sample business shows what the employee did where it did it - and what it answered from.
The audit log: actions, each with its trust level, the skill in plain words, its status and when it ran.
The audit log. Every action and the level it ran at, recorded before it ran.

Changes stay in draft until you publish

Customers keep talking to the version you published while you edit. Every version is kept, with who published it, what changed and why - and you can restore an earlier one in a click.