How-to Zerodha account opening mobile number email ID

How to change the mobile or email before opening a Zerodha account

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

Changing the mobile number or email ID before a Zerodha account is opened is a pre-activation correction, and it works differently from the modification you would use later. While the application is still in progress, before the exchanges activate the account, there is no self-service toggle: you raise a Zerodha support ticket giving the new and the current contact details, and the team updates them within 48 working hours. This is distinct from the post-opening flow in how to change your registered mobile number and how to change your registered email ID , which run through Console or Kite with an OTP and an in-person verification. This guide covers the pre-activation route and the uniqueness rule that catches people who simply start over.

The reason the two routes differ is what each is protecting. After the account is open, the contact details are bound to a verified KYC identity, so a change must re-verify you through OTP and IPV . Before the account exists, there is no verified record yet, so the correction is a clerical fix to an in-progress application, handled by support rather than by an automated modification screen. Knowing which stage you are at tells you which procedure applies, and using the wrong one wastes a cycle.

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 procedure in the infobox above is the canonical flow. The sections below expand each step. The first step is a gate: confirm you are genuinely pre-activation, because if the account is already open, none of this applies and you want the post-opening modification instead.

1. Confirm the application is still in progress

This route is only for the window before the account is opened and the exchanges activate it. If your account is already open, you have a client ID and can log in to Kite , and the contact change runs through the post-opening modification flow , which requires OTP and IPV and is a different procedure entirely. Get this right first. Applying the pre-activation ticket method to an open account, or trying the Console modification on an in-progress application, both fail, because each tool is built for one stage only.

2. Decide which contact details are wrong

Pin down exactly what needs correcting: the mobile number, the email ID, or both. A common case is a typo in the email that means the OTP and the eventual welcome email would go to an address you cannot read. Another is a mobile number entered with a transposed digit, so the onboarding OTP never reaches you. You can correct the mobile, the email, or both in a single request, so list precisely the wrong values and the correct replacements before you open the ticket.

3. Raise a support ticket

Go to the Zerodha support portal and create a ticket asking to change the contact details before the account is opened. There is no in-flow self-service button for this during onboarding; the correction is handled by support. Raising a ticket, rather than abandoning the application and starting fresh, is the supported path, and it matters because starting fresh runs straight into the uniqueness rule described below.

4. Provide the new and current details

The ticket needs four values so the team can locate and amend the right in-progress application:

  • New mobile number: the number you will use to complete account opening.
  • New email ID: the email you will use to complete account opening.
  • Current mobile number: the number you want to replace.
  • Current email ID: the email you want to replace.

Giving both the old and the new values lets support match the application unambiguously, since the current details are how the in-progress record is indexed.

5. Wait up to 48 working hours

Zerodha updates the contact details within 48 working hours of the ticket. Do not, in the meantime, begin a new application with the correct details, because the in-progress application still holds the old mobile and email, and the system treats those as already registered. Starting over therefore creates a duplicate and can block the very details you are trying to move across. The wait is short; let the ticket complete rather than racing it with a second application.

6. Resume onboarding with the corrected details

Once support confirms the update, continue the account-opening flow. The onboarding OTPs, and later the welcome email with your user ID , will now arrive at the corrected mobile and email. From here the rest of the flow, the DigiLocker eKYC , the PAN validation, bank verification and IPV, proceeds normally, since only the contact details changed and not the identity basis.

The uniqueness rule, and why starting over backfires

A mobile number or email ID can sit against only one Zerodha account, and an in-progress, not-yet-completed application counts. This is the mechanism behind the error This mobile is already linked to another account or This email ID is already linked to another account: the value you are trying to use is held by an incomplete application of your own. The clean fix is the ticket route above, which moves the details across rather than leaving them stranded on an abandoned record. Trying to open a second application with the same correct details, or with the wrong ones again, only multiplies the conflict. If you have already created such a stranded record, the same support ticket is what unblocks it.

How this differs from the post-opening change

The contrast is worth stating plainly, because the search intent often blurs the two. Before activation, the change is a support-handled correction to an unverified application, needing only the old and new contact values and clearing within 48 working hours. After activation, the change is a modification to a verified account, running through Console or Kite with an OTP to confirm control and an in-person verification to confirm identity, because the details are now bound to a completed KYC record filed with a KRA . Same end result, a corrected mobile or email, but two different machines, one for each side of the activation line.

See also

External references

References

  1. Zerodha support, How can I change my mobile number or email ID before opening a Zerodha account, support.zerodha.com (as of 20 June 2026); raise a ticket with the new and current mobile and email; updated within 48 working hours.
  2. Zerodha support, error while modifying contact details on Console, support.zerodha.com (as of 20 June 2026); a mobile or email already linked to an account, including an incomplete one, cannot be reused.
  3. SEBI Master Circular on Know Your Client (KYC) norms for the securities market, October 2023, on contact-detail verification in account opening.

Related articles

Frequently asked questions

How do I change my mobile number or email before my Zerodha account is opened?
While the application is still in progress, there is no self-service toggle. Raise a Zerodha support ticket giving the new and the current mobile and email; the team updates the contact details within 48 working hours, distinct from the post-opening modification flow.
Why does Zerodha say my email or mobile is already linked to another account?
A mobile number or email ID can sit against only one Zerodha account, and an incomplete in-progress application counts. The value is held by your own stranded record. Raise the same support ticket to move the details across rather than starting a fresh application.
Can I just start a new application with the correct details instead of raising a ticket?
No. The old mobile and email stay registered on the in-progress record, so a fresh application hits the duplicate-linkage error and blocks the very details you want. The supported fix is a support ticket, which updates the existing application within 48 working hours.
What details does the support ticket need to change the contact information?
Provide four values: the new mobile number and new email ID you will use to finish onboarding, plus the current mobile number and current email ID you want to replace. The current details are how the in-progress application is indexed and matched.
How long does Zerodha take to update the mobile or email before opening?
Zerodha updates the contact details within 48 working hours of the ticket. Do not race it with a second application in the meantime. Once support confirms the change, resume onboarding and the OTPs and welcome email reach the corrected details.
How is the pre-activation change different from changing contact details after opening?
Before activation it is a support-handled correction to an unverified application, cleared within 48 working hours. After activation it is a modification to a verified account through Console or Kite with an OTP and in-person verification, because the details bind to a completed KYC record filed with a KRA.

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.