HR Ticketing System in Pakistan — End the WhatsApp HR Era
In most Pakistani SMBs, HR queries live in WhatsApp — and die there. "Bhai, my January payslip nahi mila" → scrolled past, never resolved. A proper HR ticketing system routes, tracks, escalates and reports on every HR query the way IT and customer support has done for two decades. Here is what to look for.
Common HR query categories
- Letter requests — experience letter, employment letter, salary certificate, visa letter, NOC
- Payslip queries — "where is my payslip", "this deduction seems wrong"
- Leave queries — "how many casual leaves do I have", "is X type of leave eligible"
- Policy clarifications — "what is the policy on..."
- Insurance / medical claim queries — process, documents needed, status
- Document upload requests — degree, NIC, marriage certificate
- Address / bank detail update — change requests with audit
- EOBI / PF queries — registration status, contribution history
- Year-end tax certificate — issuance, queries
The 6 things HR ticketing must do
1. Categorised request creation
Employee picks category (letter / payslip / leave / policy / etc.), describes the request. Optional attachment. 30-second creation.
2. Auto-routing
Letter requests → HR letters team. Payslip queries → payroll team. Policy queries → HR policy lead. Routing per category, configurable.
3. SLAs
Acknowledge within X hours, resolve within Y hours, escalate if breached. Letter requests typically 2-3 business days; payslip queries 1 day; policy answers 1-2 days.
4. Status visibility
Requester sees current status (submitted / in-progress / resolved). Push notification on changes. No "any update?" follow-ups.
5. AI Q&A for routine questions
"How many casual leaves do I have left?" should not become a ticket — AI answers from the employee's own data. "What is the policy on X?" answered from company policy documents. Tickets only when AI cannot resolve.
6. Letter generation automation
For common letters (experience, employment, salary certificate), HR can generate from templates with the employee's data auto-filled. PDF created, signed (or digitally signed), delivered to the requester. Used to take 2 hours; now 5 minutes.
The HR ticket pattern report
Monthly: top categories, average resolution time, SLA breaches, frequent requesters. Patterns surface root causes:
- "60% of last month's tickets were salary slip queries" → distribute payslips automatically; reduce future tickets
- "40% were experience letter requests at the start of the month" → batch-generate
- "Manager X's reports raise 3x average tickets" → coaching opportunity
What WhatsApp-based HR loses
- No record after 30 days (chat scrolls)
- No SLA — depends on who feels like responding
- No metrics — cannot see patterns
- No audit trail — disputes have no record
- Mobile number changes — historical context lost
- Group chat noise — important requests buried
The integration that matters
With employee record
The ticket knows who the requester is — their department, role, location, tenure. HR can verify quickly.
With payroll
Payslip queries can pull the relevant payslip data directly. Letter requests use the same salary data.
With document management
Document upload requests link to the employee's document folder.
With mobile app
Tickets raised from mobile. Status seen on mobile. Push notifications.
The Zaffre HRM HR ticketing fit
Zaffre HRM helpdesk covers HR ticketing with categorisation, routing, SLAs, mobile access, AI self-service for routine queries, and letter generation automation. Same platform as HR / payroll, so context is instant. See: internal helpdesk guide.