AI Agents With a Fixed List of Actions
An AI agent is given one bounded task and a fixed list of actions. It can collect details, look up a record, update one field or notify a person; anything else is refused.
Jobs that suit an agent
- Taking a service request, checking the warranty status, raising a job card
- Following up for a missing document until it arrives, then closing the task
- Checking a delivery against its order and telling the branch what is short
- Reading a status question and replying with the current position
Guardrails built into the agent
Every action an agent can take is listed in advance. Anything absent from the list is not possible. Limits apply to the rest: a value above which approval is required, records it may read but never change, and a stop after a set number of attempts. Everything the agent does is logged, so a disputed action can be traced to the request that started it.
What stays with a person
Money, promises and anything a customer would treat as a commitment stay with your staff. That covers prices, credit terms, refunds, discounts and cancellations. An agent may prepare each of these and hand it over. None of them leave on its own authority. That line is drawn before development starts.
Frequently asked questions
How is an AI agent different from a chatbot?
A chatbot answers questions. An agent acts in your systems: it creates a record, updates a status or sends a notification. For that reason the list of permitted actions matters more than the conversation.
Can an agent change records in our ERP without approval?
Only the fields you have allowed, and never beyond the limits you set. Anything else is prepared and left for a person to approve.
Who is responsible when an agent gets it wrong?
It depends on the cause. You remain responsible to your customer, which is why the scope is kept narrow and every action is logged. A fault in what we built is ours to fix, and the log shows which case applies.
Which details are needed to scope an agent?
A task somebody does repeatedly, the systems it touches, and a clear statement of what it must never do. The last item usually takes longest to agree, and it sets the limits.
Tell us what you need.
Share your requirements and one of our engineers will come back to you within one business day.
What happens after you share your requirements
- A senior engineer reads your answers. Nobody phones first.
- Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
- If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
- No call is booked and nothing is paid until you have read the note. Your details stay with us.
Start with your requirements
Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.
Share your requirements