Skip to main content


The Repairs task is a vital part of *Case management*, allowing you to select a case and initiate and manage a corresponding repair from A to Z.

Repairs can be created in Admin Suite - as described on this page - or via the Tasks App.

The Repairs overview is divided into three tabs; tabs containing an active task will display a red dot next to the tab name.

  • Receive: if the defective product tied to the case is shipped by a customer, you can mark the item as received here.
  • Execute: this is your main page for tracking and accessing current repairs.
  • Ship: use this overview for any items needing to be shipped back to the customer.

Both cases and repairs are created for a single product and every repair must be tied to a Case. Either the case itself will lead to the creation of a repair task, in which case you can skip straight to Managing a repair, or you will have to create the repair yourself.

When creating a repair manually via Suite, make sure that the the corresponding case has already been created in the Case management chapter in Suite so you can select it in the repair.


Working with the Repairs chapter requires your role to have the Repairs permission. Permissions are managed from the Roles and rights chapter namely, from the functionalities card of a users role.

Creating a repair

Creating the actual repair task is very intuitive, simply select the OU where the product will be repaired and attach its case. Indicate whether the item in question is already present or needs to be shipped still. In case of the latter, a new label Expected date will be shown.

By creating a repair task, its Status will automatically be set to In Progress.

Managing a repair

Now you can start adding details to your repairs task. These include the:

  • Products to use in the repair (up to 10 in Select products for repair)
  • Assignee;
  • Relevant images and documents.

The Case card shows you the details of the case, including the order at heart of the repair. The product from that order will be displayed at the bottom of the card, including its warranty state.

The Repair order card in the bottom-right of the overview shows you the Order ID of the order that has been created for this repair specifically. Any items you select for use during the repair will be stored on the order.

Additionally the item to be repaired is shown in this card. The item's Warranty state is for information purposes only and cannot be changed.

The interaction log

There are a few types of interaction logs that could be displayed under the Interaction logs card, and things could get quite messy especially if it's a complicated case or repair.

By clicking the Settings icon, you can filter the logs and either show all, or just show private, public, system, or repair related interaction logs.

You can create messages for either internal use or to be public, i.e. sharing them with a customer. If you want a message to be shared with the customer, you'll have to do so specifically by means of the action button. The message then gets sent to the customer by email.

Completing a repair

Completing a repair gives you a full overview of the repair and comes with a range of (required and optional) choices.

After completion of the repair task, you'll be automatically forwarded to the corresponding order (which was attached and visible in the overview as well) allowing you to request payment for any open amounts.

Getting the product to the customer

Depending on what you selected during the execution of the repair in the Tasks App, the product is either shipped back to the customer, or the customer is expected to pick it up.

Whichever you picked, after completion of the repair, its task will be displayed in the corresponding tab in the main overview in Admin Suite. You can then indicate whether it's completed easily by means of giving it a checkmark.

Pickup task configuration and templates

Currently only the Tasks App supports the selection for shipping/pickup of the repair.

Configuration of the pickup task and the corresponding message templates are described in the Tasks App section.