Inside the HireQwik AI Interview Invitation Email

On 26 August 2026 we switched on WhatsApp messages for HireQwik candidates. The templates that went live that day told people to reply STOP to opt out, and the code that actually honoured STOP shipped the next day. For one day, a message promised something the system could not yet do.

We closed that gap quickly, but it taught us to read every candidate-facing message as a promise. The HireQwik AI interview invitation email is the biggest of those promises, because it is usually the first time a candidate hears about the interview at all. Recruiters think of the invite as step three in a process the candidate already understands. The candidate experiences it as an unexpected email asking them to talk to an AI. This post walks through what the system sends, in order, and the short note HR should add around it. If you have not seen the flow from the recruiter’s side, start with how a sheet row becomes a screening campaign.

Key takeaways

• The invite email carries a self-schedule link; the booking confirmation adds a calendar file with a reminder 15 minutes before.
• Re-sending a confirmation updates the existing calendar event instead of creating a duplicate.
• WhatsApp is switched on per role, sits alongside email, and uses fixed Meta-approved wording.
• None of the system messages say why the candidate was shortlisted or what the AI will ask. Your pre-notice has to.
• Stopping a campaign cancels interviews that have not started, so follow it with a human message.

What does a HireQwik interview invite contain?

The HireQwik AI interview invitation email contains a self-schedule link that lets the candidate pick their own interview slot. After they book, a confirmation email follows with a calendar file and a reminder. Roles with WhatsApp switched on also send a WhatsApp invite, reminder and confirmation alongside the emails.

Each of these has one job. The invite gets a slot booked. The confirmation gets that slot into a calendar. The WhatsApp messages make sure a candidate who does not live in their email inbox still sees both. None of them is meant to explain what an AI interview is or why your company uses one. Keeping that division clear is what stops teams from trying to cram a whole briefing into a system message it was never built to carry.

HireQwik invite email and booking confirmation

The invite email, sent without HR

In the trigger flow, each job description has a Google Sheet linked to it. When a new candidate row appears, HireQwik enriches it, scores the resume against that role, and emails the candidate a self-schedule link. No one on the team needs to press send for each person.

That automation is the point: in a large drive, hand-sending invites is exactly the kind of work that stalls a pipeline for days. But it has a side effect worth being honest about. Because the email is triggered by a sheet row, it can reach a candidate before anyone from your company has spoken to them. If a placement cell forwarded a spreadsheet on Monday and invites land on Monday evening, the candidate may not yet know they were shortlisted.

The fix is timing on your side, not a change to the email. Send your own short notice first, then let the sheet trigger.

The confirmation and its calendar file

After the candidate picks a time, a confirmation email follows. The useful part is the attachment: a calendar file in the RFC 5545 format, the internet standard for calendar data that Gmail, Outlook and most phone calendars read. It supports the normal accept and decline buttons, and it adds a reminder 15 minutes before the interview.

This sounds like a small detail. It changes behaviour. A link sitting in an email gets forgotten. An event sitting in a calendar pings the candidate a quarter of an hour before they need to find a quiet room. We covered why this design choice affects attendance in our breakdown of self-scheduling design, so here the practical takeaway is simple: tell candidates to accept the calendar invite, not just read the email.

Why a re-sent confirmation does not duplicate

One more property of that calendar file saves a lot of confusion. Each file carries a stable identifier tied to the interview’s join URL. If a confirmation is sent again for the same interview, the candidate’s calendar recognises the event and updates it rather than adding a second one. Anyone who has received three copies of the same meeting after a sender edited it knows why this matters: a candidate with two calendar entries for one interview does not know which time is real. For recruiters, it means re-sending a confirmation to a candidate who says they lost it is safe.

HireQwik WhatsApp invites, one role at a time

For many candidates in India, especially freshers and people applying from their phone, WhatsApp gets checked far more often than email. HireQwik can send the invite, a reminder and the booking confirmation over the WhatsApp Business API, alongside email.

Three design choices to know

Three design choices are worth knowing before you promise candidates anything about it.

It is per role. HR turns WhatsApp on for one job at a time in that role’s trigger settings. Other roles stay email-only.

Email remains the main channel. WhatsApp is added on top and built to fail safely, so a WhatsApp outage cannot stop an email, a booking or a reminder from going out.

The wording is fixed. Meta requires pre-approved templates for messages a business starts, so each message swaps in just four details: who the candidate is, which job, which employer, and either a link or a booked time. You cannot add a paragraph about your hiring process into a WhatsApp template.

STOP and opt-out

Candidates can also reply STOP to opt out, and since 27 August that request is honoured before any later message is sent. The full detail is in our posts on WhatsApp invites and reminders and how opt-out works.

What HireQwik invite messages cannot tell candidates

Line the messages up and a clear gap appears. Between them, they tell a candidate when to show up and where to click. They do not tell a candidate:

• that they were shortlisted, or by whom;
• that the interviewer is an AI and what the conversation will cover;
• that the role opens with eligibility questions that can end the call early;
• what device and browser setup they need;
• when they will hear back afterwards.

