A customer reports that a product arrived damaged. Another says a component stopped working after a few months. A third wants to know whether a repair is covered by the warranty.
For a growing retailer these requests quickly become hard to follow. Photos arrive by email, order details are missing, colleagues ask for updates, and nobody is sure whether a case is waiting for the team or for the customer. The problem is rarely slow people. It is that the information needed to resolve a case is scattered across emails, marketplace messages and memories.
Vedron's service cases put each request on one record with a reference code, a status, an owner, the customer's photos and the whole conversation.
Why after-sales requests need their own process
A delivery question may only need a tracking link. A defect is different: it needs an assessment, often more evidence, a decision, and a record of what was agreed. Without a defined process the same problems keep returning:
- Missing information: the customer describes a fault but leaves out the order, the serial number or the purchase date.
- Repeated questions: colleagues ask for details the customer already sent.
- Unclear ownership: nobody knows who is handling the case.
- Scattered history: months later nobody can reconstruct what was reported and what was decided.
The fix is to make the case, not the individual message, the unit of work.
What a service case holds
Your team opens a case and records what is known. A case holds:
- The customer's name, email, phone and language.
- The order number, serial number and purchase date, as provided.
- The type: warranty, return, repair or general question.
- A subject and a description of what happened.
- Photos, videos and PDFs, kept privately with the case.
- The company it belongs to, the colleague it is assigned to, and internal notes.
Provided, not verified. The order number and serial number are stored as given. They are not checked automatically against your order records, so your team should confirm the purchase and the product during its review.
Let the customer add the details themselves
Instead of long email threads, the customer gets a private link to a page on vedron.io. There they describe the problem, add photos, a short video or a PDF (up to 25 MB each), and read your replies. No account and no login are needed, and the page speaks the language of the case: English, German, Polish, Spanish or Chinese.
- The link is personal and works for 30 days. Every email carries a new link.
- It opens only that one case. Your internal notes are never shown.
- The page is not indexed by search engines.
- A closed case does not accept new messages.
How a case starts. Today your team opens the case, or it is created from an email sent to your service mailbox when email intake is switched on. There is not yet a public claim form on your storefront.
A reference code for every case
Each case gets a code such as SC-1-00001. The number counts per company, so cases of different companies never share a number, and a customer can quote the code in any conversation.
The code is in the subject of every email we send. When email intake is on and the customer replies to that email from the address on the case, the reply joins the case automatically.
Statuses that show what happens next
A case moves through six statuses:
- Open: new, not yet looked at.
- In review: your team is assessing it.
- Awaiting customer: you asked for more information. This is set when you tick that option on a reply.
- Resolved: a solution was found.
- Rejected: the claim was declined.
- Closed: finished. The customer can no longer add messages.
When the customer answers a case that is awaiting them, it moves back to in review. A message on a resolved or rejected case reopens it. These movements tell the team at a glance what is waiting for us and what is waiting for the customer.
A practical workflow, from request to outcome
- Receive the request. Open a case, or let an incoming email create it. The customer gets a link to add details and photos.
- Assign it. Give the case to a colleague so there is one clear owner.
- Review the claim. Read the description and photos, and check the purchase and the product.
- Ask for what is missing. Reply with one specific request and tick the option that you need more information. The status becomes awaiting customer and the customer is emailed a link.
- Decide and record the outcome. Write the outcome in the case, set resolved or rejected, and tell the customer. The system records the process; it does not decide whether a claim must be accepted.
- Close it when nothing more can happen.
Give each case to the right person
Every case can be assigned to an employee. The list can be filtered by assigned to me, unassigned or a colleague, and it shows how many open cases are assigned to you or still unassigned. Only active staff who may work on service cases and who may access the case's company are offered, and moving a case to another company clears an assignment that no longer fits. Each assignment is noted in the conversation.
Keep customer communication in one place
When you reply, the customer receives a short email in their language that says we replied and gives a fresh link. The text of the reply stays on the page, so the conversation has one home. Good practice still applies:
- Acknowledge the problem clearly.
- Ask specific questions instead of vague ones.
- Explain what happens next.
- Do not promise an outcome before the facts are confirmed.
One record that stays useful
The conversation, your internal notes and the outcome stay together. Status changes, assignments and company moves leave a line in the thread, so a colleague who picks the case up later can see how it went. Files are private and open only to your team and to the customer of that case. This is a case record, not an analytics system: spotting recurring issues is still done by reviewing completed cases.
What a service-case system does, and what it does not
It gives you
- One record per request, with a reference code.
- Photos and messages from the customer on the case.
- Clear statuses and one owner.
- A private customer page and reply emails.
- A thread and audit lines for what changed.
Your team still has to
- Assess the merits of each claim.
- Verify the purchase and the product.
- Decide, and carry out any repair, replacement or refund.
- Make sure decisions follow your warranty terms and the law.
Email intake for a dedicated service mailbox
An administrator can switch on email intake for a mailbox that is only used for service. Each new email then opens a case with its text and photos, and the customer receives one link to add more. A reply that carries the case code and comes from the customer's address joins that case. Automated mail is skipped, mail from before the switch-on is ignored, and the mailbox is only read: nothing is marked as read, moved or deleted.
Where service cases stand today
- They are switched on per account. Ask your administrator if you do not see them in the menu.
- Staff need the service cases permission, and users limited to certain companies see only those companies' cases.
- Order and serial numbers are not verified automatically.
- Customers cannot yet start a case from your storefront themselves; your team opens it or an email creates it.
Frequently asked questions
Does a service case replace email?
Not entirely. The case is the record and the reference point. Customers are told by email when you reply and answer on the page, and with email intake on, replies sent to your service mailbox join the case too.
How does a customer start a case?
Your team opens the case, or it is created from an email sent to your service mailbox when email intake is switched on. The customer then gets a private link to add the details and photos. A public claim form on the storefront is not part of service cases yet.
Does the customer need an account?
No. The private link is the only thing needed. It works for 30 days, and every email carries a new one.
Can reference codes be separate for each company?
Yes. The number in a code such as SC-1-00001 counts per company, so cases of different companies never share one.
Does Vedron verify the order number and serial number?
No. They are stored as provided and are not checked automatically against your orders, so your team should confirm them during its review.
What happens when the team needs more information?
Tick the option that you need more information when you reply. The status becomes awaiting customer, the customer is emailed a link, and when they answer the case moves back to in review.
Can I assign a case to a colleague?
Yes. Every case can be assigned to an employee who may work on service cases and may access the case's company, and you can filter the list by assigned to me or unassigned.
Give every after-sales request a clearer path
Service cases are meant to move after-sales work from scattered messages to a consistent, documented process. If you want to try them, ask your Vedron administrator to switch them on for your account.
