Desk
Support ticket workspace
2026 — present
MENA
React • TypeScript • Tailwind CSS
Case StudyA customer-support platform that brings tickets, conversations and service workflows together so teams can own a request from intake to resolution.
Ressan's role
Full-stack product engineering
Capabilities
Industry
SaaS & StartupsSystem state
In production · running now
What was built
- Ticket workspaces with replies, internal notes, attachments and activity history
- Agent and team queues with ownership assignment and availability tracking
- SLA policies, escalation rules and business-hour configuration
- Support mailboxes, reply templates, macros and scheduled responses
- Knowledge-base management for articles and support content
- Customer satisfaction reporting and CRM integration
Evidence
No sourced metric on this project.
We shipped this system, but we do not have a measurement we can attribute to it. Rather than estimate a percentage, here is the scope in full — which is a claim you can check with the client.
Delivered
2026 — present
Engagement window recorded for this system.
Surface area
6 modules
Distinct things built, listed on this page.
Stack
13 technologies
Taken from the project's own dependency manifest.
01
The problem
Support teams need incoming requests, conversation context, ownership and service deadlines in one place.
02
The approach
Connected ticket handling, customer information and service automation in a shared workspace, with configurable queues and escalation rules.
03
The outcome
A support platform where a request can be tracked from intake to resolution, with reusable content and a visible owner.
Technology
The stack as shipped.
- React
- TypeScript
- Tailwind CSS
- TanStack Query
- Zustand
- Nx
- Vite
- C#
- .NET 10
- PostgreSQL
- Redis
- Kafka
- Docker
Related
