The Invite Line That Says Keep the Camera On

Candidates who were told to keep the camera on still write three ways. “Link broken.” “Screen froze.” “It asked for my camera and then nothing.” When I open the screenshot, two of those are the lobby and one is the pause. The product was consistent. The invite was not. If you want people to keep the camera on for a HireQwik interview, write the rule where they already look, which is the message above the booking link, not the shield icon they skip.

The hold itself, including the button, is in the in-call camera hold. This page is the message, the phone script, and the three misunderstandings I still have to unwind every drive.

Key takeaways

• Name both screens in the invite: the grey Join control, and the hold that covers the call.
• Tell them the microphone is quiet during the pause.
• Tell them the way back is Turn On Camera, not a fresh URL.
• Say a covered lens does not trigger the box.
• Move blur, lighting, and device choice to before they enter.
• A lobby failure is not a character conversation.

Write the camera rule as two screens, not one threat

Candidates collapse every camera moment into “I got in trouble.” Your email should refuse that collapse. There is a door, and there is a hold. They feel different, and the remedy is different.

The door: the browser must open a camera, or Join is grey and its text is Camera Required to Join. Denied permission and a missing device get their own short explanations, plus Retry Camera Access. Nobody has started. No pause has been counted.

The hold: after they are in, toggling video off mutes them and covers the call. That cover is headed Camera Turned Off. It stays. Turn On Camera restores video and the mic together. They can do this three times and continue. A fourth shutoff closes the session.

If your email only says “keep your camera on,” people hear a manner tip, like “smile.” They will still block the browser prompt because a classmate told them the site is suspicious, and they will still flip the control mid-call to chase a blur setting. Spell the two screens. The manners take care of themselves.

Here is a paragraph you can paste. It is deliberately not the campus WhatsApp note and not the tab-switch note. Those are other messages.

This interview will not start without a working camera. Allow the prompt. If you see Camera Required to Join as the button label, you are still outside: use Retry Camera Access after you allow the camera, or plug a webcam in. Once you have entered, leave video on. Switching it off silences your microphone and shows Camera Turned Off until you choose Turn On Camera. Three of those holds are recoverable. One more shutoff ends the interview. Arrange lighting before you enter. Keep the lens clear. A hand over it does not help.

That paragraph is the whole policy a candidate needs. A longer email does not make it kinder. It makes the camera lines easier to miss.

Booking steps, the microphone, and early must-have questions sit in the wider preparation note. Leaving the browser page is a separate rule, written in the tab-switch briefing. If you send both camera and tab lines, give them separate sentences. One blended “don’t move” sentence is how people burn the wrong counter and then quote your email back at you.

A phone script for the lobby, ninety seconds

When someone calls from the lobby, do not open with integrity. Open with the button label.

Ask: does the button say Camera Required to Join, or are you already talking to the interviewer? If it is the button, ask whether they saw “access denied” or “no camera found.” Those are the two lines the page uses. Denied means the browser site setting is Block. No camera means the machine did not expose a device. Retry Camera Access only works after that underlying fact changes. Clicking it ten times on a laptop with the webcam unplugged changes nothing.

Then give them the Allow path in that browser, one path, not three. For Chrome, that path is site settings, then Camera, which Chrome’s permission steps list. The prompt the page shows is the browser camera request described in Mozilla’s getUserMedia notes. Ask which browser they have before you describe the Allow click. A Chrome path read out to someone on Safari wastes the slot. If the slot window is about to close, book another time rather than coaching them into the last two minutes. A rushed entry is how the next complaint, the pause, gets born.

Say, before you hang up, that once they are in they should not touch the camera control. Curiosity about the control is a pause. You want them curious before they enter, on the preview, where a failed preview is still only a locked door.

A phone script for the pause, even shorter

If they are already inside and Camera Turned Off is the heading, the script is one action.

The session has not closed. Your microphone is quiet because video is off. Press Turn On Camera. Stay in that window. I am not sending another link.

Then stop. Extra texts pull them onto a phone and can cover the interview window, which spends a different tally. One instruction. The button. If they report that Turn On Camera had no effect, ask whether a permission prompt came back. One retry. If the webcam has disappeared, stop the call-centre routine. Note the time. Decide later whether another slot is fair, using the record rather than the apology. That later decision is written in when a camera pause ends the room.

Skip any request for a photo of the room as proof they were alone. You will not review those photos the same way twice, and the request teaches people the process can be bargained.

Blur, a covered lens, and a second gadget

These three arrive every week. Answer them in the invite so Monday night is not a rewrite.

