Agentic AI Patterns

Course Content

Agentic AI Patterns

9 sections · 50 lessons

Can Agentic AI improve operational flexibility? Explain how.


What you need to know

Where the flexibility comes from

  • Exception handling. Scripted automation fails on the unexpected: a new invoice layout, an off-script customer question. An agent reasons through it with the same tools.
  • Recomposition. Adding "also check the vendor's GST registration" can be a new tool and a prompt line, not a release of new branching code.
  • Elastic capacity. A surge is a scaling problem (more compute) instead of a hiring problem.
  • Long-tail coverage. Workflows too rare to justify custom automation become worth doing.

The trade-off

What flexibility gives

  • Handles cases nobody coded for
  • Changes ship as config and prompts
  • Scales with compute during surges
  • Covers rare, low-volume workflows

What it costs

  • Paths you did not test can happen
  • Behaviour can change with a model update
  • Cost per case varies more
  • Harder to explain to auditors

The design that gets both

A workflow engine owns sequencing, retries, state and audit. The agent works inside bounded steps with narrow tools, step budgets and permission tiers. Every new path you enable gets golden-set cases before it goes live.

A real-life example

A travel-booking agent at a corporate travel company during a monsoon day in Mumbai: 60 flights are cancelled, and 900 travellers need rebooking in a few hours.

  • Old system: scripted rebooking worked only when the same airline had a seat on a later flight the same day. About 40% of travellers fit that. The rest went to a queue of 12 agents, with waits of over 3 hours.
  • With the agent: for each traveller, it checks other airlines, nearby airports (Pune with a cab), next-morning flights plus a hotel, and trains, all within the company's travel policy. It holds options (reversible) and sends the traveller two choices. Confirming a booking above the policy cap needs the travel manager's approval.
  • Bounds: 15 steps and Rs 25 of model spend per traveller; only hold_* tools are autonomous.

82% of travellers were rebooked without a human, median time 11 minutes. The flexibility came from the agent; the safety came from the tiers and budgets.

Follow-up questions to expect

  • "How do you add a new path safely?" — Add golden-set cases for it, run CI, release it behind a flag to a small share of traffic, and watch its metrics.
  • "Isn't a rules engine more predictable?" — Yes, for known cases. Keep rules for the common path and use the agent for exceptions.
  • "How do you explain agent decisions to auditors?" — Traces with the evidence and tool results used, and structured decision records, not the model's free-text reasoning.