Tatkal Software: Why Agents Must Avoid Bots

It’s a familiar scene. A man walks in, or sends a WhatsApp message, with a “Tatkal tool” that promises to fill the form in a second and grab a seat while everyone else is still typing. It comes with screenshots, a few happy messages and a low price. Your customers are asking why their Tatkal bookings fail, and you’d like to say yes to something.

Before you pay or install anything, read this. The short version is that IRCTC’s own policy rules out the things these tools usually do. The same policy also bans sharing an agent ID and selling customer tickets from a personal account. So the safe path is to use the authorised booking route and prepare your customer’s request by hand, without trying to get around the system.

How do you judge a tool?

Don’t go by what the seller calls it. Go by what it does.

As checked on 18 October 2026, IRCTC’s agent policy names four things: software tampering, Tatkal robot facilities, saved booking forms on a server or local computer, and opening Tatkal forms before the permitted time or during the restricted period (Agent Policy B.14). A “robot” here just means a program that does the booking steps for you instead of a person doing them. A “saved booking form” means a completed form kept ready, so it can be pushed out the instant booking opens.

Use this table as a quick filter.

The last row is the only one with a green light, and even there the words “assess any extra feature separately” matter.

What if the vendor says it only fills in details?

Then ask two questions. Where is the information stored? And what exactly does the software do on your computer? If you can’t tell its action apart from a prohibited robot or saved form, stop. Ask your PSP (Principal Service Provider, the company that registered you) to assess it. Ask the vendor for documentation and the written basis for any access they want.

And don’t test a doubtful tool on a live customer request. If it breaks a rule, you’ve used a real customer’s booking to find out.

Say a vendor shows you a package with two features: a handy notebook that stores your customers’ travel preferences, and a “quick launch” that opens a saved form the moment Tatkal starts. The notebook might be fine. The quick launch is the kind of thing the policy names. Bundling them doesn’t make the second one acceptable. The refusal still stands for the part that’s not allowed.

Keep a note of the offer, with its date and version. If the vendor changes the product later, it needs a new assessment. The old one doesn’t carry over.

What preparation is allowed instead?

Plenty. Most Tatkal trouble at a counter comes from unclear instructions, not from slow typing. Fix that first.

Before booking starts, ask the customer to settle:

• the date and the route
• the class they want
• what they’ll accept if their first choice isn’t available

Write down the decision the customer actually made. “Ask before changing class” is far more useful than a blank space that two different staff members would fill in two different ways. Then read the request back and check the passenger’s mobile number with the customer.

IRCTC’s booking mandates ask for a few things. The customer must know about and accept the booking. There must be a written or electronic request, with an ID-proof copy kept for six months. The passenger mobile has to be correct. And you need an itemised invoice and the prescribed Electronic Reservation Slip (ERS). Use those records to cut corrections down, not to pre-open or inject booking forms.

A paper or notebook sheet is enough. Call it a shop preparation record, not an official form. Leave out passwords and OTPs, and keep the sheet out of photographs.

Does the agent opening restriction still apply?

Yes. As of 18 October 2026, PIB’s Tatkal announcement (release 2135694, 11 June 2025) states that authorised agents cannot book opening-day Tatkal during the first 30 minutes. AC bookings open for agents at 10:30 AM and non-AC at 11:30 AM.

The announcement gives fair access for genuine passengers, stronger authentication and reduced misuse as its purpose. The software bans come from the separate agent policy, not from this announcement. Our agent Tatkal timing guide goes through the timings if you take a time-sensitive request.

There’s one more rule worth knowing. For Tatkal through an authorised agent, the announcement requires an OTP sent to the mobile number the user gives at booking. That passenger booking OTP is different from your own agent login OTP. Don’t mix them up when you explain it to a customer.

How should you set expectations?

Tell the customer before you take the request, not after the window has already opened. Say that agents can’t book in the first 30 minutes, and ask whether they still want an attempt through the agent route. Keep that choice separate from their willingness to pay the fare and your charges.

