Skip to content

Use cases · 05 Checking complaints

One colleague knows how to check complaints. Now the whole team knows.

Which documents she pulls, which questions she asks, how she spots a pattern: together with her, we write this approach down as instructions for the AI. Whoever handles a complaint then gets the check prepared, with evidence, open points and a reasoned proposal. Your team still makes the decision.

Example with fictitious data

Today

Complaints end up with the one colleague who knows where to look. If she is away, they wait.

Afterwards

Her approach is stored as instructions. Everyone in the team gets the check prepared with evidence. A person still has to decide.

Where the instructions come from. From the colleague everyone has been asking.

We sit down with the person who checks complaints most reliably and go through closed complaints with them. Which documents they pull, which questions they ask and how they spot a pattern, we write down as instructions for the AI, known in the trade as a skill.

An employee shows Luis and Julius how she works at her desk
  1. Listening.

    Using closed complaints: what do you look up first? How can you tell it is not down to the installation? Quality assurance: “If the same batch has caused problems elsewhere, it is rarely the installation.”

  2. Writing it down.

    Every document she pulls becomes a checkpoint. Every rule of thumb is noted alongside. Whatever she would never decide alone becomes a limit.

  3. Testing and approving.

    We measure on closed complaints whether the AI, following the instructions, finds the same documents and reaches the same finding. The instructions only become valid once the head of quality agrees.

Gathered by the instructions. One complaint, checkpoint by checkpoint.

A complaint from Lindtaler arrives at the sales office. The AI checks it following quality assurance’s instructions: it looks for what the colleague would have looked for and submits the check. The head of quality has to decide.

Review fileLindtaler complaintDS-12Batch 26-0412submitted to: head of quality

Complaint · 08:15From: Lindtaler Anlagenbau, Quality assurance

Seal kits DS-12, delivery of 14 October. On 6 of the 40 seal kits delivered, oil leaks after installation. We request replacements and a statement.

Check of the complaint

Evidence 1: Delivery note

LS 58213, 14 October

40 seal kits DS-12, batch 26-0412

Evidence 2: Inspection report

Batch 26-0412

Sample: pressure test passed

Evidence 3: History

Same customer, June: cause was installation

Pattern: Same batch 26-0412 at two other customers

Evidence 4: Warranty

Framework agreement, § 8

The delivery is covered by the warranty.

Finding

The leak affects a batch that has already caused problems at two other customers. That points to material or production rather than installation at Lindtaler, even though the sample in goods outward was fine.23

Open

  • Photos or returned parts are missing.
  • How Lindtaler installed the parts is open. In June, the cause lay there.

Proposal

Accept and supply replacements as soon as the parts are back.14 Clarify batch 26-0412 with production.3

The same check, even when the colleague is away.

The instructions apply to everyone who handles complaints: in the sales office, in service, for new starters. The colleague from quality assurance approves them and takes on what is genuinely difficult.

Sales officeComplaint from Lindtaler Anlagenbau

  1. Delivery
  2. Inspection
  3. HistoryPattern
  4. Warranty
  5. Check

ServiceComplaint from Lindtaler Anlagenbau

  1. Delivery
  2. Inspection
  3. HistoryPattern
  4. Warranty
  5. Check

New startersComplaint from Lindtaler Anlagenbau

  1. Delivery
  2. Inspection
  3. HistoryPattern
  4. Warranty
  5. Check

If someone spots a new pattern, it goes into the instructions. A change only takes effect once it performs better on a fixed test set and the head of quality agrees.

What is stored is what was corrected, not who corrected it.

What changes and what it takes.

  • For your teamThe knowledge of experienced colleagues becomes available to everyone, including new ones. The experienced colleague is interrupted less often and keeps the difficult cases.
  • PrerequisitesAn experienced person who takes the time to explain their approach using real complaints. Delivery notes, inspection reports and earlier complaints, easy to find and approved for this purpose.
  • Measuring successHow often the proposal holds without rework, how often documents have to be requested, how long complaints stay open. Measured by the instructions, not by people.
Area
Assistance for staff
Capabilities
  • Searching
  • Generating
Approval mode
  • AI researches and prepares

Which task takes up most of your team’s time?

Bring a specific task or an initial idea. You do not need a finished project brief.

Your first conversation is directly with one of the founders: Julius, Luis, Max or Quentin.

Prefer to write directly? kontakt@omnerio.com Two or three sentences about your task are enough.