How-to support ticket zerodha support portal raise a query complaint grievance redressal

How to create a support ticket at Zerodha

From WebNotes, a public knowledge base. Last updated . Reading time ~10 min.

To create a support ticket at Zerodha , open the help article that matches your issue on the support portal at support.zerodha.com, scroll to the bottom, tap Create ticket, choose whether to log in, describe the problem in the Describe your issue in detail box, attach up to six files under 5 MB each, and submit. Zerodha issues a ticket number and replies within 48 working hours.

The ticket is Zerodha’s primary support channel, ahead of the phone line, because it leaves a written, trackable record of the query and routes it to the team that owns the topic. Zerodha does not run a single open contact form on its home page; instead the Create ticket button sits at the foot of each help article, so the article you choose sets the ticket’s category and the team it lands with. That design is the single thing most people get wrong, and it is the reason a ticket sometimes feels misrouted: the category came from the article, not from anything you typed.

This guide covers where the create-ticket flow lives, how the optional login changes what the team can see, what to write so the first reply resolves the issue, the 5 MB and six-file attachment limits, and how the ticket number then drives every later step, from tracking the status to escalating an unresolved grievance.

Conflict-of-interest disclosure. This guide is published by the WebNotes Editorial Team for informational purposes and is written independently. WebNotes operates a Zerodha account-opening referral programme, disclosed on the pages that carry the referral link; this guide does not carry it and earns no referral commission from the procedure described here.

Step-by-step procedure

The numbered box above gives the full sequence. The sections below expand the parts that trip people up: finding the right article so the ticket is categorised correctly, the login choice, and writing a description that gets resolved on the first pass.

1. Open the support portal and find the matching article

Go to support.zerodha.com and search for the topic of your issue, for example “fund withdrawal”, “DDPI”, or “IPO mandate”. The portal is organised as a knowledge base, and the Create ticket button appears only at the foot of an individual article, never on the home page or the category index. Open the article that sits closest to your problem. The team that handles withdrawals is different from the team that handles KYC , and the article you pick is what assigns the ticket, so a minute spent finding the right one saves a re-routing later.

If no article fits exactly, pick the nearest one in the correct area. The free-text description still reaches a human; the article only sets the starting queue.

2. Scroll down and tap Create ticket

At the bottom of the article, below the body text and any related-article links, tap Create ticket. On Kite web and the Kite app you reach the same flow through the support or help menu, which deep-links into the portal; the create-ticket form itself is identical because it is the same support.zerodha.com page. There is no separate ticket form inside Console or Kite ; both hand off to the support portal.

3. Choose whether to log in

A drop-down asks: “If you have a Zerodha account, we can help you more effectively. Would you like to log in?” Select Yes to sign in with your Zerodha credentials, or with your email and a one-time password. Logging in attaches your client ID, segment, and account state to the ticket, so the team can check your ledger, holdings, or order book without asking you to confirm identity first. Select No only when you cannot log in, for example before an account exists or after it has closed; the create-a-ticket-without-login route then verifies you with an email OTP instead.

4. Describe your issue in detail

Type the problem in the Describe your issue in detail field. A precise description is the difference between a one-reply resolution and a three-day thread. State the client ID, the platform (Kite web, Kite app, Console, or Coin), the exact error message or the order or transaction number, the date and time, and what you expected to happen. For a fund issue, include the UTR or transfer reference ; for an order rejection, paste the rejection reason verbatim. Avoid one-word tickets such as “withdrawal not working”, which force the team to ask for everything you could have supplied up front.

5. Attach evidence with Choose file

Tap Choose file to add files. The limit is up to 6 files, each smaller than 5 MB. Screenshots of the error screen, a contract note , a bank statement showing a debit, or a funds statement all speed resolution. If a screenshot or document exceeds 5 MB, do not skip the evidence; follow the attach-large-files route instead. For combining several images into one document, see how to convert images to PDF .

6. Submit and note the ticket number

Tap Create ticket to submit. Zerodha generates a ticket number and emails it to your registered address along with a copy of what you wrote. Save that number. It is the reference for every later reply, for tracking the status , and, if the matter is a formal grievance, for the escalation to the exchange and to SEBI SCORES that follows.

What category to pick, and why it matters

