Navigating Government e-Marketplace (GeM) support efficiently requires knowing exactly which channel to use. Every official GeM support channel—from toll-free helpline numbers and helpdesk email to in-portal tickets—serves a specific purpose. This guide details which channel fixes which problem, how to manage escalations when tickets stall, and how to avoid fraudulent numbers.
| Channel | Details (verified Jul 2026) | Best for |
|---|---|---|
| Toll-free helpline | 1800-419-3436 / 1800-102-3436 9 AM–10 PM, Mon–Sat |
Quick questions, ticket status, navigation help |
| Helpdesk email | helpdesk-gem@gov.in | Written queries with attachments |
| Railway buyers/sellers | 0755-6627300 9 AM–10 PM Mon–Sat |
Railway-specific procurement queries |
| Defence buyers/sellers | 0755-6627400 9 AM–10 PM Mon–Sat |
Defence-specific queries |
| Walk-in helpdesk | 2nd Floor, Jeevan Tara Building, 5-Sansad Marg, near Patel Chowk, New Delhi-110001 9 AM–6 PM Mon–Fri |
In-person help (GeM office in Delhi) |
| In-portal incident/ticket | Seller dashboard → support/incident section path | Account-specific problems — the channel with an audit trail |
| Portal maintenance | gem.gov.in announcements | Checking if "the site is down for everyone" |
Note: The ticket system is 24×7 for filing; phone support runs the 9–10 window noted above.
Phone the helpline for: How-do-I questions, checking why something looks stuck, or ticket status. Expect general guidance, not account surgery — agents can explain process but rarely fix data.
Raise an incident for: Anything specific to your account — verification stuck, PAN validation failed, listing rejected, payment not reflecting, CRAC not generated, or user access issues. Tickets create the paper trail that escalation later depends on.
Email for: Queries needing attachments or formal record — but mirror anything important as an incident too; tickets track, inboxes drown.
Based on extensive observation of ticket successes and failures:
One issue per ticket. Bundled complaints get partial answers and closed tickets.
Category it correctly. Mis-categorized incidents bounce between desks.
Front-load the identifiers: Seller ID, order/bid number, exact error text (screenshot attached), and date-time it occurred.
State the ask, not just the pain: "Please re-trigger PAN validation; records were corrected at NSDL on [date]" beats "not working please help".
Note the ticket number and check status every 2–3 working days via the ticket status section.
If closed unresolved, reopen or re-file referencing the old number — history compounds your case.
Honest boundary-drawing prevents wasted weeks of effort:
Policy isn't negotiable by ticket. Charge structures, vendor assessment requirements, and category rules — support explains them, never waives them.
Buyer-side delays (CRAC sitting ungenerated, payment file not processed) — tickets nudge, but resolution often needs correctly-addressed buyer-side follow-up.
Your document problems — PAN/Aadhaar mismatches and GST issues get fixed at NSDL, UIDAI, or GST portals, not on GeM.
Strategy questions — "why am I not winning bids" isn't a support ticket; it requires professional bid analysis.
Escalation, when tickets stall: Follow the working ladder — reopen with history → re-file referencing prior tickets → written escalation to the helpdesk email with the ticket trail → public-handle nudge with ticket number (measured tone). Keep every ticket number; escalation without a trail is just complaining.
Beware fake "GeM helpline" numbers: Search results and social media carry fraudulent numbers run by scammers who "help" for a fee or phish credentials. Rules of thumb: official support never demands payment (GeM registration is free), never asks for your password/OTP, and official numbers live on gem.gov.in.