Skip to content

feat: ZenDesk Support Inbox SPA — Dashboard, Ticket Inbox, Workspace, Macros & SLA Tracker #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ernestofosu05 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: ZenDesk Support Inbox SPA — Dashboard, Ticket Inbox, Workspace, Macros & SLA Tracker #29

ernestofosu05 wants to merge 1 commit into from

Conversation

@ernestofosu05
Copy link

@ernestofosu05 ernestofosu05 commented Feb 1, 2026

PR: ZenDesk Support Inbox SPA

Title: feat: ZenDesk Support Inbox SPA — Dashboard, Ticket Inbox, Workspace, Macros & SLA Tracker

Closes: #3

What's Included

A fully-functional ZenDesk-inspired support inbox SPA with 5 interconnected views, built for RL agents to practice triaging tickets, applying macros, and coordinating escalations.

Views

View Description
Agent Dashboard Queue health metrics (new/open/pending/solved/SLA warnings/breaches), personal performance stats (resolved, avg response time, satisfaction), urgent tickets list, recent activity feed
Ticket Inbox Filterable list (status, priority, tags), full-text search, bulk actions (set open/pending/solved), select all, infinite scroll pagination
Ticket Workspace Tabbed view — conversation history, internal notes, customer profile. Supports add note, assign agent, change status/priority, apply macro. All persisted via dojo.setState
Macros Library 6 canned responses across 4 categories (General, Technical, Resolution, Billing). Each macro has actions (setStatus, setPriority, addTags, replyTemplate). Quick-apply to any open ticket
SLA Tracker Timeline widget with breach/warning/ok status, time remaining or overdue, escalation log

Seed Data

  • 10 realistic tickets across all statuses and priorities
  • 8 customers (diverse companies and lifecycle stages)
  • 2 agents with performance stats
  • 6 macros with templated responses
  • 10 automation events (ticket created, assigned, reply sent, status changed, SLA breach, escalation)

Tech

  • Scaffolded under zendesk/app/ per repo structure
  • Vite + React 19 + TypeScript (strict mode)
  • @chakra-dev/dojo-hooks for ALL shared state — no bespoke stores
  • Tailwind CSS v4 via @tailwindcss/vite
  • vite-plugin-singlefile → single dist/index.html (271 KB, 79 KB gzipped)
  • lucide-react for icons
  • No auth flows — boots straight into business context
  • Responsive layouts at 1280px and 1440px
  • Fully offline with seed data

Build

pnpm install && pnpm run build
# tsc: 0 errors
# vite: dist/index.html 271 KB (79 KB gz)

@ernestofosu05
feat: ZenDesk Support Inbox SPA with Dashboard, Ticket Inbox, Workspa…
010043d 
…ce, Macros, and SLA Tracker Chakra-Network#3

- Agent Dashboard with queue health metrics, personal performance stats, urgent tickets list, activity feed
- Ticket Inbox with filters (status, priority, tags), search, bulk actions, select all, infinite scroll
- Ticket Workspace with tabbed view (conversation, internal notes, customer profile), reply, assign, macros
- Macros Library with 6 canned responses in 4 categories, quick-apply to any open ticket
- SLA Tracker with breach/warning/ok timeline, time remaining/overdue, escalation log
- 10 seeded tickets, 8 customers, 2 agents, 6 macros, 10 automation events
- Vite + React 19 + TypeScript strict + Tailwind v4 + @chakra-dev/dojo-hooks
- Single-file build via vite-plugin-singlefile (271 KB / 79 KB gzipped)
- Responsive layouts at 1280px and 1440px, lucide-react icons, fully offline
@ernestofosu05 ernestofosu05 mentioned this pull request Feb 1, 2026
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@ernestofosu05