Zerodha’s support portal does not present a free category drop-down at ticket creation; the category is inherited from the article you opened. This is deliberate. A ticket opened from the “Transfer of funds” article reaches the funds team; one opened from the “Profile” article reaches the KYC team. If you open a generic article and describe a funds problem, the ticket may first land with the wrong team and be reassigned, adding a day.

The practical rule: search for the most specific article that names your problem, then create the ticket from it. If you are unsure which area your issue belongs to, the grievance redressal overview maps the common categories and the team each one reaches.

Response time and working hours

Zerodha states a reply within 48 working hours. Working hours exclude weekends and exchange holidays, so the clock on a Friday-evening ticket effectively starts the next working day. High-volume periods, such as the days around a large IPO allotment or a market-wide settlement issue, can stretch first-response times. The ticket queue is first-in, first-out within a team, so a duplicate ticket on the same issue does not jump you forward; it splits the thread and slows both. If a matter is genuinely urgent and time-critical, such as a stuck position, the call-and-trade desk on the Zerodha customer care number is the faster channel for that narrow set of issues.

From a ticket to a formal grievance

A support ticket and an investor grievance are not separate systems; the grievance ladder starts with the ticket. SEBI’s framework expects an investor to approach the intermediary first, which means raising and exhausting a Zerodha ticket before escalating. If the ticket is unresolved or the resolution is unsatisfactory, the next rungs are the Compliance Officer at complaints@zerodha.com , then the exchange grievance portal, then SEBI SCORES with its 21-day action-taken-report timeline, then SMART ODR . The ticket number you saved is the evidence that you began at the right rung; carry it through. The full ladder is set out in how to file an investor grievance against Zerodha .

See also

External references

References

  1. Zerodha support, How do I create a ticket at Zerodha? (as of 20 June 2026): support portal flow, Create ticket button, 6-file and 5 MB attachment limits, 48-working-hour response.
  2. Zerodha investor charter, on the right to have grievances redressed and the Compliance Officer contact complaints@zerodha.com (as of 20 June 2026).
  3. SEBI circular SEBI/HO/OIAE/OIAE_IAD-A/P/CIR/2023/145 dated 31 July 2023, Redressal of investor grievances through the SCORES platform, on approaching the intermediary first.

Related articles

Frequently asked questions

How do I create a ticket or raise a complaint at Zerodha?
Go to support.zerodha.com, open the help article that matches your issue, scroll down and tap Create ticket, log in or enter an email, describe the problem, attach up to 6 files under 5 MB each, and submit. Zerodha replies within 48 working hours.
Where is the Create ticket button on the Zerodha support portal?
It is at the foot of each help article, not on the support home page. Search for the article that fits your query first, then scroll to the bottom, where Create ticket appears. The article you pick sets the ticket’s category.
Do I have to log in to raise a Zerodha ticket?
No. Logging in with your Zerodha credentials helps the team see your account and answer faster, but you can also file by selecting No at the login prompt and entering an email address that an OTP then verifies.
How long does Zerodha take to reply to a ticket?
Zerodha states a response within 48 working hours on the support portal. Working hours exclude weekends and exchange holidays, so a ticket raised on a Friday evening may be answered the following week.
Can I attach a screenshot when creating a ticket?
Yes. Tap Choose file in the create-ticket form to attach up to 6 files, each smaller than 5 MB. Screenshots of the error, the order number, or a statement help the first reply resolve the issue instead of asking for details.
How do I track a ticket I have already raised?
Use Track tickets on support.zerodha.com and sign in to open My tickets, where every ticket and its status appears. Zerodha also emails you each time the ticket is updated, so the thread stays in your inbox too.
Is there a phone number instead of a ticket?
Zerodha runs a call-and-trade and support line, but routine queries are handled through tickets so there is a written record. For the current numbers and hours, see the Zerodha customer care number page. Account-specific changes still need a ticket.

Reviewed and published by

WebNotes Editorial Team

The WebNotes Editorial Team covers Indian capital markets, payments infrastructure and retail investor procedures. Every article is fact-checked against primary sources, principally SEBI circulars and master directions, NPCI specifications and the official support documentation published by the intermediary in question. Drafts go through a second-pair-of-eyes review and a separate compliance read before publication, and revisions are tracked against the SEBI and NPCI rule changes referenced in the methodology section.

Last reviewed
Conflicts of interest
WebNotes is independent. No relationship with any broker, registrar or bank named in this article.