Reporting a repair, not buying again: designing a service journey
Help customers identify an item, describe its symptoms and submit useful materials without asking them to diagnose the fault.
Article language: English

In this article
“Select the damaged component.” The customer looks at a wooden stand that will not hold its set angle. They know what is happening, but not whether the cause is a joint, a knob or a part with a name used only in the storeroom. The form asks them to diagnose the fault before it will accept the request. That is a rather bold way to organise a repair service.
In this hypothetical example, a manufacturer supports people using stands to display illustrations. The page should give the service team enough information to identify the individual item and understand the symptom. The customer provides what they know and can observe. A service specialist then decides what needs to be checked next.
The customer's product exists beyond the current catalogue
Getting help should not require buying again. A clear entry point on the product page and in support might say “Report a problem with a stand you own”. State which requests this channel accepts. A question about choosing a new size may lead to a different conversation from a report about an item that no longer holds its position.
The first field does not have to be an order number. The customer may have received the product from a company, bought it through a partner or lost an old message. If the number is needed later, explain its role and the available route for someone without it. A mandatory field filled with a made-up number gives the service team no better information than an explicit “I do not have an order number”.
Distinguish the model name, the individual item's number and the purchase number. In a catalogue these can mean three different things. Show an example of the appropriate marking in a photograph of your own product, with a caption explaining where to find it. The illustration should help locate the label, not suggest dismantling the product or doing something the manufacturer has not included in its instructions.
Apple describes several ways to find a Mac's model name and serial number, including a marking on the device and its packaging. It also notes a limitation: after a logic board replacement, the printed number may no longer be current. This is an example of identifying a particular product, not a ready-made set of rules for our stand.
Validation rules must reflect the actual markings. Apple explains, among other things, that its serial numbers use the digits 0 and 1 rather than the letters O and I, and that a scan of a box barcode may have an initial S. Those rules should not be copied into another manufacturer's form. They do show that an entered or scanned string needs to be checked against the appropriate format.
If the customer selects a model from a catalogue, show its name and a distinguishing feature before they continue. A similar-looking stand may have a different fitting. When the system does not recognise a number, do not silently replace it with the nearest result. Offer help identifying the item or accept a photograph of the marking if the service team actually works that way.
Imagine a label worn away over several years of use. The customer can point out the stand and attach a photograph, but cannot read the number even when enlarged. This route should lead to a different set of information, not another request for the same number at the end of the form. The summary might say “Model requires confirmation by the service team”. The team then receives an explicit unknown. If it cannot yet propose a next action without identification, it can respond about identifying the product instead of receiving a randomly selected model and an apparently complete record.
Remember older products. The current sales range does not describe everything customers still use. Linking a request to support for parts from an older series (in Polish) requires the company to have information about earlier markings. The website can honestly show a route to identification instead of removing the older product from the list and leaving the customer without an answer.
Ask about an event the customer can describe
For the stand, a useful question might be “What happens when you use it?” The answer “the arm drops when I let go” is an observation. “Damaged locking mechanism” is already an interpretation. A form should not force the second answer merely because an internal system assigns cases by component.
GOV.UK recommends a question protocol that records why each answer is needed and how it will be used. It also describes branching questions so people see those relevant to them. In our project, that means agreeing the fields with the people who actually receive the case before the screen is designed.
For each question, identify the service team's next decision. The model helps locate the right documentation. A symptom description helps prepare a conversation. A photograph of the label makes identification easier. If no one can say how they will use a field called “additional parameters”, remove it from the required set or name the specific information needed.
A well-chosen list of symptoms can make answering easier. It should also provide “Another problem” with a description and, where appropriate, “I cannot tell”. GOV.UK guidance on questions allows answers expressing uncertainty when they are valid for the case. Such an option does not remove the need for follow-up; it protects against a forced diagnosis that only appears precise.
In our example, a frequency question might distinguish “every time”, “sometimes” and “it happened once”. Do not add every possible answer just in case. If the service team asks about circumstances later for only one symptom, show that question after the relevant choice. An overly long list of similar faults demands knowledge the specialist was supposed to provide later.

