AI Agents for Business
An agent that does the work in your systems, and stops where you would.
It reads the request, opens the order, changes the booking and writes the reply inside the software your team already runs. When money, a complaint or a promise you have not made comes into it, the decision goes to a person you have named.
What it did while you were doing something else.
A sample day in an online store, from the first unread email of the morning to the record that closes the evening.
Overnight messages answered from your policies
Questions that arrived after closing are read and answered from the rules you have written, before the first person on your team logs in.
14 threads · policies.pdf
An order changed in the store, the customer told
Lena B. asked to swap a size. The agent reserved the new one, issued the return label and wrote back with the dispatch date.
ORD-77310
A refund held for a person, approved from the phone
The return shipping refund waited for Daniel R. He approved it from his phone between two meetings, and the agent carried on.
phone
The day’s actions written to the audit trail
Each action of the day sits in one record with the time, the tool used and the person who approved it, ready to read or export.
31 entries · exported
Five jobs it does inside the software you run.
Choose a job to see the screen it leaves behind: the reply, the changed order, the held refund, the handed-over complaint and the record.
Answers from your written policies
Messages that came in after closing are read and answered from the rules you wrote, before anyone on your team logs in.
- SKSofia K.Do you ship on Saturdays?delivery policy
- CMClaire M.Can I return a gift without the receipt?returns policy
- LBLena B.Wrong size, can I swap it?order change
Changes the order in your store
Lena B. asked to swap a size. The agent found the order, reserved the new size, issued the return label and wrote back with the dispatch date.
- Customer
- Lena B.
- Item
- Size M delivered, size S wanted
- Stock
- Size S reserved
- Return label
- Issued
- Reply
- Sent with the new dispatch date
Holds the refund for a person
Money never leaves on the agent’s word. The refund is prepared with its reason and waits until the person you named approves it.
Hands a complaint to your team
A complaint is not the agent’s to settle. The thread moves to a member of your team with its full history, so the customer never explains twice.
- Customer
- Claire M.
- About
- A parcel that arrived damaged
- Handed to
- Sofia K., support
- Attached
- The thread, the order and her photos
Writes every action to the audit trail
Each action of the day sits in one record with the time, the tool used and the person who approved it, ready to read or export.
- 08:12Reply sent to Sofia K.inbox · delivery policydone
- 10:30Order changed for Lena B.orders.update · ORD-77310done
- 14:00Refund approvedrefund.hold → Daniel R.approved
- 15:20Complaint handed overthread → Sofia K.person
Four things it never does alone.
The agent prepares each of these, then stops and hands the decision to someone on your team.
Money leaving
Refunds, credits and payments are prepared with the amount and the reason, then held until the person you named approves them.
Anything about a complaint
The thread is handed to a member of your team with its full history, so the customer never has to explain twice.
A promise you have not written down
When a customer asks for something outside your written policy, a named person is asked before any answer goes out.
A record being deleted
The agent marks the record and states why; a named person confirms before anything is removed.
What the agent touches, and what it never touches alone.
Routine work runs by itself inside your tools. Money, complaints, unwritten promises and deletions wait for a person. Both sides land in the same audit trail.
Four things you always get.
Whatever the size of the work, these come with it.
A written brief
What we agreed to build, in one document.
A fixed price
Set in the proposal, before work starts.
Staging + approval
You see it and approve it before it goes live.
Documentation
How it works and how to change it, handed over.
Before you begin.
Send any other question in writing; a written answer follows within one business day.
Which systems can it work in?
The ones your team already opens each day: helpdesk, store, order system, calendar, email and accounts. The agent works through each system under its own account, with only the permissions the job needs, and every connection is listed in the written brief before we build.
Who approves money?
A person you name for each kind of action, for example a store lead for refunds and an owner for payments above a limit you set. The agent prepares the amount and the reason, and the approval is recorded under that person’s name.
What if it is not sure?
It does not guess. When a request falls outside your written material, the agent hands the thread to your team with everything it has read so far and notes the handover in the audit trail.
What do we own at the end?
The configuration, the connections, the documentation and the audit trail, all on accounts you control. The agent stays with you whoever looks after it later.
Not sure what you need? Ask in writing.
Describe the work in a few lines. We will reply in writing within one business day with what we would build and how.