Blur and virtual backgrounds belong on the lobby preview, before Join. The preview is there so they can see their own face. Switching the camera control off after the interviewer has started is the pause, even if their intention was a setting. Intention is not what the counter stores.

A hand, a sticker, or a notebook across the webcam does not fire this pause. The control is still on, so the call continues, and the recording will show a black frame or a ceiling. Tell them a reviewer can watch that. Never claim the software “detects a covered camera.” It does not look at the pixels for this rule. I would rather they hear the limit from you than discover it in an appeal and decide the whole note was theatre.

A second phone propped up to “be the camera” while the interview runs on a laptop is not the camera track unless the laptop actually selects that phone as its camera. The join check is the browser’s camera on the device running the page. One device. One allowed camera. Face visible. Anything more clever fails in a lab and then becomes your evening.

Headphones are fine. They do not touch this counter. Mention them only so nobody unplugs the webcam while hunting the audio jack. That hunt, on a lab PC, is a classic way to hit the camera control by accident. Say “plug audio in before you allow the camera,” and you remove a class of pauses that feel unfair because they were.

What the pause is not, so the email stays accurate

Do not write that the clock freezes. The promise on the box is that speech resumes once video is back. It is not a promise about a timer.

Do not write that one pause fails the application. The room continues, inaudible, until they restore video, for the first three times.

Do not write that pause number three closes the session. The close is the shutoff after that.

Do not write that we scored their eyes. There is no gaze model in this pause. The count is the control. The recording is what a person can watch later. Those are different objects, and the score, if one exists, comes from what they said. The camera count does not move it. If a candidate asks, point a curious recruiter at why the camera count stays off the points, and tell the candidate the short version: a pause is not a mark.

Do not soften the rule in a side channel after the email goes out. A private “we never really pause” becomes the version the batch believes. A private “one blink and you are out” becomes the version they fear, and then a normal lobby lock gets described as a rejection. The email’s version has to be the only version.

Let them meet the prompt before the scored slot

The first time a person sees a camera prompt should not be the minute their slot opens. Send them, a day ahead, to the ungraded sample on hireqwik.in. The point of that practice is the voice and the prompt, not a drill in how many times the control can be switched off. Say that plainly. The aim is to finish the tinkering before the scored room starts.

Someone who has already allowed a camera once, on a practice page, is less likely to hit Block on the real morning out of surprise. Surprise is the lobby’s real enemy. The pause’s real enemy is mid-call tinkering. Practice reduces the first. The email reduces the second. Together they are the briefing. A PDF titled “AI interview etiquette” that never names the button fails that test.

Put the keep-camera-on paragraph in every channel

I have watched a drive send three versions in one afternoon. The careers email said “camera on, please.” The WhatsApp from the coordinator said the pause would fail the application. The poster on the lab door said nothing about a camera at all. A campus cell’s Sunday wording is a fourth version if you do not align it, and that wording lives in the campus camera-off note. The shape of a normal invite, before you add the camera lines, is in how an AI interview invitation is written. Candidates believed the strictest version they saw, then quoted it back when a lobby lock felt like a rejection.

Pick one paragraph, the one above, and paste it into the email, the WhatsApp, and the door. If a channel cannot hold the paragraph, leave the camera rule out of that channel rather than shortening it into “keep smiling and keep the camera on.” A short version is how the two screens collapse again.

Also name who answers the phone. A candidate who calls the front desk will hear one account. A candidate who calls the recruiter who wrote the email may hear another. Give the front desk the ninety-second lobby script and the one-line pause script, printed. If they are unsure, they book another time. They do not improvise a ban.

Parents and placement officers will forward the email. Write it so a forward still makes sense. No internal slang, no “we usually let the third one slide,” no joke about cheating. The forward is the policy. If you would be embarrassed to see it in a grievance thread, rewrite it before it goes out.

One more check before you hit send. Read the paragraph next to the tab-switch paragraph if you are sending both. Each rule needs its own sentence and its own remedy. A candidate who mixes them will restore the camera and still lose the room because they opened a notes tab, or they will stay on the page and still sit in silence because video is off. Separate sentences prevent that mix-up. The invite for leaving the page is the other briefing, already linked. Do not merge the two into a single “stay put” line.

If this paragraph should land in the template your open roles use, and you want to watch a locked join and a live hold before candidates do, book a walkthrough. Block a camera, allow it, switch it off, restore it. Then send the email.

One last read before it goes out. Sit with a colleague who has not seen the product and ask them to point at which sentence is the lobby and which sentence is the hold. If they cannot, the paragraph is still one threat. Split it until they can. That thirty-second test catches more bad invites than another round of wording inside your own head.