When the symptom changes, remove from the current summary answers that belonged only to the previous branch. If the customer first chose a surface crack and then chose a falling arm, an answer about the crack's location should not appear as part of the current request. Keep a description written in the customer's own words for them to review again. Explain that the scope of questions has changed and show the new set before submission. Going back to an earlier screen then does not create a contradictory history the service team later has to clarify by phone.
Retain a free-text symptom description as the customer's own account. Do not turn “I think the part feels loose” into “looseness confirmed” in the summary. Automatic tidying can help, but should not raise the certainty of an observation. This also applies to using AI to handle requests and complaints (in Polish) if the company later adds such a tool to the process.
The symptom and the desired next step answer different questions. A customer may want to establish whether repair is possible, ask about a suitable part or receive an explanation. The form should convey that intention to the team. A button label alone should not decide the diagnosis or the terms on which the service will be performed.
Choose contact details according to the next real step. If the team replies by email, a phone number need not be mandatory just because there is room for it in the mock-up. If a conversation is needed, explain that beside the field and let the customer state contact conditions the team can actually accommodate. The product user is not always the purchaser. The form should distinguish details for the reply from details of an earlier order. Otherwise the message about the case may reach someone who knows the purchase but not the problem described.
Materials should help, not become an obstacle
A photograph of the whole product and a photograph of its marking serve different purposes. Rather than showing two empty frames, explain what the person receiving the request needs. If a photograph is optional, say what the service team can do without it. If a particular stage requires one, explain that condition at the relevant question, not only after someone tries to submit the form.
A clear approach to adding attachments and correcting individual files (in Polish) lets the description survive a photograph error. Customers should be able to tell whether a photograph has merely been selected or has reached the case. Removing an old image and adding a new one must not leave both in the summary as current materials.
Switching to a phone can be natural: the description is written at a computer, while the photograph is taken beside the product. If you support that route, design the handover between devices (in Polish). The person taking the photograph needs to recognise which request it will join. An open camera alone does not confirm that the earlier context has been retained.
Supporting materials should concern the correct model. Product instructions and first steps (in Polish) may explain the markings or show the intended way to use it. Do not make a customer go through the entire manual again just to open the form. If they report a symptom that appeared after several months, the contact route must remain visible.
A question about a replacement requires a separate compatibility check against the product already owned (in Polish). A similar photograph of a part does not confirm a fit. The form can collect the marking and the question, leaving confirmation to a person or system with the right data. Do not present receipt of the message as confirmation that the accessory is compatible.
At Aeneia Design, the starting point for such a journey is the service team's real questions and the available request workflow. A design can bring model identification, the description and materials into a clear route. Useful input from the company is one example of a properly received case and one needing more information, prepared without unnecessary customer data.
What has actually been received?
Before submission, show the selected product, symptom description and list of materials. Correcting one answer should preserve the others. If the customer changes the model, check which previous fields still make sense. Do not automatically carry answers about a different construction into the new request merely because both products are stands.
Once the request is accepted, provide a recognisable case reference and the confirmed next step.
If the connection breaks after submission, distinguish a missing confirmation from a rejected request. When the system can check the state of the earlier attempt, show that result before offering a retry. A customer should not receive two case numbers simply because the first response did not reach the browser. “We received your request” does not mean “the product has been accepted for repair”. If the service team will first review the materials and contact the customer, say exactly that. A response deadline should appear only if the company has actually set one for this route.
Additional information should belong to the existing case. When the team asks for a clearer photograph of the label, the customer should not have to fill out the form again and accidentally create a second request. In the message, show the case number and the missing information. Confirm receipt of the photograph while keeping the earlier description. When accepting the page, also walk through this short follow-up: an employee asks for one item, the customer sends it and the team finds it with the right case. That is a different outcome from a successful first submission alone.
A well-designed confirmation page after the form (in Polish) lets people return to the case. Also show whether the customer needs to send anything physically at this stage. Receiving a description must not look like an instruction to ship the product to a default company address. Such an instruction has to come from an agreed service process.
Acceptance can end with a simple task: a person who knows only the model and symptom submits a case without inventing a diagnosis. The team receives information that helps identify the item, sees what is missing and can state the next step. The form has done its job if the specialist does not have to start the conversation by asking which product the customer meant.








