Metaview couldn't automatically match
The extension tries to auto-match your scorecard to a Metaview conversation. If no match is found, you can manually pick the correct conversation from the side panel session picker.
Why were some scorecard fields left blank?
This is expected as Metaview intentionally leaves subjective fields blank - anything that requires your own judgement as the interviewer (e.g. “Would you recommend this candidate?” or “How strong are the candidate’s technical skills?”) is left for you to complete. Additionally, if the transcript doesn’t contain relevant information for a particular scorecard question, that field will also be left blank. If you’d like Metaview to autofill a question that’s currently being skipped, try rewording it to be more objective - for example, instead of “How strong are the candidate’s technical skills?” try “Summarize the candidate’s technical skills based o the interview discussion.” The key is to shift the question from asking for your opinion to asking about what was actually discussed, so Metaview has concrete transcript content to pull from.
I'm being asked to log in again
The extension authenticates via a browser cookie. If you’ve cleared your cookies, are using icognito mode, or the session has expired, you’ll see the login screen again. Simply click Log in to reauthenticate.
Your ATS isn't connected yet
This means your Metaview workspace doesn’t have an ATS configured. Go to your Metaview settings in the web app and connect your ATS (Greenhouse or Ashby) first. The extension will then be able to autofill scorecards.
Unassigned speakers warning
If a session’s transcript has unassigned speakers, the extension will show a warning. This can affect autofill quality - go to the session in Metaview and assing speakers before autofilling. To find detailed steps on how to assign participants, please visit this page.
This LinkedIn profile doesn't match any candidates in Metaview
The extension looks up the candidate in Metaview when you visit their LinkedIn profile. If there’s no match, it means this person isn’t in your Metaview workspace yet.