MESKRU is an official Atlassian Training Partner!

November 02, 2026

Sorting customer requests in retail: one front door, AI behind it

By Alexander Kruse, CEO

Your customers write about everything: late parcels, damaged goods, returns, sizing questions, ideas for the range. And it all lands at one address.

So why does a person still sort every single one? We show where the time goes, who pays for it, and how Customer Service Management on Jira Service Management uses Rovo AI to read the request, enrich it with order data and pass it to the right process.

InsightsCurrent topics
Cover of the MESKRU whitepaper: Customer Service Management for Retail

Where the time goes

Without AI and without automation, every step is done by hand:

  1. Read and classify. Someone reads the request and decides what it is about. Minutes.

  2. Look up the order. In the shop system, the ERP, at the carrier. Minutes.

  3. Forward by email. To the team that might be responsible. Hours.

  4. Wait for the other team. Days.

  5. The customer asks again. One request becomes another ticket, and everything starts over.

That is how one request quickly turns into three days. It could be sorted in seconds.

When every request is just a ticket, the whole shop pays

The cost doesn't only show up in support. How many teams touch a single customer request today?

  • Support reads and sorts every request by hand instead of helping customers.

  • Shoppers wait while tickets bounce between teams.

  • Margin: claims repeat because the causes stay unfixed.

  • Product misses what shoppers keep asking for.

One front door for every channel

Customer Service Management (CSM) is Atlassian's solution for external customer service and is built on Jira Service Management. It gives every channel the same front door. According to Atlassian, that includes email, a support website, an AI-powered chat widget for your website, phone and messaging apps such as WhatsApp.

Wherever the customer writes or calls from, the request arrives in the same place and runs through the same logic. Which channels and AI features are available in your Atlassian plan is changing fast. We check that case by case.

What the AI does between customer and process

Between the customer and your processes, CSM works with Rovo AI in four steps:

  1. Answers instantly. The customer doesn't wait for the next free agent to learn that the request has arrived and what happens next.

  2. Reads the intent. Claim, delivery problem, question or idea: the AI understands what it is about.

  3. Adds order data. Order, item and shipment status come in from your systems, so nobody has to look them up.

  4. Routes the case. To the process and the team responsible for it.

One front door, unlimited processes

Behind the front door there isn't one big pile but a separate process for each kind of request. In retail these are typically:

  • Support: the AI drafts the answer, the agent sends it. Atlassian's Support Companion creates drafts for review and never posts on the agent's behalf.

  • Claims: refund or replace, with the supplier task in Jira so the cause doesn't get left behind.

  • Delivery: late, damaged or lost: a case with the carrier and a tracking update for the customer.

  • Ideas: Rovo clusters what shoppers keep asking for, and Jira Product Discovery prioritizes it.

Every request lands where it makes a difference, and recurring claims and wishes turn into tasks for the teams that can fix the cause.

No data, no sorting

AI sorts only as well as the data it sees. Only with the order, customer history and shipment status does "Where is my parcel?" become a case the right team can work on straight away.

That's why we connect Jira Service Management to the systems your shop already uses, from Shopify, Shopware and Salesforce to HubSpot, SAP and Microsoft Dynamics 365, all the way to DHL and DPD. Then the AI works with real order data instead of guesses.

Three questions to start with

  1. Which requests could AI sort today?

  2. Which teams should own them?

  3. What could a first Rovo agent do in your shop?

We answer these three questions in a short remote call and sketch your front door from there. Before MESKRU, our founders Manuel Mesmer and Alexander Kruse were the internal Atlassian team responsible at a large European group. Today MESKRU is an Atlassian Gold Solution Partner and Service Management Specialized Partner in EMEA.

The whitepaper

Problem, cost and solution on five pages: the whitepaper Customer Service Management for Retail is free. For how to make the SLAs behind it reliable, read SLAs in Jira Service Management that your team actually meets .

For everything else we do for retailers, from store IT support to peak season planning, see Jira Service Management for retail .