Reaching AJIO seller support: route it right, and put it in writing.
AJIO support is reachable — but what you get back depends almost entirely on how you file. This guide maps the channels that exist, shows how to route payments, catalog and logistics issues to the right queue the first time, and covers the follow-up cadence and paper-trail habits that separate answered tickets from ignored ones.
- The channels: Seller Central help and ticketing first, your category or account manager (where assigned) in writing second, written escalation on the existing record third. The support section of the panel lists current routes — trust it over old forum posts.
- What gets responses: the right queue, order IDs, the relevant extract attached, and a numbered specific ask. Payments, catalog and logistics are different teams — route the issue correctly the first time and you skip a full round-trip.
- Keep the paper trail: every promise in writing, every call summarised back by email the same day, follow-ups on the same thread on a weekly cadence. Plan timelines in ranges — days for routine queries, weeks or more for contested settlement disputes.
Payments, catalog and logistics are three different doors
The single highest-value habit with AJIO support is deciding what kind of issue you have before you file it. A settlement shortfall is a payments issue — it needs the settlement extract and order-level amounts, and it needs to reach a team that can see settlement data. A rejected or hidden listing is a catalog issue — it needs the style or listing reference. A pickup that never happened is a logistics issue — it needs the AWB, the manifest date, and the pickup attempts. File any of these under a generic category and the first response will be generic too, because it was written by a team looking at the wrong screen.
The second habit is writing for action. Agents resolve tickets they can act on without a second question: IDs listed, the extract attached, the dates in order, and an ask stated so precisely that yes is a complete answer. Sellers consistently report that a three-line factual ticket with the right attachments outperforms a page of justified frustration.
Seven habits that get AJIO tickets answered
None of these are tricks. They are the mechanics of being the easiest ticket in the queue to resolve — which, at marketplace scale, is the whole game.
- 01
Classify before you file
Payments, catalog, or logistics? Decide first, then pick the matching category in Seller Central. Correct routing is worth more than any wording — it puts the ticket in front of a team that can actually see the relevant data.
- 02
One issue per ticket, IDs up front
State the single issue in the opening lines and list every affected order ID plainly. Bundled grievances get partially answered and then closed; single-issue tickets get resolved or escalated cleanly.
- 03
Attach the extract, not a description
For payment issues, attach the settlement extract showing the shortfall line. For catalog, the listing reference and screenshots. For logistics, AWB numbers and manifest dates. Evidence attached beats evidence promised.
- 04
End with a numbered ask
Close every ticket with what you want, numbered: reconcile these five orders against the rate card, restore this listing, confirm pickup for this manifest. An agent should be able to action your ask without interpreting it.
- 05
Follow up on a fixed cadence
Weekly, on the same thread, two factual lines: the ask, the wait so far. A live thread keeps its history and its place; a fresh ticket starts from zero and fragments the record.
- 06
Escalate in writing, keep managers looped
Where you have a category or account manager, escalate by email with the ticket number in the subject. If anything is promised on a call, summarise it back in writing the same day and ask for confirmation.
- 07
Log everything as you go
Ticket ID, date raised, issue, status, promises made, next follow-up date. The log schedules your cadence and becomes the timeline that any higher escalation — or any formal route later — will ask you to produce.
A mis-routed ticket costs a round-trip — and the money waits with it
Say a settlement lands ₹2,300 short across a week of orders (illustrative — check your own extracts). Filed vaguely under a general category, the sequence runs: template reply, re-explanation, re-route, request for order IDs, then the actual review — each step days apart. Filed correctly with the extract attached and a numbered ask, the review starts at the first touch. Same issue, same money, but one version of the ticket spends weeks in transit before anyone qualified even reads it. For a two-person team, those round-trips also cost the scarcest thing you have: attention during dispatch hours.
The paper trail has its own payoff. Sellers report that disputes which eventually resolve in their favour are the ones where every promise, date and figure exists in writing on one thread — because whoever finally reviews the case can reconstruct it in minutes instead of adjudicating memories.
The best support ticket is the one you never have to raise
A large share of AJIO support traffic is really bookkeeping: did the settlement match the orders, did the deduction match the rate card, did the pickup actually happen. Robnu runs that bookkeeping continuously. It processes AJIO orders end to end and reconciles every settlement against what each order should have paid — so a ₹2,300 gap surfaces as a flagged line with the evidence attached, not as a bad feeling about this month's payout.
When something does need AJIO's side to act, you file from strength: order IDs, extracts and timelines already assembled by the system that watched it happen. And for claimable deductions, Robnu files the claim itself — fully autonomous filing is rolling out, and a rare claim still asks you for one approval click before it goes.
AJIO seller support, answered
The primary route is the help and ticketing section inside AJIO Seller Central — raise the issue from the panel so it is tied to your account and the affected orders. Sellers with an assigned category or account manager have a second route: a written email keeping the manager in the loop, with the ticket number referenced. The support section of the panel lists current channels, and those change over time — treat the panel as the source of truth rather than contact details copied from old forum threads or third-party blogs.
Documented seller reports point at the same two culprits again and again. The first is routing: a payment discrepancy filed under a general or catalog category lands with a team that cannot see settlement data, so the reply is generic. The second is vagueness: a ticket that says payments are wrong, without order IDs, settlement extracts or a specific ask, leaves the agent nothing to check. Route the issue to the right queue, attach the numbers, and state exactly what you want — first-touch quality improves sharply.
Four things. The order IDs affected, listed plainly — not described in prose. The relevant extract attached: the settlement report line for payment issues, the listing reference for catalog issues, the AWB and pickup dates for logistics issues. The dates of each event, so the agent can reconstruct the timeline without asking. And a numbered, specific ask at the end — reconcile these five orders against the rate card, restore this listing, confirm this pickup — phrased so the agent can action it rather than interpret it.
Escalate in writing, and keep everything on the record. Follow up on the same ticket thread on a fixed cadence — weekly is a reasonable default — with a short factual note restating the ask and the wait so far. If you have an assigned category or account manager, loop them in by email with the ticket number in the subject. If anything is promised on a call, send a written summary back the same day asking for confirmation. Verbal promises evaporate; written ones become the record your next escalation stands on.
Treat any specific number you read online with suspicion — timelines vary by issue type and season, so plan in ranges. Routine catalog and logistics queries are often addressed within days. Payment and settlement disputes are slower because they cross teams: seller reports commonly describe weeks, and contested cases running longer. What shortens your side of the wait is routing correctly the first time and never letting a thread go quiet — check the support section of the panel for current expectations on each issue type.
Most support tickets are really evidence problems, and Robnu solves those before they start. It runs AJIO order operations end to end, so every order carries its own documented timeline — acceptance, documents, dispatch, manifest, settlement — and its reconciliation catches payment gaps against expected amounts, order by order. When you do need to raise a ticket, the extract and the IDs are already assembled. And for claimable deductions, Robnu files the claim itself — fully autonomous filing is rolling out, with a rare claim asking for one approval click.
Where this comes from
- AJIO Seller Central help and ticketing documentation — the support section of the panel lists current channels and issue categories.
- Documented seller reports on response quality, routing and escalation outcomes: public seller community threads (Reddit r/IndiaBusiness, seller Facebook groups, professional networks), 2025–2026.
Related guides & pages
AJIO payment not received
Trace a missing settlement before you ticket it — the checklist.
AJIO seller operations
The daily AJIO workflow the support tickets are trying to protect.
Meesho support escalation
The same ladder discipline, applied to Meesho's queues.
Revenue protection
How Robnu reconciles settlements and files claims for you.