If you booked a VFS appointment two years ago and are doing it again now, the flow is not the same. Two changes matter, and the second one quietly rewrites what a booking service can and cannot be.
What changed
A one-time code at confirmation. At the point an appointment is confirmed, the system sends a code to the applicant. Someone has to enter it within a few minutes or the booking does not complete.
The appointment bound to an application reference. The slot is tied to a specific application rather than held as a generic place that can be filled in later.
Both were aimed at the same thing: people taking appointments in bulk and reselling them. An appointment that cannot be held generically, and cannot be confirmed without the applicant’s code, is much harder to treat as stock.
What it means if you are applying yourself
Mostly good news, with one thing to plan for.
Be reachable at the end. The code has a short life. If it arrives while your phone is off, the booking fails and the appointment goes back into the pool.
Have the application reference ready. Because the appointment binds to it, the booking flow expects it. Fumbling for it inside a minutes-long window is a common way to lose a batch.
Fewer captured appointments in circulation. The tightening cuts against whoever was hoovering up releases to sell. That is a straightforward improvement in your odds, even if it does not feel like one from an empty calendar.
What it means if someone is helping you
This is the part worth being precise about, because it changes what a legitimate arrangement looks like.
Your password stopped being necessary. It was never a good idea, and now there is a concrete reason it is unnecessary: the confirmation step requires you, not your credentials. Anyone still insisting on the password is asking for something the work does not require — the longer version is here.
A service that holds appointments for resale has a much worse business. Which is the point. If someone offers you a specific date and time before you have engaged them, ask how they are holding it in a system designed to prevent exactly that.
Watching and booking still work fine. Monitoring a calendar and completing a booking in your name, with you present for the code, is unaffected by either change. That is the arrangement the changes leave intact — arguably deliberately.
What did not change
- Availability. None of this creates appointments. The consulate still sets how many exist, and on a pressured route the calendar is empty most of the time.
- Processing times. Unchanged, and still starting from the appointment.
- The rate limits. Refreshing the booking page in a loop still gets you restricted, and still ends with you unable to see the batch you were waiting for.
- Where you may apply. The residency rule is untouched, and remains the thing that quietly decides whether an application succeeds after the booking does.
What makes it worse
- Sharing the code with anyone. It exists specifically so that you are the one who confirms. Handing it over gives away the only part of the process that is unambiguously yours.
- Being unreachable when it lands. The one new failure mode. If you are working with someone who watches for you, agree how they reach you and keep that channel open.
- Assuming an old guide still applies. Instructions written before 2026 describe a flow that no longer exists, and the confident ones are the most misleading.
- Buying a “held” appointment. Harder than it was, which means anyone still claiming to do it is either misdescribing an ordinary booking or selling captured stock.
How we work with it
We watch, we book in your name through the official system, and you read out the code. A few seconds of your involvement at the end, and nobody has to hold your password to make it work.
We think the changes made the honest version of this service easier to explain, not harder to run.