Why the Start Interview Now Button Is Not Showing

When the Start interview now button is not showing on a HireQwik booking page, the system is almost always behaving correctly. The instant card, explained in full in how instant AI interviews work, is designed to disappear whenever it cannot honestly promise a candidate a call in the next minute. That is a good property, but it is confusing if you have just ticked the setting and a candidate messages you, “I only see a calendar.”

Picture the message arriving on a Tuesday afternoon: “Sir, the email said I could start immediately, but there is no button.” Before you reply, it helps to know that there are exactly six reasons the card hides, and five of them are the system protecting either the candidate or the box. This post goes through each one, what the candidate sees, and how to check it in about five minutes.

So you know what you are looking for: when the option is live, the top of the candidate’s booking page shows a lightning-bolt card headed “Ready now? Start your interview immediately,” with a Start interview now button. The calendar sits underneath, labelled “Or pick a time that works for you.”

When the card is hidden, the page shows only the calendar, labelled “Pick a time that works for you.” Nothing looks broken. That is deliberate, and it is also why candidates and recruiters sometimes assume the feature is off.

Reason 1: the job has not opted in

What is happening. Instant interviews are off by default and switched on one job at a time. HR ticks “⚡ Instant interviews” on the job’s Connect Sheet card and saves. Without that, no candidate on that job sees the card. Because the choice lives on each job, one role can offer instant starts while the next one stays on booked slots.

Where it goes wrong. The setting was ticked but not saved. Or it was saved on a different job with a similar name. Two jobs parsed from the same description used to look identical in lists, which is why HireQwik now lets you give each job its own label and adds a suffix such as location or upload date when titles collide. Check the label, not just the role title.

How to check. Open the job the candidate’s link came from, open the Connect Sheet card, and confirm the box is ticked after a page refresh.

Reason 2: the candidate already booked a slot

What is happening. Instant is for a candidate’s first booking only. Once a candidate has booked any slot, the card is gone for them. If they come back to the page to reschedule, they see the calendar, not the card.

Why it works that way. A booked candidate already holds a join link. Letting them also start instantly would create two claims on seats for one person. If a booked candidate somehow sends an instant request anyway, the server replies that instant start is only available before a slot is booked and points them to their existing join link or the reschedule option.

How to check. Look at the candidate’s row in /inbox. If they are under Scheduled, they have a booking. They can join at that time, or reschedule within the limit of 3 attempts in 72 hours explained in the reschedule limit article.

Reason 3: the current window is full

What is happening. The card only appears when the current booking window has a free seat, using the same weighted seat count the calendar uses. A call that runs past its slot still counts against the next window, at half a seat by default, so a busy stretch can fill a window before its nominal seats are gone.

What the candidate sees. The calendar only. The same windows that are full on the calendar also block the instant card.

How to check. Look at the calendar yourself on a test link. If the current window shows as full, this is the reason. It will clear as calls finish. The full-slot article explains the seat math.

Reason 4: live interviews are at the ceiling

What is happening. Apart from window seats, the card asks a second question: how many calls are in progress this second? The hard limit is 25 simultaneous interviews, and it is a common pool, not a per-job allowance. When in-progress calls already equal that limit, no card.

Why a second check at all. Window seats are a booking ledger. The door, meanwhile, admits only against calls that are really running. A few long calls from an earlier window can leave the ledger showing room while the door is shut. Checking both is what stops the card from inviting a candidate who would then be bounced. One subtle detail: reaching exactly 25 counts as full, since the new call has not joined the tally yet.

The surprise for HR. A different job’s campus drive can hide the card on your job. If another team is running a heavy campaign at the same hour, your candidates may see only the calendar. For planning around that, see our concurrency explainer.

Reason 5: the page was stale when they clicked

What is happening. The candidate loaded the page while the card was visible, waited a minute, and clicked after seats filled or the job’s setting changed. The server re-checks everything on the click. The button’s request alone grants nothing. Technically the refusal is an HTTP 409, the Conflict status defined in RFC 9110, meaning the request clashed with the current state of the system, which is exactly what happened.

What the candidate sees. One of two brief notes, saying either that every interviewer is currently occupied or that this role does not offer instant starts, plus a prompt to choose a slot. A refresh follows, and if things changed, only the picker remains.

What to tell them. Pick a time, or try again in a few minutes if they really want to start now. Nothing is wrong with their link.

Reason 6: the system could not check

What is happening. If anything goes wrong reading the job’s setting or counting seats, the instant option turns off for that page load and the candidate sees the normal calendar.

