Where AI Interview No-Shows Really Come From

The first step to reduce AI interview no-shows is admitting you probably do not know which kind you have. For a long time we did not either. Until late July 2026, a self-scheduled HireQwik interview link stayed joinable for 8 hours, so a candidate who booked 9:00 could join at 16:50. We could not say cleanly who had missed their slot, because almost nobody technically had.

When we tied the join window to the booked slot on July 23 (it now shuts ten minutes past the end of the slot), “no-show” became a real, countable event for the first time.

Once you can count it, you notice it is not one problem. It is at least five different ones, sitting at different points between “shortlisted” and “screened.” Ghosting is a wider hiring trend, as our look at candidate ghosting data shows, but inside a screening campaign it breaks down into specific, fixable steps. Each needs a different fix. This post maps all five, names the control that fits each one, and tells you what to look at before you change anything.

Why “send more reminders” is usually the wrong first move

When a campaign’s attendance looks poor, the reflex is to add reminders. Reminders only help one group: candidates who booked a slot and then forgot it. They do nothing for candidates who never saw the invite, who never booked, or who tried to join and were turned away.

Public benchmarks back this up, loosely. Cronofy’s candidate expectations survey found that 62% of candidates would prefer an automated system to lengthy back-and-forth when arranging an interview. That points at the booking step, not the reminder step. Talview’s analysis of scheduling gaps and attendance recommends a 12 to 24 hour window for high-volume roles like early career and customer support, again a point about timing rather than nudging.

So diagnose first. Here are the five leaks in the order a candidate meets them.

Leak 1: the invite was never really seen

What it looks like. Invites were sent, but a large share of candidates never open the booking page at all. They did not decline. They simply never engaged.

Why it happens. Your automated email was the very first thing this person ever received from you. It landed in a promotions tab, or the candidate did not recognise the sender and ignored it. Freshers applying through a college cell are especially likely to miss it.

What fixes it. Two things. First, a short human notice from an address the candidate already knows, saying a screening link is on its way.

Second, a channel candidates actually read. HireQwik can mirror the invite on WhatsApp for jobs where HR switches it on, while email stays the primary channel, as covered in WhatsApp interview invites and reminders. What goes into the email itself is in the AI interview invitation email.

What does not fix it. Instant interviews. A candidate who never opens the page never sees the Start now card.

Leak 2: seen, but never booked

What it looks like. Candidates open the booking page, sometimes more than once, and leave without picking a slot.

Why it happens. Choosing a time is a small decision, and small decisions get postponed. The candidate means to come back after checking their week. Then another company’s invite arrives, or the tab gets closed, and they never return.

What fixes it. This is the leak instant interviews were built for. When a job has the option switched on and a seat is free, the page offers “Start interview now” above the calendar. A candidate who is ready does not have to make a scheduling decision at all. They click once and are in the interview within about a minute. The conditions behind that card are laid out in our guide to the Start now card.

It also helps to send the invite promptly. If invites wait for a recruiter to click Send, the candidate cools before the link even arrives. The runbook on auto invite after resume score covers mailing cleared candidates overnight.

Honest caveat. No production job has run instant starts yet, so any percentage I gave you would be made up. It removes the decision that causes this leak. How much of the leak it closes is something each campaign will show.

Leak 3: booked, then forgotten

What it looks like. Candidates booked a slot, often a day or two out, and the window passed with no join.

Why it happens. The longer the gap between booking and call, the more room life has to push the interview out of mind. This is the classic no-show.

What fixes it. Reminders, placed well. Every HireQwik booking confirmation includes a calendar attachment that common mail apps open natively, and it carries an alarm a quarter hour ahead of the call. If the candidate accepts it, their own phone does the reminding. On jobs with WhatsApp switched on, the reminder goes there too. And for candidates who would rather not carry a booking at all, instant removes the gap entirely.

What does not fix it. Shorter slot lists. Forcing everyone into tomorrow morning does not make them remember. It makes them book a time that does not suit them, which feeds leak 4.

Leak 4: booked, then a conflict came up

What it looks like. A candidate genuinely wanted the interview, but their exam moved or another company scheduled them at the same time. They did not show because they could not.

Why it happens. Placement season and active job searches are crowded. Conflicts are normal, not a sign of low interest.

What fixes it. A reschedule path that is easy but bounded. HireQwik allows three reschedules inside a 72-hour window from the original booking. Past that, the picker refuses further changes until HR resets it manually. The reasoning behind that limit is in the reschedule limit explained. Make sure your invite tells candidates that rescheduling exists. Many assume a missed slot is the end.

One detail worth knowing. Instant is offered only for a candidate’s first booking. A candidate who booked and then reschedules will see the calendar, not the Start now card. That is deliberate: they already hold a join link, and the system keeps that booking stable.

Leak 5: tried to join, and could not

What it looks like. The candidate did show up, in their own mind, but never reached the interviewer. From HR’s side it looks exactly like a no-show.

