UAE · ENBook a demo
IT CompanyManagementInvestigator

Vendor Coordination Agent

Manages vendor requests and service levels.

Vendor Coordination AgentOperations Coordination
Industry
IT Company
Department
Management
Team
Operations Coordination
Kind
Investigator
Approver
Head of Service Delivery
Code
MGT-10

It manages requests and service levels with the company's own suppliers (cloud providers, subcontracted development shops, data-centre and support partners) and explains why a supplier missed its service level and what that means for the company's SLAs to clients. It logs the breach with the supplier, drafts the service-credit claim and asks first before a claim or escalation goes out. **The problem it solves:** Why the supplier missed its service level: which metric, by how much and when, whether the cause was the supplier, its dependency, our change or measurement, and which client services felt it.

How it works

6 steps, and a person signs off before step 6.

  1. 01Looks it up

    Finds the record the request is about in the ticketing and service management system: the supplier's tickets, service-level measurements, outage records and the client incidents linked to them..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Works it through

    Weighs competing explanations against the evidence and shows which one holds up.

  5. 05Asks a person

    Hands the work to Head of Service Delivery with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the ticketing and service management system: it logs the breach against the supplier and opens the credit-claim or escalation task. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The supplier management handbook: each critical supplier's service levels and credit terms, contacts and escalation path, and which client services depend on which supplier.

Reads from

the ticketing and service management system: the supplier's tickets, service-level measurements, outage records and the client incidents linked to them.

Acts in

the ticketing and service management system: it logs the breach against the supplier and opens the credit-claim or escalation task.

Hands back

An object with supplier, breaches (a list, each with service, metric, target, actual, cause, evidence and confidence), client_sla_impact (a list with client, service and breached true or false), credit_claim (an object with amount_usd, deadline and draft_text, or null), escalate (true or false) and next_steps (a list).

Asks a person when

A credit claim or supplier escalation would be sent, or a supplier breach caused a breach of a client SLA.

ApproverHead of Service Delivery

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Claim service credits within (days)30Credits must be claimed within this many days of the breach under most supplier contracts.
Breaches in a quarter before escalation3A supplier at or above this many breaches in a quarter is escalated to its executive contact.
Smallest credit worth claiming (USD)500Credits below this are logged but not claimed.
Critical suppliersprimary cloud provider, managed network provider, offshore QA partnerComma-separated. A breach by one of these is reviewed against client SLAs straight away.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Explain each breach from the evidence: the supplier's own fault, a dependency of theirs, a change on our side, or a measurement gap; weigh them and say what would confirm each.
  • Map each breach to the client services that depend on it and state whether any client SLA was breached as a result.
  • Claim credits of 500 USD or more within 30 days of the breach; never let a claim window lapse unflagged.
  • A supplier with 3 or more breaches in a quarter is escalated, with the Head of Service Delivery's agreement.
  • A breach by one of primary cloud provider, managed network provider, offshore QA partner that touched a client SLA is reported to the account managers of the clients affected.
  • Never accept a supplier's root cause without its evidence.

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.

Vendor Coordination Agent · IT Company | Basinwright Industries