Helpdesk
Internal support ticketing and knowledge platform built for FenceOS, a fencing-industry CRM automation company.
The original project URL returned an availability error when checked on 17 October 2026. The case study and original screenshot remain available here.
The challenge
Support requests were scattered across email and GoHighLevel conversations with no shared queue, no SLA visibility, and no searchable internal knowledge base for the support team.
The approach
A ticketing application built on Next.js (App Router) with React and TypeScript, backed by Supabase for the database, authentication, and file storage, and deployed to Vercel.
What’s inside
- Ticket queue with status/priority workflow and internal-only notes
- Role-based access via Supabase Auth (agent vs. admin)
- Searchable internal knowledge base backed by Postgres
- Admin-editable settings and ticket categories
Behind the interface
Next.js App Router with separate client/admin/api route groups, Supabase Postgres with row-level security, Supabase Auth for role-based access, Supabase Storage for attachments.