Client support, online gaming

Staff stopped copying client emails into Jira

Every client request now goes to one desk with its full history, so staff answer clients instead of copying emails across.

Client
A multi-brand online gaming group
Built on
Jira, with AI sorting
Replaced
An old desk and a portal that needed developer accounts
Book a 30-minute call
0client emails staff copy into the tracker, down from every one
2,860past requests moved across with their history
99.5%of updates reached Jira within 5 minutes
6 weeksto replace the old desk and portal

What changed for the business

What it means for the group

  • The hours staff spent copying and searching now go on answering clients.
  • Anyone in client services can pick up a request and see everything that client has asked before.
  • No request depends on someone remembering to copy it into the tracker.
MeasureBeforeAfter
Client emails staff copy into the trackerEvery oneNone
Where a request can sitEmail or the old portalOne desk
A client's full historySpread across 2 systemsIn one place
Desks and portals to run21

We measured these during rollout and the 7-day test.

What the group needed

Clients raise requests for the group's developers every day. Client services had to answer each one quickly, with the client's full history to hand. And the developers had to stay in Jira.

How it worked before

  • The old portal only worked for people with developer accounts, so most clients emailed instead. Then staff copied every email into the tracker.
  • Requests sat in 2 places. Seeing one client's full history meant searching both.

What we built

  1. 01

    One desk for staff and clients

    Each client account belongs to one person, and every request keeps its full conversation history.

  2. 02

    Developers stay in Jira

    Status changes, comments and replies move between the desk and Jira within 5 minutes, so nobody copies them across.

  3. 03

    AI sorting

    AI suggests a category for each request and finds similar past ones, so staff start from what worked before.

  4. 04

    The history moved across

    Every past request from 74 client accounts, moved and checked against the old systems.

How it went live

  1. Week 2

    Staff working in the new desk on the company network.

  2. Week 5

    Clients raising and following requests in their own accounts.

  3. Week 6

    The desk moved to its own address. Updates passed a 7-day test between the desk and Jira, the old desk was switched off and its old addresses now redirect.

Client requests used to arrive by email and through a portal only our developers could use, and we copied them into the tracker ourselves. Now every request has one place and one history, and our developers still work in the tool they know.

Head of Client ServicesOnline gaming group

Questions about this project

Did the developers have to change tools?

No. Requests, replies and status changes reach Jira on their own, so developers work where they always have.

What does the AI decide?

Nothing on its own. It suggests a category and finds similar past requests, and staff decide and reply.

How was the old data checked?

Every past request was moved with its history and checked against the source before the old desk was switched off.

Get one desk for requests spread across inboxes and tools

Bring the inboxes and portals your requests arrive through to a 30-minute call. We'll map the one desk that replaces them and the hours it would save.

Ask your AI assistant about us

Open our summary in the assistant you use, or copy the prompt.

Read the prompt