- Industry
- Procure AI
- Department
- Customer
- Team
- Customer Lifecycle
- Kind
- Investigator
- Approver
- Client Engagement Lead
- Code
- CUS-15
It groups feedback from client QBRs, surveys, tickets, requisitioner chats and supplier enablement calls into themes, such as approval chains too long, catalogue gaps, invoice match exceptions or onboarding friction for suppliers, and sizes each by volume, clients and fees affected. It explains the root cause behind the biggest themes and files them with their evidence in the product feedback tool, linked to existing roadmap items. **The problem it solves:** Why clients, requisitioners and suppliers are giving this feedback: the themes, how many and which clients raise them, since when, and what changed in the platform, workflows or service before.
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 QBR notes, survey responses, tickets, chats and supplier calls for the period, with each client's annual fees..
- 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 Client Engagement Lead 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 roadmap items. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The feedback taxonomy: service and platform areas (requisitioning, approvals, catalogues, sourcing events, contracts, supplier onboarding, invoicing and match, analytics), theme definitions, the voice-of-client report format and the known issues and roadmap items.
Reads from
the feedback repository: the QBR notes, survey responses, tickets, chats and supplier calls for the period, with each client's annual fees.
Acts in
the product feedback tool: it creates or updates one feedback item per theme with its evidence, linked to existing roadmap items.
Hands back
A ranked list of themes, each with theme, service_area, audience (client or supplier), items (a count), clients (a count), fees_affected (a number or null), sentiment (negative, mixed or positive), root_cause, cause_type (defect, missing_feature, workflow_design, service_process or documentation), quotes (a list) and linked_item (a roadmap or issue id, or null).
Asks a person when
A theme points to a security, data-protection, payment or compliance-control issue, or it would file a new product feedback item rather than link to an existing one.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Items needed for a theme | 5 | Smaller groups stay in other instead of making a theme. |
| Most themes reported | 8 | The report keeps the top themes up to this number. |
| Quotes kept per theme | 3 | Verbatim quotes kept per theme, with personal data and supplier prices removed. |
| Rank themes by client fees affected | On | When on, themes are ranked by the annual fees of the clients raising them, not only by count. |
| Keep supplier feedback in its own themes | On | When on, feedback from suppliers is themed apart from client feedback, since their needs differ. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Put each item in exactly one theme from the taxonomy; a theme needs at least 5 items, and at most 8 themes are reported.
- Rank themes by client fees affected when on is true, otherwise by count, and report both.
- When on is true, theme supplier feedback separately from client feedback.
- Count clients, not items: one client's repeated complaints are one client.
- For the top themes, name the likely root cause and whether it is a platform defect, a missing feature, a client workflow design, a service process gap or a documentation gap.
- Keep up to 3 quotes per theme, with names, emails, prices and supplier names removed.
- Link a theme to the existing roadmap item or known issue instead of filing a new one where one exists.
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.