agents that run processes end to end.
Our AI agents read the email, find the record in your ERP, catch the mismatch, ask for approval where it's needed and close out the work. You step in only where a decision is required.
- Runs on top of the tools you already use
- Human approval at critical steps
- Every action in the audit trail
Click a completed step to see its call and result.
- tool call
- mail.read({ inbox: "ap", id: "msg_8f21" })
- result
- pending…
Reasoning: Found a PDF invoice attached to the message from Northfield Supply.
Variance €300: 1,200 units × €0.25
- Read the email
- Parsed the invoice
- Matched it to the PO
- Flagged a price variance
- Requested approval
- Posted the entry
- Notified the team
Found a PDF invoice attached to the message from Northfield Supply.
mail.read({ inbox: "ap", id: "msg_8f21" })09:14:02
when rules break, work goes on.
Classic automation follows pre-written rules; when something unexpected happens, it stops and drops the work into a queue. An agent reads the situation, gathers context and decides what to do within set boundaries.
The supplier sent the invoice as a scanned PDF. The invoice has no PO number; it only appears in the body of the email. And one line item's price differs from the PO.
Hello, the attached invoice belongs to your order PO-7710. Kind regards.
INV-20931.pdf · scanned
- 1Attachment downloadedPDF saved to a folder.
- 2PO number field unreadableThe template field is empty; the scanned document has no text layer.
- 3Matching skippedThe rule can't continue without a PO number.
- 4Dropped into the error queueWaiting until someone notices.
- 1Read the documentExtracted line items and amounts from the scanned PDF.
- 2Found the missing dataPulled the PO number from the email body: PO-7710.
- 3Spotted the varianceNS-4410 has a price variance outside tolerance.
- 4Sent it for approvalSummarized the variance, checked with the authorized approver and posted the entry once approved.
- Ambiguous inputStops on documents outside the templateReads the document and fills gaps from context
- ExceptionsEvery exception needs a new ruleDecides within policy, and asks when outside it
- Cross-tool workOne trigger, one actionWorks step by step across multiple systems
- ChangeBreaks when the screen changesWorks through APIs and authorized tools
- TraceabilityOften just an error logEvery decision logged with its reasoning
pick a process, watch the agent.
The flows below are examples we build often. In each one the agent moves step by step across the systems your company uses, stops at the step that needs approval and waits for your decision.
CONNECTED SYSTEMS
AGENT TRACE
0/6- 1Mail+00:00
Recognized the invoice attachment and the sending supplier.
› mail.read({ inbox: "ap" })
- 2Docs+00:02
Extracted line items, tax and totals from the PDF.
› doc.extract({ file: "INV-20944.pdf" })
- 3ERP+00:05
Ran a three-way match against the PO and delivery note.
› erp.match({ po: "PO-7731", receipt: "GRN-3302" })
- 4ERPhuman approval
Sent the out-of-tolerance price variance for approval.
› approval.request({ rule: "price_tolerance" })
- 5ERP+00:08
Posted the approved invoice as an accounting entry.
› erp.journal.post({ entry: "AP-5520" })
- 6Slack+00:09
Posted a summary and the entry link in the finance channel.
› slack.post({ channel: "#finance" })
OUTCOMEInvoice matched to the PO, entry posted, team notified.
tool calls: 0 · human decisions: 0 · all in the audit log
the agent works, you stay in control.
Every agent runs with defined permissions, limits and approval steps. What it did, why it did it and who approved it are all on record, and a single click stops it when needed.
Change a setting: the verdicts on pending actions and the audit log update right away.
Approval steps
- Out-of-tolerance invoicePrice variance above 2%Finance lead
- Amount above limitPayments and refunds over the per-transaction limitManager
- First customer replyFirst message sent with a new templateSupport lead
Role permissions
Click a box: the permission changes right away and is logged.
Action limits
32 actions in the last hour
Pending actions
- invoice-agentPost invoice INV-20944 to the ERPBaltic Freight · price variance 4.1%€3,480Goes to approval · Finance lead
- support-agentRefund return R-1182Order SO-10482€640Automatic
- support-agentRefund return R-1190Bulk order SO-10477€8,200Goes to approval · Manager
- sales-agentUpdate the opportunity stage in the CRMKestrel Labs · quote sent—Blocked · no permission
- support-agentSend the first reply to the customerRequest T-3310 · new template—Goes to approval · Support lead
- invoice-agentRetry entry AP-5521ERP timeout · attempt 5—Blocked · retry limit
Emergency stop
Stops all agents immediately. Unfinished work is saved and waits until it's resumed.
- invoice-agentrunning
- support-agentrunning
- sales-agentrunning
Audit log
- 10:42:18invoice-agentEntry AP-5518 posted to the ERP · approved by Clara Wendt
- 10:41:57clara.wendtINV-20931 price variance approved
- 10:39:03support-agentRequest #3304 routed to the priority queue · reason: complaint
- 10:36:44sales-agentNo write permission; CRM update suggested to the rep
we measure first, then we scale.
We start with a single process. We measure the result in a pilot, then widen the scope and the agent's permissions step by step once your team is ready.
Discovery
We talk with your teams and map the repetitive processes that involve rules and exceptions. Together we choose which ones suit an agent.
DELIVERED IN THIS PHASE
- Process inventory and prioritization
- Systems and data access list
- Success criteria
Chosen for the pilot: Invoice matching
questions about agents.
How agents are kept in check, which systems they work with and how a pilot starts.
Let's look at your process
Discovery call
If your question isn't answered here, write to us. We can go through the details of your process together.
Send an emailThe agent acts only within the permissions and limits you define. It asks for approval at critical steps and stops to ask when a case falls outside the policy. Every decision is logged with its reasoning, and all agents can be stopped with a single button.
No. Agents work on top of your email, ERP, CRM, e-commerce, document and support channels, through APIs and authorized tools.
A rule-based flow stops on a non-template document or an unexpected exception and drops the work into a queue. An agent reads the document, fills gaps from context and decides within policy; when a case is outside the policy, it asks.
Repetitive processes that involve rules and exceptions and move across several systems. In discovery we map your processes with your teams and choose the right one together.
Discovery takes 1–2 weeks, the process map 1 week and the pilot agent 3–6 weeks. The pilot agent runs first in observation mode, then with limited permissions; permissions grow gradually against the criteria set in the pilot.
Yes. In the handover phase we teach your team to run the agent. If you prefer, we keep handling monitoring, updates and new processes.
LET'S START
let's pick your first process.
Tell us about the process your team spends the most time on. We'll assess together whether it's a fit for an agent, and what kind of pilot it could start with.