How ashishlukka1/sales-ticket works
Sales Ticket converts support conversations into role-routed revenue intelligence, then exposes ticket, account, memory, graph, voice, and chat workflows through a React dashboard. The principal documented path is Zendesk ticket ingestion → signal classification and draft generation → persistence and retrieval/analytics → team review. Controller excerpts confirm ticket classification, drafts, embeddings, and audio handling; README capabilities fill in unsampled dashboard and service branches, so those links are documented architecture rather than source-verified call chains.
Main entry points: index.js HTTP application · ticketController.js Ticket intake · Dashboard.jsx Dashboard shell · App.jsx App routes
Components 24
Team workspace
- Landing page
client/src/LandingPage.jsx - Login and register
client/src/components/LoginRegister/AuthPage.jsx - Dashboard shell
client/src/components/dashboard/Dashboard.jsx - Ticket views
client/src/components/dashboard/views/AllTickets.jsx - Health and memory
client/src/components/dashboard/views/AccountHealthView.jsx - Graph views
client/src/components/dashboard/views/SignalsFeedView.jsx - Voice tickets
client/src/components/dashboard/views/VoiceView.jsx - AI copilot
client/src/components/dashboard/ChatbotWidget.jsx - App routes
client/src/App.jsx
Express API
- HTTP application
server/index.js - Identity and roles
server/controllers/userController.js - Ticket intake
server/controllers/ticketController.js - Chat retrieval
server/controllers/chatController.js - Account memory
server/controllers/memoryController.js - Graph analytics
server/controllers/graphController.js
Signal intelligence
- Signal classifier
server/utils/groqClassifier.js - Reply drafting
server/utils/aiDraftGenerator.js - Embedding model
server/utils/embedding.js
Persistence and retrieval
- MySQL records
server/config/database.js - Account graph
server/config/neo4j.js
External services
- Zendesk tickets
- Groq AI
- Zendesk reply delivery
server/utils/zendeskSender.js
Other components
- Team member
Connections 37
- Team member → App routes: uses
- App routes → Landing page: routes
- App routes → Login and register: routes
- App routes → Dashboard shell: protects
- Team member → Zendesk tickets: submits tickets
- Zendesk tickets → HTTP application: sends payload
- App routes → HTTP application: API requests
- Login and register → HTTP application: auth requests
- Dashboard shell → Ticket views: shows
- Dashboard shell → Health and memory: shows
- Dashboard shell → Graph views: shows
- Dashboard shell → Voice tickets: shows
- Dashboard shell → AI copilot: shows
- HTTP application → Identity and roles: dispatches
- HTTP application → Ticket intake: dispatches
- HTTP application → Chat retrieval: dispatches
- HTTP application → Account memory: dispatches
- HTTP application → Graph analytics: dispatches
- Ticket intake → MySQL records: reads and writes
- Ticket intake → Signal classifier: classifies
- Signal classifier → Groq AI: requests inference
- Ticket intake → Reply drafting: generates replies
- Reply drafting → Groq AI: requests inference
- Ticket intake → Embedding model: embeds tickets
- Ticket intake → Zendesk reply delivery: sends approved reply
- Zendesk reply delivery → Zendesk tickets: delivers reply
- Ticket intake → MySQL records: stores embeddings
- Chat retrieval → MySQL records: loads context and saves sessions
- Chat retrieval → Embedding model: embeds query
- Chat retrieval → Groq AI: requests response
- Account memory → Account graph: queries account graph
- Graph analytics → Account graph: queries analytics
- Graph views → HTTP application: requests graph data
- Health and memory → HTTP application: requests account data
- Ticket views → HTTP application: requests tickets
- Voice tickets → HTTP application: requests audio
- AI copilot → HTTP application: sends chat