We built an internal tool from scratch where AI reads the thread, pulls order context from the database, and drafts a reply — so the team handles more tickets in less time. Stack: Next.js 16, MongoDB, Tailwind, Google Gemini.


The Harixx team was processing customer emails across multiple interfaces in parallel: inbox, marketplace consoles, order spreadsheets. Order context had to be looked up manually for every ticket — response time kept growing, SLA didn't.
Harixx came to us with a product brief: build a single tool where the support team handles customer correspondence from the first email to ticket close — without jumping between inbox, spreadsheet, and marketplace console.
The team was serving several businesses at once, each with its own ticket flow, reply templates, and SLA. Order metadata — ASIN, carrier, tracking number, delivery date — lived in different systems and had to be checked manually for every request.
The goal wasn't to build yet another ticketing system, but to ship a tool where AI takes the routine off the operator and leaves them in control of the final reply.
The starting requirements were concrete:
We worked as a product team with weekly releases. The focus: get to a working version for the support team fast, then iterate on real data instead of assumptions.
Phase 1 — Architecture and foundation. Set up a Next.js 16 App Router monorepo, picked MongoDB Atlas as the primary store for the document-oriented thread model, and built a multi-tenant data schema (Business → Inbox → Thread → Message) with access isolation between businesses.
Phase 2 — Inbox and statuses. Built a four-status workflow (New / In Progress / Escalated / Resolved), real-time UI updates when new messages arrive, search by order number, filters by business and manager, and a status audit log.
Phase 3 — The Gemini AI layer.Integrated Google Gemini for three scenarios: request-type classification, reply drafting grounded in the full thread history, and an “Auto-reply candidate” flag for tickets that can be closed with an automated reply after the operator confirms.
Phase 4 — Order context and SLA dashboard.Spun up an integration layer with marketplace APIs: order metadata (ASIN, carrier, tracking number, delivery by) is pulled in next to the conversation in real time. Built a dashboard with metrics — total threads, avg resolution time, avg first response time, escalated >3H, autoreplies, drafts, currently open.
The product went into production use by the Harixx team 3 months after kickoff — no release slippage.
Five tracks that together produced an internal product ready for daily use.
Next.js 16 App Router + MongoDB Atlas, server actions, a multi-tenant data model with access isolation, role-based authentication.
A custom component system on Tailwind CSS v4 in the Harixx cream/coral brand palette. Responsive UI tuned for working with lists of hundreds of threads at once.
Request-type classification, reply drafting grounded in the full thread context, an “Auto-reply candidate” flag for bulk processing of routine requests.
Marketplace API integration: ASIN, carrier, tracking number, and delivery date pulled in real time next to the conversation. Zero tab-switching.
Team metrics (volume, resolution time, first response time, escalated >3H, drafts, currently open), charts by date and business, automatic escalation past 3 hours.
The product has been in daily use by the Harixx support team since spring 2026.
Every reply used to start with hunting for context across three systems. Now AI prepares the draft and the order data is on the same screen. Time per ticket has dropped noticeably, and the team finally sees SLA in a single dashboard.
Send a request — we'll book a free 30-minute call, run an express audit, and show you what we can do with your product.
Takes a minute to fill out. Three fields and we're already thinking about your project.