02 · E-Commerce · Tyre Trade · Goodwheel GmbH

Helpdesk Scaling with AI Pre-Qualification at Reifen24.

From an overloaded shared inbox during spring and autumn peaks to Zoho Desk and Zoho CRM with GDPR-compliant EU AI classification. Standard requests receive draft replies while the team reviews and sends.

Architecture · EU AI → Zoho Desk + CRM
01 · TICKET INTAKE Peak intake (5–10×) B2C & B2B requests · Spring & autumn 02 · GDPR LAYER EU AI Pseudonymization 4 categories · >90% · EU residency 03 · HELPDESK CORE Zoho Desk + CRM Routing · SLAs · Reply draft 04 · HUMAN-IN-THE-LOOP Human reviews & sends No blind send · full liability
Peak response time −60% Achieved in the very first seasonal peak after go-live at comparable volume.
AI classification >90% Accuracy across four main categories following two weeks of tuning.
Team size unchanged More capacity for complex tyre advice and claims with no seasonal hiring.
01 · Starting Point & Bottleneck

Five- to ten-fold ticket spikes inside a shared inbox.

Reifen24 is a brand of Goodwheel GmbH in online tyre retail serving B2C and B2B customers. Each spring and autumn, inquiry volume jumps five- to ten-fold within days as the entire market switches to summer or winter tyres at once.

Previously, all customer inquiries arrived in one shared inbox with no fixed categorization, prioritization, or SLA tracking. Hiring temporary staff solely for two seasonal peaks per year was not economically viable. The goal was to relieve the existing support team so it handles peak volume calmly and reliably.

02 · Before → Today

From a shared inbox to pre-qualified peak-season support.

Before

Double-digit hourly waits during seasonal peaks

  • Every spring and autumn, tyre-retail ticket volume surges by a factor of 5 to 10.
  • All inquiries landed unsorted in one shared inbox handled on a “whoever sees it first” basis.
  • Response times stretched into double-digit hours; escalations ran verbally with no metrics.
  • Adding temporary headcount for a few weeks each year was not commercially viable.
Today

Pre-classified tickets, vetted drafts, and clear SLAs

  • After pseudonymization, an EU AI model assigns incoming tickets across four categories at over 90% accuracy.
  • Zoho Desk routes automatically to the right role and populates standard templates with order data.
  • The support team reviews and sends; peak-season response times dropped by roughly 60%.
  • Monthly SLA and category reports show management clearly where volume or training needs grow.
03 · Architectural Decisions

Automate the prep work, keep accountability with the team.

Reviewing historical inquiries revealed four clear categories: delivery status, claims, product advice, and invoicing or payment questions. Across the first three categories, more than 70 percent were recurring standard requests.

  1. 01

    Zoho Desk and Zoho CRM as structured helpdesk

    Clear ticket categories, role-based routing, per-category SLAs, escalation rules, and automated monthly statistics replace the shared inbox directly alongside customer context.

  2. 02

    GDPR-compliant EU AI with upfront pseudonymization

    Personal data is pseudonymized prior to every AI call. Classification runs exclusively on a model with EU data residency and a documented DPA, audited and signed off by Reifen24’s Data Protection Officer.

  3. 03

    Human-in-the-Loop instead of blind auto-sending

    In the tyre trade, the retailer carries liability for incorrect product advice. AI therefore produces only the classification and pre-filled draft; a specialist verifies variables such as order number, delivery date, and tyre model before sending.

04 · Rollout & Daily Operations

Live production in three phases within 6 to 8 weeks.

Phase 1 · Zoho foundation
Configuration of Zoho Desk and Zoho CRM with categories, routing rules, SLAs, escalation logic, and automated metrics, paired with two weeks of team training.
Phase 2 · EU AI tuning
Training and fine-tuning the EU model on the first few hundred real tickets over two weeks until classification accuracy stabilized just above 90 percent.
Phase 3 · Templates & DPO
Joint creation of reply templates with placeholders for order number, delivery date, and tyre model, plus formal sign-off on pseudonymization, EU residency, and DPA by the Data Protection Officer.

In the first seasonal peak after go-live, response times ran roughly 60 percent below the prior year at comparable inquiry volume and unchanged team size. Specialists now focus on complex product advice and claims while management receives precise monthly SLA data.

“Mate iT took our helpdesk to a whole new level — with practical AI features that pre-qualify tickets and propose replies. Our support now scales without us having to expand the team. Exactly the kind of solution a mid-market company looks for.”

Hendrik Salewski · Managing Director, Goodwheel GmbH (Reifen24)

Frequently asked questions about the Reifen24 case.

How Human-in-the-Loop, GDPR, EU data residency, and rollout timelines were implemented in practice.

Does the AI make autonomous decisions or only draft suggestions?

Suggestions only. The AI classifies incoming tickets by category (such as delivery status, claims, or product advice) and drafts a reply for standard questions. A human reviews it, adjusts if needed, and only then sends it. We deliberately avoid fully autonomous replies: accountability stays with the team while speed comes from the preparation work.

How was the solution implemented in compliance with GDPR?

Classification runs on an AI model with EU data residency, so tickets never leave the GDPR zone. Personal data inside tickets is pseudonymized before classification. The data processing agreement (DPA) with the AI provider is part of the setup, cleanly documented and signed off by Reifen24.

How long does it take to roll out a comparable setup?

Core helpdesk configuration with ticket routing and escalation rules typically takes two to four weeks. AI pre-qualification follows on top and is tuned on the first few hundred real tickets, adding another two to three weeks. In total, we plan for six to eight weeks from kickoff to live operations.

Which ticket categories are pre-qualified at Reifen24?

The AI assigns incoming inquiries to four main categories: delivery status, claims, product advice, and invoicing or payment questions. In the first three categories, over 70 percent are recurring standard requests populated into prepared templates with order number, delivery date, and tyre model.

Why were Zoho Desk and Zoho CRM chosen as the helpdesk foundation?

Zoho Desk and Zoho CRM combine customer context, clear ticket categories, routing rules, per-category SLAs, escalation logic, and automated monthly analytics in one platform that integrates cleanly with GDPR-compliant AI pre-qualification.

Assess helpdesk & GDPR AI realistically.

Seasonal peaks or repetitive customer inquiries tying up your support team? Walking through ten real sample tickets, we assess how Zoho Desk and EU AI can help in full GDPR compliance.

Matthias GrdanManaging Director · AI & Service Architecture
Zoho & AI TeamHelpdesk, EU AI & GDPR · Villingen-Schwenningen

The introductory call is free and without obligation. Your request is delivered directly via our Google Workspace mail service — or prepared locally as an email draft.

Delivered via our Google Workspace mail service or prepared locally as an email preview without third-party trackers. Privacy Policy

Book a call