Each of those becomes a question your recruiters will otherwise answer by email, one candidate at a time. None of them fits in a fixed WhatsApp template, and a scheduling email is the wrong place for a process explanation anyway. Your team needs to supply it, in your company’s voice, before the system messages arrive. The content of that briefing is laid out in how to prepare candidates, and the early-ending point gets its own treatment in the knockout early-exit post.

HireQwik pre-notice template to send before the invite

The pre-notice template

The note we suggest is short, sent through whatever channel the candidate already trusts: the placement cell’s group, your careers page status update, or a direct email from a named recruiter. Its job is to make the HireQwik invite feel expected.

Hi [name], good news: [company] has shortlisted you for [role]. Within the next day you will receive an email to book a short interview slot. You will talk with an AI interviewer about this role, from your phone or laptop. Once you book, please accept the calendar invite so you get a reminder. If you do not see the email, check your spam folder or reply to this message. We will update you on next steps by [date].

Notice what it does not repeat: the link, the slot times or the join details. Those belong in the system messages, where they stay correct if a booking changes. Your note provides context; the system provides logistics. Duplicating logistics in two places is how candidates end up with an old time in one message and a new one in another.

Add a line about the sender

Add one more line about the sender. Invites go out from HireQwik’s interview mailbox, not from your company domain. For a candidate who was told “Acme will be in touch”, an email from a different domain looks suspicious, and some mail providers file it under promotions or spam. “The booking email comes from our interview partner, HireQwik” removes the doubt in one sentence.

Bulk HireQwik invites: big uploads and stopped campaigns

When a large sheet upload sends invites at once

Invites follow sheet rows, so the way you upload decides the way invites go out. Add candidates a few at a time and invites trickle out through the day. Paste a full campus list in one go and every eligible row can be invited the same evening, which puts a large group of candidates on the booking page within hours of each other.

The booking page is built for that rush. Each slot displays the seats genuinely left, for example 17 of 25 in a 9:00-9:15 slot, and closes once it fills. If a slot fills while a candidate is still deciding, they are asked to choose another instead of being double-booked. That protects the interview itself, but it can frustrate candidates who all go for the first morning slot. Two habits help. Spread large uploads across a day or two when the timeline allows it, and mention in your pre-notice that slots run throughout the day, so candidates do not all race for the earliest one. The seat counting behind this is explained in our post on full interview slots.

What stopping a campaign does to delivered invites

Sometimes an invite wave goes out with a mistake in it: the wrong job description attached, or the wrong candidates on the sheet. The best defence comes before launch, when HireQwik puts a confirmation step in front of you that lists which job, how many people, when their slots run and what it will use in credits. Read it properly. It is the last cheap moment to notice a wrong sheet.

If the mistake slips through, recruiters can stop the campaign from the dashboard, and stopping reaches back into messages already delivered. Any interview that has not started yet gets cancelled, and a candidate who clicks its link sees that the recruiter called it off. Calls already running, and calls already done, are not touched. Credits for interviews that never started go back to the original payer automatically.

After a stop, send candidates a short human message too. The system kills the link, but it cannot explain why, and a cancelled interview with no explanation reads like a rejection. The full mechanics sit in what to do after invites have gone out.

What if a candidate says the HireQwik invite never arrived?

First ask the candidate to search their mail, including spam and promotions, for HireQwik, since invites come from HireQwik’s interview mailbox rather than your domain. Then check the candidate’s own record: for WhatsApp, each invite, reminder and confirmation attempt is recorded against that individual candidate, so you can see what went out.

That check matters because the useful question is not “did we send it” but “what happened to this particular message”. A per-candidate record answers that directly, instead of guessing from campaign totals.

Resending versus resetting a booking

Recruiters also tend to reach for “resend” whenever a candidate is stuck. It fits one situation and not the others. Re-sending a booking confirmation to a candidate who lost it is safe, because the calendar file updates the event already in their calendar. Re-sending does nothing for a candidate whose booking locked after three reschedules, which needs a manual reset instead. And it does nothing for a cancelled interview, where the link is meant to stay dead.

When the problem is access, not delivery

If the invite clearly went out and the candidate still cannot get in, the issue has moved from delivery to access: a booking that locked, a campaign someone stopped, or a join window that closed. Those are covered in the broken-link triage guide. If the candidate’s worry is less “where is my link” and more “what is this AI going to do to my application”, that is a different conversation, covered in reassuring an anxious candidate.

Pairing your own note with the HireQwik invite

The HireQwik invite is good at one thing: turning a sheet row into a booked, calendared interview without a recruiter touching it. Asking it to also introduce your company, explain AI screening and set expectations is asking a scheduling message to do a recruiter’s job. The two work best as a pair: your words explain why, and the system’s messages make sure the when and where stay accurate even when a booking moves. Send a short human note first, let the system handle the logistics, and most of the “is this real?” emails stop arriving. If you change only one thing after reading this, add the sender line to your pre-notice, because an email from an unfamiliar domain is easy to mistake for spam. You can see the invite and booking flow for your own roles in the HireQwik HR dashboard.