IRCTC Agent Forgot Password or Locked Out?

You open the agent login on a busy morning, a customer is waiting for a ticket, and the page says no. Maybe you forgot the password. Maybe the screen shows a lock message. Maybe nothing arrives on your phone. Your first instinct is to try again and again, or to pay the first person who says they can fix it.

Don’t do either. A forgotten password, an expired ID and a suspension are three different problems, and each one has a different fix. Work out which one you have before you pay or change anything. This guide shows how to do that, what to write to support, and what to say to the customer in front of you.

Are you on the right portal?

SiOnline’s agent sign-in routes are different for OTP login and DSC login. Use the agent login guide to pick the route assigned to your ID. Then retype the username from your own registration record, instead of relying on what the browser filled in.

If the right route accepts it, carry on only on that official page. If the error stays, write down its exact wording and move on to the next check. The exact words matter. “Something went wrong” and “your account is blocked” lead to very different next steps.

What does the symptom point to?

Use this table to sort the problem, not to diagnose it. The wording on a screen can’t tell you everything about your account. Ask support to separate a credential problem from an account restriction before you pay for anything.

Is changing your password the same as recovering it?

No. IRCTC’s Agent Interface manual, item 11, describes a profile-password change for someone who is already logged in. It isn’t a forgotten-password recovery procedure. And it’s no proof that support can reset an account you can’t get into.

If the official page offers account recovery, follow its steps yourself. Don’t use a recovery link from a caller you didn’t ask for. Don’t give anyone a new password to set up for you. And stop if the page asks for something you can’t verify, then report that screen through your usual support channel.

Think about what you’re really dealing with, too. If you simply can’t remember the password, say exactly that. If you’ve seen a message you didn’t expect, or you think someone else used your login, keep the message and say why you suspect it. Don’t blame a colleague or a provider on a hunch. Getting back in and checking an odd transaction may need two separate answers, so ask for both and don’t assume one covers the other.

Could the ID have expired?

IRCTC’s Internet Cafe Scheme norms, item 4, checked on 18 October 2026, say expired centre access is deactivated unless its Principal renews recognition and tells IRCTC. So if your ID has run out, a guessed password fix won’t help. You need a renewal check.

Put your renewal receipt next to the validity the provider has on record. The agent ID renewal page covers the cost categories. If you already have a receipt, ask the provider to reconcile that receipt before you pay again. A bank debit alone doesn’t prove the account item was recorded. Send the receipt reference, the account it was for and the period printed on it, and ask what the provider received and applied.

One more thing. Don’t buy a replacement ID just because the old one won’t sign in. That’s a bigger and different decision.

What if you can’t reach the registered phone?

Be clear about what you know. Do you still control the phone? Does the account page show a number you recognise? If you don’t recognise it, ask the provider to check the record, rather than requesting message after message.

If the phone is lost or replaced, ask which official account-update route applies. Changing a number in another SiOnline service, or on a passenger’s PNR, does not update the agent-login record. When you write to support, don’t put the full number in a public complaint. Ask what identity evidence is needed, and send documents only through a route you’ve checked.

Keep the purposes apart, too. A passenger’s booking OTP is not a stand-in for your agent-login authentication. And never give your login OTP to someone who says they need it to trace a ticket.

How do you write a support request that can be checked?

A good request lets the support team see the problem without guessing. Include:

• your agent ID,
• the portal address you used,
• the exact error message,
• whether you can receive messages on the registered mobile,
• any renewal receipt reference, and
• whether the error comes before or after OTP authentication.

If you attach a screenshot, hide passwords, OTPs and any customer details that have nothing to do with the problem.

Contact SiOnline support with your agent ID and the exact error, or use customer care. Never send an account password or login OTP. Ask for the next verified action and keep the reply. A support request doesn’t set a restoration deadline, and it doesn’t entitle you to reinstatement.

An example of keeping your notes straight

