- Industry
- Oil & Gas
- Department
- Customer
- Team
- Customer Lifecycle
- Kind
- Investigator
- Approver
- Commercial Manager
- Code
- CUS-13
It scores each fuel account's health from liftings against contract, payment behaviour, quality and delivery complaints and survey sentiment using the weighted model, and explains which signals moved the score and the likeliest cause. It writes the score, band and drivers to the CRM and gives the account owner a task when an account turns red. **The problem it solves:** Why each account's health changed: liftings against contract, payments, complaints and sentiment over the period, and the supply, price or customer events that explain the change.
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 analytics warehouse: liftings, receivables, complaints and survey results by account for the period and the one before..
- 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 Commercial Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the CRM: it updates each account's health score, band and drivers, and creates a task for the account owner when it turns red. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The health model: weights, bands, signal definitions, and known events such as refinery turnarounds, supply outages and price moves that shift liftings.
Reads from
the analytics warehouse: liftings, receivables, complaints and survey results by account for the period and the one before.
Acts in
the CRM: it updates each account's health score, band and drivers, and creates a task for the account owner when it turns red.
Hands back
A list of accounts, each with account_id, score, band, change, drivers (ranked, each with signal, effect and evidence) and likely_cause.
Asks a person when
An account turns red, or the cause is a supply failure or quality problem on our side.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Liftings weight (%) | 40 | Liftings against contracted volume. |
| Payment weight (%) | 25 | Days overdue and credit holds. |
| Complaints weight (%) | 20 | Quality and delivery complaints. |
| Sentiment weight (%) | 15 | Survey scores. |
| Red below | 50 | Score out of 100. |
| Amber below | 75 | Score out of 100. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Weight liftings 40, payment 25, complaints 20 and sentiment 15 percent.
- Band red below 50 and amber below 75.
- Check whether a known supply event (our turnaround, a terminal outage) explains a lifting drop before blaming the customer.
- Name the signals that moved the score and their evidence.
See the Account Health Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.