- Industry
- Oil & Gas
- Department
- Customer
- Team
- Customer Lifecycle
- Kind
- Investigator
- Approver
- Commercial Manager
- Code
- CUS-15
It groups feedback from fuel customers, from surveys, tickets, driver reviews of stations, account reviews and the dealer community, into themes such as delivery windows, fuel quality, card acceptance and invoice errors. It sizes each by volume, accounts and annual volume affected, explains the root cause of the biggest and files them in the product feedback tool. **The problem it solves:** Why fuel customers are giving the feedback they are: the biggest themes, how many accounts and how much volume they affect, and the operational cause behind each.
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 feedback repository: the feedback items for the period..
- 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 product feedback tool: it creates or updates one feedback item per theme with its evidence, linked to existing improvement items. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The feedback taxonomy: themes for supply, quality, retail, cards and billing; the operational causes behind each; and existing improvement items.
Reads from
the feedback repository: the feedback items for the period.
Acts in
the product feedback tool: it creates or updates one feedback item per theme with its evidence, linked to existing improvement items.
Hands back
A list of themes, each with theme, items, accounts, volume_affected_m3, root_cause, evidence and quotes.
Asks a person when
A theme points to a safety or quality problem, or names a terminal, contractor or carrier as the cause.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Smallest theme | 5 | Fewer items do not make a theme. |
| Most themes | 8 | The report shows at most this many. |
| Quotes per theme | 3 | Anonymised. |
| Weight by customer volume | On | Themes are ranked by volume affected, not only count. |
| Always show safety themes | On | Any safety or quality theme is reported whatever its size. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Make a theme only from 5 or more items, except safety and quality themes when on is on.
- Rank themes by volume affected when on is on, and show at most 8.
- Trace each big theme to an operational cause (terminal, logistics, station network, billing) with evidence.
- Quote at most 3 items per theme, anonymised.
See the Feedback Analysis Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.