Say a shop owner can open the assigned agent page but can’t remember the password. There’s also an old renewal receipt, but the owner hasn’t worked out which period it covers. This is just an exercise in organising a request. It isn’t a real account diagnosis and it isn’t an official recovery form.

The owner writes down two questions and keeps them apart:

1. What is the right recovery route for an account I can’t get into?
2. What validity period does this receipt cover, and was it applied to my account?

The owner doesn’t write “renewal will reset my password”. That would join two questions nobody has answered yet. If the reply answers only the validity question, mark that one as answered and leave the recovery question open. If the reply gives a recovery route first, keep that instruction, but don’t treat it as confirmation of what the receipt covers.

It also helps to ask support to tie each answer to the same agent reference. If a reply is about a different shop account or a different service, say so before you act on it. Don’t build one instruction out of several messages that are about different accounts.

How do you read the answer you get back?

Match the reply to what you actually saw.

• A credential reply. Does it talk about an account you can’t enter, or does it assume you’re already signed in? If it points you to a profile menu you can’t reach, say that, and ask for the route for an inaccessible account.
• A renewal reply. Check the account name, the recognition period and the receipt reference against your own papers. A quoted price doesn’t mean the matter is finished. And a receipt for some other item is not proof that recognition was renewed.
• A restriction reply. Keep the stated reason and the route for answering it. Ask what information that route needs. Telling you to change your password doesn’t answer a notice about authorisation.

If the reply doesn’t name an action, ask one focused follow-up: which of my questions does this answer, and what is the next authorised step for it? Don’t ask support to approve an explanation you made up yourself. Keep your original note and the reply together, so anyone reading later can tell what you saw and what was confirmed afterwards.

What should you ask before paying for a fix?

Ask the provider to name the item being charged and the condition it covers. A password-recovery request, an annual renewal and a review of a restriction are all different. The payment description should make clear which one you’re paying for.

Be wary of an offer that calls a payment only “unlocking” without explaining your account status and the authority behind the action. Ask whether the action is available for your ID and what happens if it can’t be done. A fair answer explains what the service covers. It doesn’t rest on a promise that you’ll be back in before a particular booking window.

After you follow the instruction

Write down what you see next. Was sign-in accepted? Did you reach the authentication step? Is the same notice still there? Make this check before you take money for a booking that depends on access.

If you’re back in but the receipt question is still open, leave that question open. If validity is explained but sign-in still fails, report what fails now, instead of telling the whole story again. Close the enquiry only when every question you asked has an answer you can point to. Otherwise, note what’s outstanding and who is responsible for it.

The short version, in order

When you’re stressed, it’s easy to skip steps. Here is the order again.

1. Confirm you’re on the right login route for your ID, OTP or DSC.
2. Write down the exact error, word for word.
3. Check validity and compare your renewal receipt with what the provider has.
4. Check you still control the registered phone.
5. Contact support with your agent ID and the details above, and share no secrets.

Common questions

Can SiOnline reset the IRCTC password?

Contact support with your agent ID; never send a password or OTP. Ask support to identify the official recovery route that applies to your account.

Should I register another agent ID immediately?

No. Ask what has happened to the existing account first. A new registration is a separate commercial decision, and it isn’t proof that recovery is impossible. Get a written explanation of the existing ID’s status and any action that’s available.

What if a caller already knows my agent ID?

An agent ID alone is no reason to hand over a password or login OTP. End the call and use your established support route to check the issue. If you think someone else used your credentials, keep the message and any transaction reference, and ask the support channel how to report it.

What should I tell a customer waiting at the counter?

Tell them the agent account needs an access check before you can take the booking. Don’t predict when it will be restored, and don’t take payment on the hope that the next attempt will work. You can ask whether they’d like to come back once access is confirmed.

Sources

• IRCTC: Agent Interface, retrieved 18 October 2026.
• IRCTC: Internet Cafe Scheme norms, retrieved 18 October 2026.

Confirm the applicable rule and account status before acting.