Why it happens. A few specific reasons, each with its own message:

• They came outside their window. Joining opens five minutes before the slot and closes ten minutes after it ends. Arriving an hour late is too late.
• The box was full at that moment. At most 25 calls run at once. Anyone arriving while that limit is reached is told the interviewers are busy instead of landing in a broken call.
• Their link was cancelled. If HR stopped the campaign, unstarted interview links were revoked and return a recruiter-cancelled message.
• A browser or microphone problem. The call needs Chrome, Edge or Safari with a working mic.

What fixes it. Treat these as support tickets, not attendance problems. The troubleshooting guide for AI interview links walks each message to its cause. For the busy case specifically, the instant card only appears when in-progress calls leave room, and it re-checks when pressed.

How do you find which leak you have?

Here is the sequence I would run on a campaign with poor attendance:

1. Count invites sent against booking pages opened. A big gap is leak 1.
2. Count pages opened against slots booked. A big gap is leak 2.
3. Count slots booked against windows joined. A big gap is leak 3, 4 or 5.
4. Read candidate replies. “I had an exam” is leak 4. “It said busy” or “the link did not work” is leak 5. Silence is usually leak 3.
5. Change one thing, on one job. Switch on instant for leak 2, or WhatsApp for leak 1, and compare against a similar job that stayed the same.

Each candidate’s live status is visible from the HR dashboard.

One warning if you compare periods. Attendance figures from before 23 July 2026 are not comparable with figures from after it. Under the old eight-hour window, a candidate who arrived six hours late still got in, so older campaigns will look healthier than they really were. Now that the join window is tied to the slot, that same late arrival can no longer join and shows up as a miss.

A team that lines up June against August and concludes attendance fell has mostly measured the rule change. Compare campaigns that both ran under the current window, ideally the same role at a similar time of year, and change only one thing between them.

The same caution applies inside a single week: a campaign that overlapped with a heavy drive on another job may show more busy messages at the door, which is a capacity story rather than a candidate one.

What to send candidates at each leak

Settings fix part of each leak. Words fix the rest. These are the short messages I would have ready, one per leak, written for a recruiter to send from their own address rather than from the system.

Before the invite, for leak 1: “Hi, this is the talent team at our company. You have been shortlisted for the support role. In the next hour you will get an email from HireQwik with a link to a short AI voice interview. It is genuine, it takes about fifteen minutes, and you can do it from your phone.” Four sentences, sent first, and the system email stops looking like spam.

For leak 2, a day after the invite if the page was opened but nothing was booked: “Your interview link is still open. If you are somewhere quiet, you may be able to start straight away from the same page. Otherwise, pick any time that suits you this week.” This nudge only mentions starting right away if the job has instant switched on. Otherwise drop that sentence.

For leak 3, on the morning of a booked slot: “A reminder that your AI interview is today at the time you chose. Open the join link we emailed you, and join from Chrome, Edge or Safari with your microphone allowed.” Short, practical, and it repeats the browser detail that causes so many leak 5 failures.

For leak 4, whenever a candidate replies that they have a clash: “No problem. Open the same link and use the reschedule option to choose a new time. You can move it a few times, so pick a slot you are sure about.” Candidates who know rescheduling exists use it instead of disappearing.

For leak 5, after a failed join: “Sorry the call did not connect. Tell us roughly when you tried and what the page said, and we will sort it out.” Then check the message against the link troubleshooting guide before you promise anything. If the call broke for a technical reason, HR can reset the booking and send them back in.

None of these messages is clever. Their value is that each one answers the exact doubt behind a specific leak, instead of one generic “please complete your interview” email sent to everyone.

Where do instant interviews fit among the fixes?

Of the five leaks, instant interviews directly target one, help a second, and do nothing for the other three. I think that is the right way to describe any single feature. It is a strong tool for the candidate who is ready now, and a poor one for the candidate who never saw your email.

Whether a given role deserves it is a judgement call, worked through in comparing instant and booked interviews. For campus drives, where leaks 1 and 2 are most severe, see instant interviews on a placement day. And if you switched it on and candidates report no button, the hidden-card checklist explains why that happens.

Key takeaways

• No-shows are five separate leaks: unseen invites, pages opened but never booked, forgotten slots, new conflicts, and failed joins.
• Count each funnel step on one campaign before changing anything.
• Extra reminders mainly help people who booked and forgot; they cannot rescue an invite nobody opened.
• Instant interviews directly target one leak and help with a second; the other three need different fixes.
• Only compare attendance across campaigns run after the 23 July 2026 join-window change.

Where to start this week

No-shows are a funnel, not a number. Find the widest gap, fix that one, and measure again. Adding reminders to a campaign whose real problem is an unread invite is how teams spend a month convinced their candidates do not care.

If you want help reading your own campaign’s funnel, talk to us. We will go leak by leak with you.