> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/interview-studies/conduct-an-interview-session/troubleshooting-interviews.md).

# Troubleshooting interview studies

Running into technical trouble with your interview session? We're here to help! Follow these troubleshooting steps to get your session back up and running.

{% hint style="info" %}
**Note:** The steps you'll need depend on how your study meets. For studies that meet on Zoom, Google Meet, or Microsoft Teams, see [Studies that meet on another platform](#studies-that-meet-on-another-platform).
{% endhint %}

## Studies that meet on Dscout

<details>

<summary>Re-joining a dropped session</summary>

If you encounter a dropped call or other issue, don’t panic! If you stay in the interview session and simply refresh the page, the scout should be able to re-join. If you need to chat with the scout via the Manage page, open it up in a separate browser tab.

*If you exit out of a session and are unable to re-join, you'll just need to add a new session.* Go to the Manage page > scroll to the scout’s name > click on the dropdown arrow next to the scheduled time slot > click “Add Session.”

</details>

<details>

<summary>Problems with internet connection</summary>

Most of the time, technical problems related to live interviews are the result of internet connectivity problems. It is important to keep tabs on your internet connection, as call quality is based on the strength of your internet connection.

During an interview session, you will see a status icon next to your and your scout's names. These represent your network latency. Latency is the measure of time it takes to send a packet of data from one endpoint to another.

{% hint style="info" %}
**Note:** A microphone problem or a weak connection doesn't prevent a participant from joining. If either check warns them before the session, they'll see troubleshooting tips and a **Join anyway** button. So you may occasionally start a session with a participant whose connection is poor or whose microphone isn't working. The status icon next to their name shows their connection; if you can't hear them, use the session chat to ask them to check their mic—they can still read and reply there.
{% endhint %}

If you or a scout are experiencing issues with your network:

* Close any other apps on your network that may be consuming large amounts of bandwidth
* Make sure your internet is working
* Try moving closer to the router

If you are unable to stabilize your network, we recommend communicating this with the other participant. Try to reschedule another time to complete your session when your network is reliable.

{% hint style="info" %}
VPNs and other internet security tools like Netskope or Cloudflare Zero Trust may disrupt your connection to interview sessions. If you or your organization use these tools and are experiencing issues using Dscout, please contact your Account Owner for assistance.
{% endhint %}

</details>

<details>

<summary>Problems with firewall</summary>

For some users, firewall configurations may prevent access to interview sessions. Dscout's interview room is powered by [Daily](https://www.daily.co/), so your firewall needs to allow access to Daily's servers and the providers it uses to connect calls. For the full list of domains, ports, and providers, see [Configure your network for interview sessions](https://help.dscout.com/interview-studies/what-are-interview-studies-in-dscout/configure-your-network-for-interview-sessions.md).

To check whether your network is set up correctly, run [Daily's network test](https://network-test-v2.daily.co/) from the same network you'll use for sessions. For more help, see [Troubleshooting firewall issues](https://help.dscout.com/interview-studies/conduct-an-interview-session/troubleshooting-firewall-issues.md).

</details>

<details>

<summary>Problems with microphone or camera</summary>

If you or a scout experience microphone / camera problems, Chrome or Edge permissions may be to blame. To troubleshoot:

**Chrome users** should click on the Menu icon in the top right corner (three dots) > Settings > Privacy & Security > Under Permissions, locate Camera > locate Dscout under "Allowed to use your camera" and tap > ensure that neither camera nor microphone are blocked for Dscout.

**Edge users** should click on the Menu icon in the top right corner (three dots) > Cookies and Site Permissions > All Sites > Locate dscout.com and verify that camera and microphone permissions are set to allow

</details>

## Studies that meet on another platform

In studies that meet on Zoom, Google Meet, or Microsoft Teams, your meeting platform handles the call itself, including audio, video, and connection quality. For help with those, refer to your platform's documentation. The steps below cover the parts Dscout handles.

<details>

<summary>The Start button is disabled</summary>

The session doesn't have a meeting link yet. Add a default link for your study or a unique link for the session, then try again. For more information, see [Add meeting links to an interview study](https://help.dscout.com/interview-studies/manage-an-interview-study/add-meeting-links-to-an-interview-study.md).

</details>

<details>

<summary>A participant can't find the Join Session button</summary>

Participants won't see **Join Session** on their study page in these cases:

* **The session doesn't have a meeting link yet.** Add one from the **Manage** tab of your study.
* **They're on a mobile device.** Studies that meet on another platform currently support desktop participants only, so participants need to open their study page on a desktop or laptop computer.

For more information, see [Participant flow in an interview study on another platform](https://help.dscout.com/interview-studies/manage-an-interview-study/participant-flow-in-an-interview-study-on-another-platform.md).

</details>

<details>

<summary>The recording bot didn't join the meeting</summary>

The recording bot, named **Dscout**, arrives at the session's scheduled start time. If you don't see it in the call:

* **Check your waiting room or lobby.** If your meeting uses one, the bot waits there until you admit it, like any other attendee. For more information, see [Waiting rooms and lobbies](https://help.dscout.com/interview-studies/conduct-an-interview-session/conduct-an-interview-session-on-another-platform.md#waiting-rooms-and-lobbies).
* **Check who's allowed to join.** If your meeting only allows signed-in users or people in your organization, the bot can't join. Change the setting so anyone with the link can join.
* **Check the session's meeting link.** If the **Meeting link** column on the **Manage** tab shows **This isn't a supported meeting link, so the recording bot may not be able to join**, replace it with a Zoom, Google Meet, or Microsoft Teams link.
* **Make sure you're in the right meeting.** Click **Start** on the **Manage** tab to open the meeting link the bot was sent to.

</details>

<details>

<summary>Part of the session wasn't recorded</summary>

Recording starts once the bot is in the call and stops when it leaves. Anything said before you admit the bot, or after it's removed from the meeting, isn't recorded. To record the full session, admit the bot as soon as your participant joins, and keep it in the call until you're done. For more information, see [The recording bot](https://help.dscout.com/interview-studies/conduct-an-interview-session/conduct-an-interview-session-on-another-platform.md#the-recording-bot).

</details>

<details>

<summary>The recording isn't on the Sessions tab yet</summary>

After the call ends, Dscout processes the recording and transcript before adding them to the **Sessions** tab of your study. This can take a few minutes. Once it's ready, the session is marked complete.

</details>

<details>

<summary>Speaker labels in the transcript are wrong</summary>

Dscout labels the meeting host as the moderator and the first other person to speak as the participant. If someone else hosted the meeting, or another attendee spoke before your participant, labels may be incorrect. Speakers can't be reassigned in these sessions, so have the session's moderator host the meeting and ask other attendees to stay muted. For more information, see [Speaker labels in the transcript](https://help.dscout.com/interview-studies/conduct-an-interview-session/conduct-an-interview-session-on-another-platform.md#speaker-labels-in-the-transcript).

</details>

## Other technical problems

Have a concern that isn't covered here? Direct your participants to email <help@dscout.com> and our team will troubleshoot with them directly. You can also chat with Dscout Support (between 9am - 5pm CST Monday - Friday) by tapping the question mark icon in the top right corner of your study.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.dscout.com/interview-studies/conduct-an-interview-session/troubleshooting-interviews.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
