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

# Improve your interview session quality

If your call quality is poor, it's probably due to a poor internet connection. This can cause dropped calls, delays, and low-quality audio and video.

Below, you'll find some quick tips to help improve your call quality when participating in an interview study.

* Improve your internet connection: Make sure you have a strong WiFi signal, or if possible, use a wired connection via ethernet cable.
* Close other tabs and applications: interview studies rely on having plenty of your computer's bandwidth to support the call. File sharing applications, streaming audio or video, downloading files, or even just having another browser open are all things that can eat up bandwidth.
* Plug in your laptop: If your device has low battery or is in power-saving mode, try plugging the laptop into a power source or switching it to maximum performance mode.

If call quality does not improve, consider ending the session and requesting to reschedule for a time when you have access to better internet quality.

***

*Last updated: 2026-05-21*\
\&#xNAN;*Source:* [*Improve your interview session quality*](/interview-studies/interview-troubleshooting/improve-your-interview-call-quality.md)


---

# 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://participanthelp.dscout.com/interview-studies/interview-troubleshooting/improve-your-interview-call-quality.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.