SupportCentral runs on your own PHP & MariaDB host. Tickets, company assets, employees, vendors, subscriptions and approvals — one system instead of five spreadsheets and an inbox.
An employee emails the helpdesk; their lead and manager reply; the employee replies again. SupportCentral reads the mail headers and keeps every message on the same ticket — even if the subject line changes.
A keyword engine (pre-loaded with a real IT triage table) reads each ticket and assigns a category — and flags requests that belong to HR or Finance as out of scope, so your queue stays clean.
Track assets through their whole life — assign, return, replace, dispatch, retire. Allocation views break the fleet down by processor and by age, with CSV export and a 3-year ageing alert.
| Asset | Holder | Age | Status |
|---|---|---|---|
| LT-2291 · i7 | A. Sharma | 1–2 yr | in use |
| LT-1840 · i5 | R. Mehta | 3+ yr | refresh due |
| LT-2410 · M2 | unassigned | < 1 yr | in stock |
A built-in monthly report shows tickets resolved per agent, average handle time, average first response, and SLA-met percentage — with CSV export. Or build your own in Report Studio.
| Agent | Resolved | AHT | SLA met |
|---|---|---|---|
| Priya R. | 132 | 3h 12m | 96% |
| Arjun K. | 118 | 4h 02m | 91% |
| Sara D. | 97 | 5h 40m | 84% |
Twelve ready-made roles, fully editable — or create custom roles by ticking permissions per module. Changes apply immediately, and custom roles are assignable to users right away.
Turn events into actions: notify admins on a new ticket, alert when a vendor contract is expiring, or flag an asset that has crossed three years in service. You decide what fires — everything is opt-in.
A chat assistant greets every visitor, works out whether the question is IT or HR, answers from your own knowledge base, and only involves a person when it needs to. Two personas, one engine — and ask the wrong desk, it offers to hand you across with your question.
Turn an article into a wizard that walks someone through the fix one screen at a time. If a step doesn't work the next one appears — and if nothing does, it opens a ticket that already lists what they tried.
| Step | Outcome |
|---|---|
| 1 · Join in the browser | fixed it |
| 2 · Sign in, don't sign up | next step |
| 3 · Still stuck | ticket pre-filled |
The waiting queue refreshes on its own, and every chat can be attended, transferred to the other helpdesk, or declined politely. IT agents see IT chats, HR agents see HR chats, owners see everything.
Intake captures the serial, power state and remote-access ID up front — with video for intermittent faults — and links the record to the asset automatically. Replacements dispatch with tracking, and the case closes only once receipt is confirmed and the old unit is back.
Assets break down by processor and memory with unit counts and the monthly rent for each — a grand total you can reconcile against the invoice. Click a line to see exactly those machines; export to XLS or PDF.
| Configuration | Units | Rent / month |
|---|---|---|
| i3 · 8GB | 186 | ₹2,65,440 |
| i5 · 16GB | 87 | ₹2,30,570 |
| i7 · 32GB | 31 | ₹1,51,650 |
| Total | 418 | ₹10,25,290 |
Anyone can raise a request without an account, so the public endpoints are rate-limited: submissions, sign-in attempts, reset emails, sign-ups and chat starts all cap per client. A flood becomes “please slow down” instead of a buried queue — and real users are never locked out if the limiter itself fails.
Merge two tickets into one, run incidents / problems / changes, publish KB articles, take live chat, and open a service catalog with approvals — all under one roof.
Ready? Deploy on your host and open /install to get started.