What it must know
Your products, prices, rules, exceptions and the way your team phrases things. This is the part that makes the difference between a plausible answer and a correct one.
Built around how you work.
Most AI you can buy asks you to change your process to fit it. We go the other way: we start from the way your company already runs, and build the agent into that. Vekil and Bekir are two results of this; yours will look like yours.
What actually gets decided.
A custom build is not a bigger prompt. Four things get defined, and they are what make the agent yours rather than generic.
Which systems it reads
Whatever holds the truth: your database, order system, calendar, stock. The connection is read-only — the agent answers from the source instead of guessing.
What it may decide
Where its authority ends. Which discount it can give, which appointment it can confirm, which commitment it must never make on your behalf.
Where it stops
The handover rule. The moment a conversation needs a person, it tags you and stops — without leaving the customer waiting.
How a build goes.
Scope comes before commitment. We would rather tell you on the first call that something is not worth building than discover it in week three.
-
01
Intro call
Thirty minutes. You describe the problem; we say plainly whether it is a week of work, a larger build, or something you should not automate at all.
-
02
Scope
We write down what the agent will know, read, decide and refuse. This document is what we both agree to — not a vague statement of intent.
-
03
Contract
NDA and service agreement. Data boundaries, access permissions and retention period are put in writing before anything is connected.
-
04
Build and train
Your information, tone and rules go into the agent; the read-only connections are made. Your isolated instance comes up.
-
05
Supervised launch
It goes live on a real line but supervised — you approve as it goes. Authority widens as you get comfortable.
-
06
Handover
It runs on its own. We stay on for changes, new rules and the things your business only discovers later.
What we will not build.
Saying no early is part of the job. These are the cases where we will tell you to keep a human in the seat.
01 Binding commitments
An agent that can sign your company up to something. Vekil deliberately cannot; nothing we build will either.
02 Medical or legal advice
Diagnosis, treatment, dosage, legal opinion. The agent can carry information to a professional; it does not replace one.
03 Decisions with no source
If the answer does not exist in any system or document you have, the agent will say so rather than invent it. We will not fake a data source.
04 Pretending to be a person
How an agent introduces itself is configurable, but we will not build something designed to deceive in a sector where that is not allowed.
05 Write access to your systems
Read-only is not a limitation we ran into; it is a rule. An agent that can modify your source data is a risk we do not take on.
06 Anything you cannot exit
No build that traps your data. Memory is exportable and deletable from day one.
Same foundations as the built agents.
Custom does not mean looser. Everything that protects Vekil and Bekir protects your build too.
01 Isolated instance
Your company runs in its own separate instance. No customer's data ever shares a memory with another's.
02 Encrypted memory
WhatsApp traffic is end-to-end encrypted, and the agent's own memory is encrypted at rest.
03 NDA first
Signed before anything connects. Where the data sits, who reaches it, how long it is kept — all in writing.
04 No model training
Your conversations are not used to train general models. Learning happens only in memory that belongs to you.
Frequently asked
How long does a custom build take?
If your case is close to an agent we have already built, roughly a week. Beyond that it depends entirely on scope — which is exactly why we scope it in writing before either side commits.
What does it cost?
A corporate monthly subscription based on the number of agents, systems connected and conversation volume. Custom builds are scoped first and we give a firm number on the call — no figure invented before we understand the work.
Do we need technical people on our side?
For the conversation itself, no. If the agent needs to read one of your systems, we will need someone who can grant a read-only connection — usually one short session.
Can it work somewhere other than WhatsApp?
WhatsApp is where we run today and what this site describes. If you need another channel, raise it on the call and we will tell you honestly whether it is in scope.
What if it turns out not to work?
You stop. Memory is exported and, on request, deleted in full. We would rather lose the build than have you stuck in one.
Who owns what gets built?
Your data and the memory are yours — exportable and deletable at any point. Commercial terms for the build itself are set in the service agreement.
Describe the problem. We will tell you if it is buildable.
Thirty minutes is enough to know whether this is a week of work, a bigger build, or something you should not automate at all. We will say which.