Ask Fin first
Fin is the assistant in your dashboard. It knows this Help Centre and the FAQ, and it is the fastest route for anything already documented. It is also the fastest way to find out that your problem is not documented, which is worth knowing before you write a ticket.
Open a ticket
From Help & Support in your sidebar. A ticket reaches a person.
What to include
The difference between a useful first reply and three rounds of clarification:
- What you were trying to do, in one sentence.
- What happened instead, including the exact wording of any message.
- When — the date and roughly the time, with your timezone. This is the single most useful thing you can provide, because it is what makes the event findable in a log.
- The link to the interview, candidate or position involved.
- Your browser and operating system, for anything about camera, microphone or screen.
What not to send
Never send a password, an API key, or a verification code. Support will never ask for one, and anything you paste into a ticket is stored with it.
For candidates with an interview problem
If it is about a deadline, a reschedule or whether you may sit something again, the organisation decides, not us. Reply to their invitation email. Support can explain how something works; it cannot change a decision that belongs to the employer.
Urgent, mid-interview
Finish if you possibly can — a completed interview with a recorded problem is far easier to make right than an abandoned one. Then raise it immediately, while the timing is still precise in your memory.