What to email when you have technical issues in a video interview

A technical-difficulties email is the short note you send when a video interview breaks. You name the exact step that failed, say plainly it was a fault and not a missed deadline, and ask for one fix: a fresh link, a reset, or confirmation of what recorded. Send it within the hour and most teams reopen it.

That is the whole move. The rest of this page gives you the actual emails, sorted by what went wrong, plus who to send them to and the honest read on whether a glitch costs you the job. Short version on that last part: it rarely does.

These templates cover both kinds of interview. A live call on Zoom, Teams, or Meet where a person is waiting, and a recorded one-way interview where you answer set questions with no interviewer present. The wording shifts a little between them, and each block below says which case it is for.

First, a few seconds of diagnosis

A specific email is worth ten vague ones, so work out which thing actually happened before you write. It takes a moment and makes the message instantly actionable.

• The camera or mic would not work and you could not start, or you started without one of them. Fixes for this live on the camera not working page.
• An answer would not upload, or one clip is stuck on “processing” while the rest went through. This is the most common case on recorded interviews.
• The connection dropped mid-call or mid-recording. The internet connection page covers the in-the-moment recovery.
• The link expired or locked you out partway through, and you cannot get back in.
• The page froze or crashed during an answer, and you do not know whether it saved.

Note the exact question number or step where it broke. That single detail is the most useful thing you can hand a recruiter, because “question 3 would not upload” is something they can act on and “it didn’t work” is not. If you can, screenshot the error, the not-submitted status, or the frozen screen with a timestamp. You probably will not need to send it, but it is your proof that this was a fault and not a missed deadline.

Who to email, in order

You usually have two contacts. Use both if you have them.

• The recruiter or hiring contact first. They own the decision and can almost always reset your invite or extend the deadline. Their address is in the original invitation, the email that carried the interview link.
• The platform’s support address second. Recorded-interview tools like HireVue, Spark Hire, Willo, and VidCruiter usually have a support email or help link, often in the invite footer. Support can confirm what was actually captured on their servers, which sometimes reveals your answers saved fine after all.

If you only have one of the two, use it. The recruiter matters more, because they are the person who decides what happens next.

The email: a recording failed to submit

For a one-way or recorded interview where an answer would not upload, the page froze, or you got a submit error. This pairs with the deeper walkthrough on what to do when a one-way interview did not submit.

Subject: Technical issue with my recorded interview, [Job title]

Hi [Name],

I recorded the interview for the [Job title] role today, but I ran into a technical problem. [Question 3 would not upload and still shows as not submitted / the page froze during one of my answers / I got an error when I hit submit.] I have a screenshot if it helps.

I would like to finish this properly. Could you reset my link, or let me know whether you can see what was already recorded? I am happy to re-record [the missing answer / the whole set], whatever is easiest on your end.

Thanks for your help, [Your name]

The email: the link expired or locked you out

For a recorded interview where the session died partway through and you cannot get back in. Expired or timed-out links mid-interview are a known issue and are not your fault.

Subject: Expired interview link, [Job title]

Hi [Name],

I was completing the recorded interview for the [Job title] role and the link expired partway through, at [question 4]. I can no longer get back in to finish.

I would still like to complete it. Could you reissue the link or reset my invitation? If there is a deadline on it, would you be able to pause that while we sort this out.

Thanks very much, [Your name]

The email: a live call cannot connect

For a scheduled live interview on Zoom, Teams, or Meet, when your camera, mic, or connection fails at the start and the interviewer is waiting. Send this fast, because a real person is on the other end.

Subject: Technical trouble joining our interview, [Job title]

Hi [Name],

I’m having a technical problem joining our [time] interview. [My camera will not start / my audio is not coming through / my connection keeps dropping] and I have not been able to fix it in the moment.

I’m trying to rejoin now from [my phone / another device]. If that does not work in the next few minutes, could we reschedule for the soonest time that suits you? I’m keen to talk and sorry for the disruption.

Thanks, [Your name] [Phone number]

If it is a live call and you are mid-conversation when things glitch, you often do not need an email at all. A calm “sorry, my connection just dropped, give me one second” and a rejoin handles it. The email is for when you cannot get back in, or to follow up afterwards. There is a full recovery script on what to do when your internet drops.

Why these emails work

Every one of the templates above is built the same way, on purpose.

• They name the exact failure. A recruiter can act on “question 3 would not upload” or “the link expired at question 4.” They cannot act on “it broke.”
• They offer a fix instead of asking forgiveness. You are making it easy to say yes: reset the link, confirm what saved, reschedule. You are not waiting to be rescued.
• They do not grovel. One clean apology is enough. A spiral of sorries reads worse than the glitch did, and the glitch was not your fault.
• They ask to pause the clock where there is one. A countdown on a recorded link should not keep running while you wait for a reply. Naming it protects you.

Send the moment you notice. A message inside the hour reads as a genuine fault. One sent three days later, after the deadline, is a much harder thing for a recruiter to reopen, even when they would like to.

Does a technical glitch actually cost you the job?

Almost never, and here is the honest reasoning. Recruiters and the platforms know these tools fail. Dropped uploads, frozen recordings, and expired links are ordinary support tickets, not rare events. The hiring team has almost certainly seen the same tool stumble before, so a single hiccup does not surprise them. A candidate who hits a snag, flags it calmly, and offers to fix it does not look careless. If anything, handling a small technical mess cleanly is a mild point in your favor, because composure under a hiccup is exactly what most jobs ask for.

The thing that genuinely hurts you is silence. If you say nothing and an answer is blank, the recruiter has no way to tell a glitch from a no-show. So the rule is simple: the failure rarely sinks you, but not reporting it can.

A different problem: when the format itself is the barrier

Everything above is for a tool that broke. If the issue is not a glitch but the format itself, a clock that will not pause, no captions, a hard cap on retakes, or a camera that has to be on when the role never asked for it, that is a different email. You are not reporting a fault, you are requesting a reasonable adjustment, and you are allowed to. The wording, the menu of things you can ask for, and the reasoning behind each line are on the accommodation request email template.

After you send it

You have done the part you control. Now wait without feeding the worry.

• Do not email five times. One clear message, then give them a working day or two. A short reminder after that is fine. A barrage is not.
• Do not re-record the whole interview unprompted unless the recruiter asks. You might overwrite a version that was actually fine.
• Do not read silence as a rejection. If your application still shows as under review a few days on, that is normal pacing, not a verdict.

A technical failure feels like the end of the process. It is almost always a five-minute detour. You flag it, they reset it, you finish it.

If you want to stop this happening in the first place, the surest fix is to test your setup before the interview, in the actual app, the day before. And if the underlying worry is not the glitch but how your answers came out, read what to do when you think you bombed a one-way interview.