The reasoning. The harmful mistake would be launching an interview for a role whose owner never switched instant on, or promising a start with no capacity behind it. Asking a candidate to pick a time is the safe fallback. So the feature fails closed, and a hiccup looks exactly like reasons 3 or 4.

How to check. Try the page again a few minutes later. If it stays hidden on a quiet hour for a fresh test candidate on an opted-in job, report it with the time you tested.

Which reason is it? A symptom-to-cause table

How do you test the card before a campaign?

Do this once whenever you switch the option on for a job, ideally the day before invites go out:

1. Refresh the job’s Connect Sheet card and confirm Instant interviews is ticked.
2. Put yourself in the job’s sheet as a dummy candidate, then approve that row in /inbox (or let auto-invite mail it) so a real self-schedule link arrives.
3. Open the link on your phone, on mobile data, at an hour when no other campaign is running.
4. Confirm the card is there, then click Start now and join the call for a minute. Allow the browser’s microphone prompt when it appears, the same step every candidate will face.
5. Reopen the same link. The card should be gone, because you now hold a booking.

That last step catches a lot of confusion later, because it shows you exactly what a returning candidate sees. Per-candidate status stays visible from your HR dashboard.

What should you tell the candidate?

The candidate does not need to hear about seat math or opt-in flags. They need one clear next step. These replies cover every reason above, and each can be sent in under a minute.

When the job was never switched on, which is reason 1: “Sorry for the confusion, this role uses booked times. Please pick any slot on the page that suits you.” Then fix the setting, or fix whatever message promised an instant start in the first place. A recruiter template that says “you can start immediately” for a slots-only job creates this ticket every time.

When they already hold a booking, reason 2: “You are already booked for the time you chose earlier. Join then from the link your booking email carries. If that time no longer works, the same page lets you move it.” This reply prevents the candidate from hunting for a second link that does not exist.

When capacity is the cause, reasons 3 and 4: “Our interviewers are fully occupied right now. Please choose a time later today, or reopen the link in about half an hour and the start option may be back.” Do not promise it will reappear. It depends on calls finishing.

When they hit a message after clicking, reason 5: “That message means the interviewers filled up between your page loading and your tap. Nothing is wrong with your invite. Just pick a time.”

When you cannot find a reason, reason 6: “Thanks for flagging this. Please book any slot for now so you are not held up, and we will look into why the start option was missing.” Then run the five-minute test above yourself, at the time the candidate tried.

Keep the tone the same in every case. The candidate has done nothing wrong, and a calm reply that points to the calendar costs them a few minutes rather than a lost opportunity.

It also pays to keep a simple log of these messages for the first few weeks after switching the option on: the time, the job, and which of the six reasons turned out to be behind it. Patterns show up fast. A cluster of reason 1 tickets usually means a template or a WhatsApp forward is promising instant starts on jobs that do not offer them.

Reason 3 and 4 tickets bunched at the same hour point to a collision with another campaign, which calls for a scheduling conversation with the other team rather than a bug report. A genuine reason 6 that keeps repeating is worth reporting straight away, with the times attached, because a failed check that recurs is exactly what we want to hear about.

Key takeaways

• A hidden Start now card is usually correct behaviour, not a fault.
• The six causes are: the job never opted in, the candidate already booked, the window is full, live calls sit at the 25 ceiling, the page went stale, or a check failed.
• A busy or not-enabled message after clicking means the server re-checked and refused; the invite link itself is fine.
• Test with a dummy candidate on your phone the day before invites go out.
• Give every candidate one clear next step, which is usually picking a slot.

Why trust a card that hides?

The booking page broke once during development, before anyone outside the team saw it. A new helper function was inserted in the wrong place in the code, and the booking page was silently routed to it. The test suite caught it the same day.

There are 14 tests covering the instant path alone, including ones for a job that has not opted in, a full window, live calls at exactly the ceiling, and a failed seat count. I mention it because every reason in this post has a test behind it, and that is why I am confident the card hiding is usually correct.

Still unsure a job should offer instant starts? The five questions in instant or scheduled, role by role settle it quickly. Reasons 3 and 4 appear most on big placement days, so read the campus drive plan before one. When the real trouble is people who never book or never join, the five attendance leaks is the better starting point. For problems after the candidate is in the call, the AI interview link troubleshooting guide picks up from here.

My view: a card that sometimes hides is better than a button that sometimes lies. If you have checked all six reasons and the card still will not appear, tell us the job and the time, and we will look at it with you.