If availability changes while you’re booking, ask the customer before you switch to another train or class. Don’t decide on their behalf that speed matters more than the journey they agreed to. A counter that says “I can’t use that workaround” gives a customer a clearer answer than one that takes money on a vendor’s promise.

What if a tool is already installed, or you’ve entered your login?

Stop using it for customer bookings now. Then do these things in order:

1. Keep the tool’s name, the invoice, and any messages where it said what it would do.
2. Note which account was involved, without repeating the password or OTP anywhere.
3. Ask your PSP to review the access you gave it. Contact the PSP through a route you’ve checked yourself, not a number the vendor gave you.
4. If a password change is needed, make it yourself through the official account process.

Don’t let the vendor “investigate” by asking for more OTPs or remote control of your computer. That’s the opposite of fixing the problem.

IRCTC’s policy lists software tampering and unauthorised access among penalised irregularities, and it provides for deactivation in specified cases. It doesn’t create a right to get an ID back after the software is removed. Removing an add-on also won’t explain an unexpected booking or cancellation. So check any customer transaction against the original records and ask for confirmation of the account’s status.

For sign-in routing, use the agent login guide. For an account-specific concern, go to SiOnline support. To check who a provider is, read the Principal Service Provider list guide.

How do you explain the refusal to staff and customers?

To your staff

Teach actions, not product names. A list of banned apps goes out of date in a month. A list of banned actions doesn’t:

• sharing agent access
• selling tickets commercially from a personal account
• sending forms through a service nobody has checked
• trying to get around a restriction

If a staff member gets a new software link, they should bring it to the account holder before they install it. Don’t set a speed target either. A target like “book it faster” invites the exact workaround you want them to question.

To your customers

Tell the customer you can attempt the booking through your authorised account under the applicable rules, and explain the timing restriction. If they ask you to install a tool, say the counter has to find out first whether that action is allowed. Then offer them real choices: an authorised attempt, another train checked, or time to pick a different route.

Record any change in their instructions. And if the customer decides not to go ahead, close the request clearly so another staff member doesn’t submit it later.

A short checklist before you say yes to any tool

Run through these before you pay, install or enter a single login:

• Can the seller tell you in plain words what the tool does on your computer, and where it keeps customer information?
• Does it open, fill, save or submit a booking form for you? If yes, compare it with the four things in IRCTC’s agent policy named above.
• Does it ask for your agent ID, password or an OTP? If yes, the answer is no.
• Does it promise special seats, earlier access or a way round authentication? Then reject the claim.
• Is there a written basis for the access it needs, which your PSP has seen?
• Have you written down the offer, its date and its version, so a changed product gets a fresh look?

If any answer worries you, stop and ask your PSP before the customer is waiting.

Questions agents ask

Can I use software that only saves my customer’s details?

Only if it stores preferences and has no connection to the booking site. A saved completed booking form is named in the agent policy, so refuse that.

A vendor says IRCTC approved their tool. Is that enough?

No. A vendor’s claim of approval doesn’t replace IRCTC’s permission. Ask for the written basis and show it to your PSP before you use anything.

Is the Tatkal booking OTP the same as my agent login OTP?

No. For Tatkal through an authorised agent, the PIB announcement requires an OTP sent to the mobile number the user gives at booking. Your agent account-login OTP is a different thing.

What if I need a faster workflow at the counter?

Speed can come from preparation: the date, route, class and alternatives settled before the window opens. The speed doesn’t come from a tool that does what the policy names.

Facts checked on 18 October 2026, from IRCTC’s Agent Policy and the PIB announcement of 11 June 2025. Confirm the applicable rule and account status before acting.

Sources

Official pages linked in this article:

• IRCTC’s agent policy
• PIB’s Tatkal announcement

Fees, dates and rules change. Confirm them at the source before you act.