Skip to main content
Module 06 · Candidate Support

Support & Ticketing

A built-in helpdesk for lakhs of anxious candidates: categorize, route, and resolve issues inside the platform, with war-room mode when the exam is live.

  • 92% within-SLA resolution
  • Exam-day war room mode
  • Statutory grievance trails
<4h
Median first response
92%
Tickets resolved within SLA
18%
Volume deflected by KB
24/7
Self-service availability

Medians across production drives; deflection rate measured as knowledge base sessions that did not convert to tickets.

Capabilities

A Helpdesk That Knows What Drive It Is Serving

Generic helpdesks fail exams because context lives elsewhere. Here the ticket, the candidate, and the examination record share one system, which is why resolution times stay sane even during notification-week floods.

Unified Ticket Intake

Web portal, email, and phone-logged queries all become tickets against the candidate record. Agents see application status, payment history, and center allotment beside the conversation, so answers come from context rather than guesswork.

Email, WhatsApp, phone, and web channels
Candidate context auto-attached
Duplicate detection across channels
Priority scoring by impact

Category-Aware Routing

Admit card issues route to drive admins; payment failures route to finance with gateway references attached; technical faults route to engineers. Nothing sits in a generic inbox waiting to be triaged by hand.

02
Key Detail

Tickets route based on category, drive context, and agent expertise. SLA clocks start on creation and escalate automatically on breach.

SLA Clocks & Escalation

Each category carries its own response and resolution targets. Breaching tickets escalate automatically through the hierarchy, and the dashboard shows exactly which queues are burning.

03
Key Detail

Candidates file grievances in their preferred language. The system translates for agents while preserving the original text in the record.

Multilingual Candidate Experience

Candidates file and track grievances in English or Hindi with regional language expansion per drive. Automated acknowledgments cite their ticket number and expected resolution window.

04
Key Detail

A searchable knowledge base deflects common questions. Usage analytics surface gaps so content stays current across drives.

Knowledge Base Deflection

Before a form opens, candidates see answers to the questions driving this week’s ticket volume. Well-maintained articles routinely absorb double-digit percentages of would-be tickets.

05
Key Detail

Trend analysis identifies systemic issues: a spike in payment failures from one gateway, or admit card errors for one center batch.

Issue Trend Analytics

Weekly clustering reveals systemic problems: one payment gateway failing on a bank network, one center with confusing directions, one eligibility rule nobody understands. Fix causes, not just tickets.

06
Key Detail

During live exams, the helpdesk shifts to war-room mode with prioritized queues, escalation chains, and real-time incident dashboards.

Across the Drive

Support Needs Change Every Phase. So Does the Queue.

  1. Application Window

    Onboarding volume

    Peak intake around payment deadlines and document uploads. Deflection articles publish proactively as error patterns emerge, keeping queues under SLA despite lakhs of candidates.

  2. Pre-Exam Fortnight

    Admit card & logistics

    Center change requests, admit card download failures, and travel queries dominate. Routing sends them straight to drive admins holding the allotment controls.

  3. Exam Day (War Room)

    Minutes matter

    The module switches into war-room mode: priority lanes for in-center incidents, direct lines to the CBT command dashboard, and every action timestamped for the post-drive review.

  4. Result Season

    Grievance compliance

    Score challenges and re-evaluation requests run on statutory clocks with numbered acknowledgment, ensuring RTI-grade traceability of every grievance filed and closed.

Service Levels

Default Targets Boards Start With

Categories carry different urgency because a locked-out candidate on exam morning is not the same as a receipt copy request. These defaults tune per board.

Default service level targets by ticket category
CategoryFirst ResponseResolutionEscalates To
Exam day incident15 minutesUntil resolved on-siteDrive controller
Payment failure2 hours24 hours with refund proofFinance desk
Admit card access4 hoursSame dayDrive admin
Eligibility dispute1 business dayPer notification timelineBoard committee
General information8 hours48 hoursAuto-close eligible
  • Breaching tickets escalate automatically; no queue depends on someone noticing
  • Candidates see their own SLA clock in the portal, which cuts follow-up tickets sharply

Answers

Frequently Asked Questions

Common questions from examination bodies evaluating this module. For anything specific, our team responds within one business day.

Still have questions? Talk to our examination specialists or check our API reference.

Content last reviewed August 2026 by the EMAP India examination operations team. Capabilities described here reflect current production behavior.

Drowning in Candidate Emails Right Now?

Let us show you the same volume handled as categorized, routed, SLA-tracked tickets with full candidate context on every screen.