Support email that turns itself into tickets

The problem

Customer support reached the company as email, across four separate team mailboxes. Whether an email became a tracked ticket depended on a person noticing it and re-entering it into the helpdesk. Issues slipped. Duplicates multiplied. And leadership had no single view of what was actually open.

The friction

Every support email was read and retyped by hand. The same issue raised in two mailboxes became two tickets, or none. Escalation language sat buried in long threads where nobody saw it in time. And there was no way to see which accounts were quietly accumulating unresolved problems.

The system

An automation that scans the four mailboxes on a fixed schedule, classifies each email — is this a support issue, and what kind — checks it against existing threads so the same problem does not become two tickets, and creates the ticket in the company's helpdesk.

What it deliberately does not do matters as much. Tenders, integration requests and manufacturing queries are left for people to handle. That is a policy decision taken with the support lead, not a gap in the software.

Creating tickets is only half the job; seeing the pattern across them is the other half. So alongside the automation sits a management dashboard with role-based views for the support lead, the IT head and the chief executive: blocker and bottleneck panels, ranking by risk to response commitments, detection of duplicated and over-merged tickets, clustering of related issues across tickets, a per-account health view, and a run log of every action the automation has taken.

The workflow

The automation runs on the company's own server, on a schedule, and logs every action it takes. A daily digest posts to the team's channel so the people doing the work can see what the system did overnight.

The rollout was deliberately graduated. A supervised period first, with a person reviewing the automation's decisions daily. Then unattended operation with weekly checks, then monthly. Deployment follows the company's own IT procedure — their repository, their review gates, their servers, their keys.

What we learned

Automation removes the re-entry, not the judgement. The categories that need a human still go to a human, and naming those categories up front was the part of the design the client cared about most.

A graduated rollout is worth the extra weeks. Nobody was asked to trust an automation with their inbox on day one; the system earned the move from supervised to unattended by being watched first.

The system has been running in production on the company's own infrastructure since August 2026.