A new kitchen is fitted, all good - except a scratch in the worktop, spotted at the handover. No drama, these things happen: replacement ordered from the manufacturer, it’ll be delivered, it’ll be swapped. The process is routine. And yet it becomes a nuisance, for one single reason: the customer doesn’t know what’s happening.
So they call. After four days the first time, “where’s it got to?”. The office checks the manufacturer portal, finds a delivery date, calls back. After a week another call, the same routine. By the third query the customer is irritated, even though nobody did anything wrong - the worktop is ordered, it comes when it comes. At the end there’s an annoyed customer and perhaps a mediocre review for a process that actually ran cleanly.
Why the uncertainty is the problem, not the defect
Complaints come with the territory, everyone in the trade knows that. A customer whose defect is fixed promptly and traceably is often happier afterwards than one who never had an issue - because they’ve experienced that someone cares. So the complaint isn’t the risk, it’s the chance for exactly that experience.
It’s squandered at a single point: the communication in between. Between “reported” and “swapped” there are often weeks in which nothing reaches the customer. Into that silence grows the suspicion that nobody’s bothering - even though everything’s running in the background. The customer calls not because something’s going wrong, but because they know nothing. And every one of those calls costs twice: office time on one side, a piece of trust on the other.
Photo: zacgudakov / Unsplash
Why the existing tools don’t fit
There are two obvious tools, and both are made for something else.
The kitchen-industry software - Carat, KPS and the like - is strong at planning, measuring and ordering. Complaint handling runs there, if at all, internally. A page the customer opens themselves to see progress isn’t part of it. Outward, toward the customer, there’s simply nothing.
The general ticket systems - Zendesk and relatives - are the other extreme. They’re built for IT and software support: priorities, internal responsibilities, handling times. A kitchen complaint doesn’t fit in there. It hangs on a manufacturer supply chain and a fitting date, not a support queue, and the customer wants no ticket number but understandable progress. A repurposed support tool feels as out of place here as it is.
Between them, exactly what matters is missing: a plain, customer-facing status tracking for a trade process stuck at the manufacturer.
What a status page on the parcel-tracking principle looks like
Everyone knows the model from online shopping: you order something and can see at any time via a link where the shipment is - ordered, packed, on its way, delivered. That exact principle transfers to the complaint.
For each case there’s a page, reachable via a personal link, with a few clear stages: reported, manufacturer informed, part ordered, delivery date set, fitting arranged, done. The office advances the stage with one click as soon as the manufacturer responds - and advancing it sends a short message to the customer automatically: “Your replacement part is ordered, expected delivery in three weeks.”
The effort is less than what it replaces. Instead of searching the portal and calling back at every query, the status is advanced once when something happens - and all the queries about it become moot, because the customer can look for themselves any time. What changes above all is perception: “they never get in touch” becomes “they’ve got this in hand”. The same process, the same wait, an entirely different feeling.
Photo: ka_idris / Unsplash
Where the limits are
Two things belong on the table. One is the honesty of the display. The point isn’t to gloss over delays but to make them traceable. An “expected delivery in three weeks” reassures more than any silence, but only as long as it’s true - a prettified status that then doesn’t hold does more damage than none. The page is only as good as the truth on it.
The other is access. A complaint case contains customer data, so the link belongs secured and not publicly findable, and only what’s necessary should be on it - the status, not half the customer file. Data minimalism is the right measure here too.
If every “where’s it got to?” call sounds familiar
What such a status page looks like depends on your process: which stages really reflect your complaint handling, how you communicate with the manufacturer, whether an automatic email is enough or a message makes sense too. It can’t be taken off the shelf, because your process and your manufacturer relationships are yours - but it’s no big system either, just a lean thing with exactly one purpose.
If you’d like to know how this could work for your studio: I’m Eric Menge of EMIT Solution, reachable at info@emit-solution.com and via emit-solution.com. I build tailored solutions like this myself - one person who understands the site and the technology behind it, rather than handing you a support tool built for IT tickets, not for the journey of a replacement part from the manufacturer into the kitchen.
FAQ
Isn't this overkill for a single complaint?+
For one, maybe; for the everyday, no. A kitchen studio rarely has just one open case - replacement parts, touch-ups, delayed appliances run in parallel, each with its own wait and its own customer asking. The status page pays off not because of the one case but because it catches the same recurring query across all cases - and because it's precisely the complaint that decides the recommendation.
Why isn't a normal ticket system enough?+
Ticket systems like Zendesk are built for IT and software support: internal handling, priorities, SLAs. A kitchen complaint looks different - it hangs on a manufacturer supply chain, on part orders and a fitting date, and the customer doesn't want a ticket number but understandable progress in plain language. A lean status tailored to exactly this process is closer to the need than a repurposed support tool.
What doesn't the kitchen-industry software do itself?+
Software like Carat or KPS is built for planning, measuring and ordering - that's its strength. Customer-facing status tracking that the end customer opens via a link isn't part of it. Complaint handling runs there internally, if at all; toward the customer there's nothing. That outward side is exactly what an own status page fills.
How much upkeep is it for the office?+
It has to be less work than the callback it replaces, or it doesn't pay off. So the status is deliberately simple: a few fixed stages the office advances with one click as soon as the manufacturer responds. Advancing it sends a short note to the customer automatically. On balance that's faster than the looking-up and calling-back that every query costs today.
And if it does take longer at the manufacturer?+
Then the page shows exactly that - honestly. The point isn't to hide delays but to make them understandable. A customer who sees 'part ordered with the manufacturer, expected delivery in three weeks' is calmer than one who hears nothing at all - even if the wait is the same. Transparency about a delay beats silence about a fast process.
Want to know more?
In a free intro call we discuss how you can use these topics for your company. Not a sales pitch, but an honest assessment.
Book a free intro call
