How-to Zerodha support ticket support code account access

How to reach Zerodha support from an unregistered number

From WebNotes, a public knowledge base. Last updated 19 June 2026. Reading time ~8 min.

Key facts

Time required	A few minutes to raise a ticket; Zerodha replies within 48 working hours
Cost	Free
Documents needed	Your registered mobile number and support code for the call route; identity and address proof for an offline number change

Procedure

Find your support code in your Zerodha accountLog in to Kite or Console and locate the support code, also shown as a ZPIN, in the support or contact section of your profile. The call route from an unregistered number needs it.
Call support and enter your registered number plus support codeCall the Zerodha support line. From an unregistered number the system asks for your registered mobile number followed by the support code, entered together with no separator, for example 998XXX666 then 0007 as 998XXX6660007.
If you cannot call, raise a ticket on the support portalOpen support.zerodha.com, find the relevant article, scroll to the bottom, and tap Create ticket. Choosing to log in with your Zerodha credentials links the ticket to your verified account even from an unregistered device.
Describe the issue and attach proofType the problem under Describe your issue in detail and attach up to six files under 5 MB each, such as a self-attested ID, then submit. Zerodha replies within 48 working hours and you track the ticket on the portal or by email.
Raise the number change with the required documentsIf the unregistered number is your new number, request a registered-mobile update. The online change runs through Kite; an offline change uses the account-modification and CDSL KYC forms with a signature matching your account-opening signature.

When you cannot use your registered mobile number, a lost SIM, a number you have stopped using, travel on a different number, the usual call-and-login path to Zerodha breaks because both depend on that number. This guide covers the routes that still work: the call route that authenticates you with a support code instead of the registered SIM, the ticket route on the support portal, and the registered-number change itself, along with the identity verification Zerodha requires at each step.

The constraint is that Zerodha will not act on account-sensitive requests for an unverified caller. Every route below substitutes a different proof for the registered-SIM OTP: a support code on the call line, a logged-in session on the ticket portal, or a signature-matched form for an offline number change. Pick the one that fits what you have access to.

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 procedure infobox above lists the five steps across the three routes. The H3 subsections below expand each, name the exact controls and the support-code format Zerodha publishes as of 19 June 2026, and set out the verification each route applies.

1. Find your support code in your Zerodha account

The support code, also called a ZPIN, is the credential that lets the call line trust a caller who is not phoning from the registered SIM. Log in to Kite or Zerodha Console on any device and open the support or contact section of your profile to read it. If you can still log in but cannot use your registered SIM, this is the fastest route, because the support code travels with your login rather than your phone.

2. Call support and enter your registered number plus support code

Call the Zerodha support line. From an unregistered number the system asks you to enter your registered mobile number followed by the support code, keyed together with no separator. Zerodha’s published example: registered number 998XXX666 and support code 0007 are entered as 998XXX6660007. The registered number identifies the account and the support code authenticates you in place of the registered-SIM OTP, which is why both are needed together.

3. If you cannot call, raise a ticket on the support portal

When the call route is not workable, open support.zerodha.com , find the article closest to your issue, scroll to the bottom of the page, and select Create ticket. At the prompt, “If you have a Zerodha account, we can help you more effectively. Would you like to log in?”, choose to log in with your Zerodha credentials, or sign in with your email and an OTP. Logging in ties the ticket to your verified account even though you are on an unregistered device, which is the proof Zerodha uses on this route.

4. Describe the issue and attach proof

Type the problem into the Describe your issue in detail field. Attach up to six files, each under 5 MB, through Choose file, for example a self-attested identity proof if the request touches account access. Submit with Create ticket. Zerodha replies within 48 working hours, and you track the ticket on the support portal or through email. Tickets do not depend on the registered SIM at all, which makes this the reliable route when the number is genuinely lost.

5. Raise the number change with the required documents

If the unregistered number is the new number you intend to keep, request a registered-mobile update so future logins and OTPs reach you. The online change runs through Kite where the existing mobile is Aadhaar-linked. Where the mobile is not linked to Aadhaar , or for joint, non-individual, or international-number cases, the change is offline using the account-modification and CDSL KYC forms, with a signature matching your account-opening signature. The full walkthrough is in how to change your mobile number on Zerodha .

The identity proof Zerodha requires on each route

Each route swaps a different proof for the registered-SIM OTP. The call route trusts the support code plus the registered number you key in. The ticket route trusts a logged-in session, or an email OTP, tied to your account. The offline number change trusts a signature on a physical form, matched against the signature held from account opening. None of the three lets a stranger move money or change contact details without one of these proofs, which is the point of the design.

This matters most when access is partial. If you can log in but cannot receive SMS, the support code and the ticket route both work. If you cannot log in at all, the ticket route still opens via email OTP, and the offline form route remains available for the number change itself. Map your situation to the proof you still hold before you start.

Changing the number before an account exists

If you have not opened a Zerodha account yet and need to change the mobile or email you started signup with, the fix is a ticket, not a call. Create a ticket and include the new mobile number you will use to finish account opening, the new email ID, and your current mobile number, so support can reconcile the half-completed application. This is a separate flow from changing the registered number on a live account, which is covered in how to change your mobile number on Zerodha .

Guarding against support-impersonation scams

Zerodha states that calls to resident customers are made only from its official numbers, and that customers cannot call those numbers back. Any caller claiming to be Zerodha support and asking you to share an OTP, install a screen-sharing app, or read out your support code is running a scam, because genuine support never needs your OTP. Keep the support code as private as a password; it is the credential that authenticates you on the call line, so handing it to a caller hands them your account. Verify Zerodha is safe practices and route every doubtful contact back through the official support portal.

What can go wrong

No support code to hand. The call route from an unregistered number needs it. Retrieve it from your logged-in profile first; if you cannot log in either, use the ticket route with an email OTP instead.
Keying the support code with a separator. Enter the registered number and support code as one continuous string with no space, dash, or hash, exactly as in Zerodha’s example.
Expecting an instant ticket reply. Tickets are answered within 48 working hours, not in real time. For a time-sensitive issue, use the call route if you can.
Sharing the support code with a caller. Genuine Zerodha support never asks for your OTP or support code. A request to share either, or to install a screen-share app, is a scam; end the call and use the portal.
Confusing pre-account and live-account changes. Changing the number on a half-finished signup is a ticket with old and new details; changing it on a live account uses the Kite flow or the offline forms. Use the right one for your stage.

External references

References

Zerodha Support, “Can I reach Zerodha support from an unregistered number?” support.zerodha.com, accessed 19 June 2026. Confirms the call route asks for the registered mobile number followed by the support code, keyed together, and shows the worked example.
Zerodha Support, “How can I create a ticket or raise a complaint at Zerodha?” support.zerodha.com, accessed 19 June 2026. Confirms the Create ticket flow, the login prompt wording, the Describe your issue field, the six-file 5 MB attachment limit, and the 48-working-hours reply time.
Zerodha Support, “How to change the registered email ID and mobile number with Zerodha?” support.zerodha.com, accessed 19 June 2026. Confirms the online Kite route and the offline account-modification and CDSL KYC form route with signature matching.

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: 19 June 2026
Conflicts of interest: WebNotes is independent. No relationship with any broker, registrar or bank named in this article.