/

Agentic AI

Agentic AI

Agentic AI is artificial intelligence that decides its own steps toward a goal. Rather than producing an output and stopping, an agentic system plans, acts on external systems, evaluates what happened, and adjusts until the goal is met or it hands over.

Agentic AI describes a property rather than a product: how much of the work the system decides for itself. The term covers everything from a single agent calling one tool to a set of agents dividing a case between them. Don't confuse it with AI agent (the system) or automation (a path set in advance).

How does agentic AI differ from generative AI?

Generative AI produces something: text, an image, code. Agentic AI decides what to do and then does it, which usually includes generating something along the way. The distinction is autonomy over the sequence rather than sophistication of the output.


Generative AI

Agentic AI

Decides the steps

No, you prompt each one

Yes, it plans its own

Touches other systems

Rarely

Routinely, through tools

Knows when it is finished

When the output is produced

When the goal is met, or it escalates

Main failure mode

Wrong or invented content

Wrong action, repeated at speed

That last row is why the two need different controls. A generative system that gets something wrong produces a bad sentence. An agentic system that gets something wrong can submit a bad chargeback that exposes a bank to regulatory risk, and then submit forty more before anyone looks.

What does agentic AI look like in financial services?

Most financial services processes were designed as sequences of human decisions, each with a policy behind it. That shape suits agentic systems, because the decisions are already written down, and it explains why adoption has clustered in operations rather than in marketing or content.

Where it commonly shows up today:

  • Disputes: classifying a claim, gathering evidence, and submitting to the scheme

  • Collections: assessing affordability, agreeing an arrangement, and following it up

  • Onboarding: chasing documents, handling verification exceptions, and clearing the case

  • Frontline support: resolving account queries that need a lookup and an action

Across all four categories, there is a similar pattern: a case arrives, the system reads the policy, gathers what it needs across several tools, and produces a decision with the reasoning attached. Our guide on taking AI agents from pilot to production covers how teams sequence that.

What are the risks of agentic AI in regulated operations?

Every risk in a generative system is still present, and autonomy adds three more. The first is scale of error, because an agent working a queue can repeat one bad judgment hundreds of times before review. The second is irreversibility, since some actions cannot be taken back once a payment moves or a decision reaches the customer. The third is explainability: a system that chose its own path has to show why it chose it.

Regulators have not needed new vocabulary for any of this. The obligations sit in existing rules on controls, oversight, and outsourcing, and PRA SS2/21 is explicit that using a third party does not reduce regulatory responsibility. Writing a control narrative for an agentic deployment is largely a translation exercise from vendor language into that existing framework.

What needs to be in place before deploying agentic AI?

Readiness is mostly about constraints rather than capability. The question is not whether the system can act, but whether anyone can say precisely what it may do, prove what it did, and stop it. A workable baseline:

  • Written scope: the cases the agent handles, and the cases it never touches

  • Action limits and approval gates: which tools it may call alone, and which decisions a person signs off

  • Guardrails running on every turn, in both directions

  • Evaluation before and during production, not only at procurement

  • A rollback path: how you turn it off, and what happens to cases in flight

Teams that skip the scope document tend to discover it later, usually during a control review. Our guide to evaluating AI agents covers the testing half of this.

Frequently asked questions

Is agentic AI the same as an AI agent?

Not quite. An AI agent is the thing: a specific system pursuing a goal. Agentic AI is the adjective form, describing systems that decide their own steps. A deployment can be more or less agentic depending on how much latitude it has, so the word marks a spectrum rather than a category.

Is agentic AI safe for regulated financial services?

It can be, under conditions. Safety comes from the controls around the system rather than the model inside it: scoped permissions, guardrails on every turn, human oversight where harm is foreseeable, and a complete audit trail. Deployments that skip those controls are not safe, however capable the underlying model.

What is the difference between agentic AI and workflow automation?

Workflow automation runs the path you draw. Agentic AI chooses a path at runtime, based on the case in front of it. Automation is more predictable and breaks when reality departs from the diagram, while an agentic system handles the departure and is harder to predict in advance.

Does agentic AI need a human in the loop?

For anything carrying potential harm, yes. Consumer Duty obligations make human involvement necessary where vulnerability, complaints, or financial difficulty appear, regardless of how well the system performs. Most production deployments in finance run agents autonomously on routine volume and route defined categories to a person every time.

Ready to automate more?

Put your customer operations on auto-pilot

Ready to automate more?

Put your customer operations on auto-pilot

Ready to automate more?

Put your customer operations on auto-pilot