Back to Knowledge Center

Intelligent workflows

AI Agent (AI agent)

A system that uses models, knowledge and tools to complete multi-step tasks within defined instructions and permissions, choosing subsequent actions from execution results.

Last reviewed · 2026-07-15Verified sources

01

One-sentence definition

It does more than answer questions; it can use tools to advance a controlled workflow.

02

What problem it addresses

It fits repetitive, describable and verifiable processes, but requires clear permissions, exception handling and human oversight.

03

Fit and non-fit

Good fit

  • Repeatable, rule-bounded workflows spanning multiple tools
  • Teams able to set permissions, exception handling and human takeover

Not a fit

  • Tasks with vague goals, shifting rules and unverifiable outcomes
  • Unsupervised autonomy in high-risk environments

04

Prerequisites

01

Clear task, success and stop conditions

02

Tool permissions, data scope and audit requirements

03

Evaluation set, exception handling and human takeover

05

Inputs and outputs

InputsOutputs
Workflow steps and decision rulesAgent workflow and responsibility boundaries
Tool, knowledge and permission configurationEvaluation, logs and exception records
Test cases and risk scenariosLaunch, rollback and human-takeover plan

06

Standard steps

01

Research organization

02

Drafting and review routing

03

Monitoring summaries and internal Q&A

07

Decision criteria

01

Models, tools and instructions form the system

02

Permissions and data boundaries must be explicit

03

Keep logs, evaluation and human takeover

08

Common failure modes

01

An agent is simply a chatbot

02

Connecting more tools is always better

03

No ongoing evaluation is needed after launch

09

Metrics

01

Task completion rate

Share of tasks completed correctly within defined conditions.

02

Human takeover rate

Share requiring human intervention due to uncertainty, exceptions or risk.

03

Severe errors and permission breaches

Incorrect execution, data exposure or actions outside authorized scope.

10

Case anatomy

From suggestions to controlled execution

Context

A team wanted to automate repetitive work, but incomplete inputs and exceptions were common.

Approach

Task boundaries and evaluations were defined first, tool permissions were expanded gradually, and human confirmation remained before critical actions.

Key lesson

An agent is defined less by tool count than by reliable completion within boundaries.

11

Tools and templates

Agent task card
Permission and risk matrix
Evaluation and exception log

12

Revision history

Version 2.0

2026-07-15

Upgraded to a deep knowledge unit with fit boundaries, inputs and outputs, metrics, a case and claim-level evidence.

Related terms

Evidence and sources