Example sketch
Tracking complaints in manufacturing
“Complaints reach us by email, phone and word of mouth on the shop floor, and nobody can say which ones are still open or what caused them.”
This sketch is an example. We wrote the sentence; the concept was generated by an AI and edited by us; our renderer draws it.
ConceptCustomer service
Complaint File
Every complaint gets a file, an owner and a root cause.
How we understood your problem
A complaint today has no fixed home. It sits in inboxes, on notes and in people's heads. That leaves no answer to what is still open, let alone the more important question: which causes keep recurring. The customer notices in the waiting time.
Who it's for
- Sales supportLogs complaints and keeps the customer updated.
- Quality assuranceDetermines the cause, defines actions and closes the file.
- Production managementSees which causes are recurring and which batches are affected.
Interface
Data model
| Entity | Field | Type |
|---|---|---|
| Customer | company | Text |
| contact_person | Text | |
| Product | number | Text |
| name | Text | |
| Batch | number | Text |
| product | Reference | |
| produced_on | Date | |
| Complaint | customer | Reference |
| batch | Reference | |
| stage | Text | |
| received_on | Date | |
| photo | File | |
| Cause | name | Text |
| area | Text | |
| Action | complaint | Reference |
| text | Text | |
| effective | Yes/No | |
| cost | Amount |
| From | Cardinality | To | Relation |
|---|---|---|---|
| Customer | 1:n | Complaint | files |
| Product | 1:n | Batch | is produced as |
| Batch | 1:n | Complaint | is affected by |
| Cause | 1:n | Complaint | explains |
| Complaint | 1:n | Action | leads to |
Market value
What this problem would be worth on the market: how the product could be offered if it were sold. Not our price, and not an offer.
Flat monthly price per business
-
Files
89 €
per month · per business
- Most likely fit
Files + causes
149 €
per month · per business
Complaints affect the whole business. Per-user pricing would penalise simply reading along.
Roadmap
-
Stage 1
One place
Every complaint has a file with a stage and an owner.
-
Stage 2
Causes
Fixed cause catalogue, analysis by cause and batch.
-
Stage 3
Outward-facing
Interim update and closing report go from the file to the customer.
Core features
- Logged in a minuteCustomer, product, batch, photo. Nothing more is needed at intake.
- Stages, not status labelsIntake, review, action, closed: everyone sees where a file stands.
- Cause catalogueA short, fixed list of causes is what makes recurring patterns countable.
- Batch linkageShows other deliveries from the same batch before the next customer calls.
- Reply to the customerInterim update and closing report from the file, as PDF or email.
Deliberately left out
- No full 8D report: a cause and one action are enough for most cases.
- No credit notes: the decision is in the file; booking happens in the ERP system.
- No supplier complaints: different parties, a different process, later.
What the AI does
Reads incoming emails and suggests product, batch and a cause from the catalogue.
What the AI explicitly does not doThe AI never sets the cause or replies to a customer. Both stay with quality assurance.
Integrations
- ERP system (batches)
- Email inbox
- PDF export
Three questions we would ask you first
-
Can batches be traced through to delivery today, and in which system?
-
Who decides on replacement or credit, and must that approval be part of the flow?
-
How many complaints occur per month: closer to ten, or closer to a hundred?
A sketch, not an offer. Generated by an AI, rendered by us.