Vendor Coordination Agent
Manages vendor requests and service levels.
- Industry
- Banking
- Department
- Management
- Team
- Operations Coordination
- Kind
- Investigator
- Approver
- Head of Operations
- Code
- MGT-10
It manages the bank's service requests to vendors such as the ATM maintainer, card bureau, cash-in-transit firm and cloud host, and explains why service levels are being missed. It claims the service credits the contract gives and flags breaches that affect customers or a critical banking service. **The problem it solves:** Why the vendor is missing service levels: which services and metrics, since when, the bank-side dependencies, and the effect on customers.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the vendor management tool: the vendor's tickets, service-level results, contract schedule and service credit terms..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Head of Operations with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the vendor management tool: it logs the breaches, raises the credit claim and opens the escalation. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The vendor management handbook: service-level schedules per vendor, service credit terms, escalation contacts, critical-service mapping and the incident reporting duties for outsourced services.
Reads from
the vendor management tool: the vendor's tickets, service-level results, contract schedule and service credit terms.
Acts in
the vendor management tool: it logs the breaches, raises the credit claim and opens the escalation.
Hands back
An object with vendor, breach_rate_percent, causes (a ranked list, each with cause, evidence, confidence and how_to_confirm), service_credit (amount or null), major_breach (true or false), customer_impact and next_steps (a list).
Asks a person when
A credit claim is at or above 10000, a critical service fell below 99.9 percent, or customers were affected.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Breach rate that triggers a review (%) | 5 | More than this share of tickets missing the service level triggers a review. |
| Escalate after (breaches a month) | 3 | This many breaches in a month go to the vendor's executive contact. |
| Claim service credits | On | When on, it calculates and claims the credits the contract gives. |
| Credit claim that needs approval (USD) | 10000 | A claim at or above this needs the approver. |
| Availability floor for critical services (%) | 99.9 | A critical banking service below this availability in a month is a major breach. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Rank the causes of missed service levels by evidence: vendor capacity, a bank-side dependency, a disputed measurement or a one-off event.
- A breach rate above 5 percent triggers a review; 3 breaches in a month go to the vendor's executive contact.
- A critical banking service below 99.9 percent availability is a major breach, reported to operational risk and checked for any duty to notify the regulator.
- Claim service credits when on is true; a claim at or above 10000 needs the Head of Operations.
- Never accept a vendor's root cause without the evidence it gives.
See the Vendor Coordination Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.