> 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/participate-in-interview-studies/your-desktop-interview-to-do-list.md).

# Your desktop interview to do list

Complete these tasks more than 24 hours before your session. It is important to be set up well in advance so you are on time to your interview session. If you are more than 10 minutes late, you could be marked as a no-show and may not have another opportunity to participate. **Be sure that you have a desktop or laptop computer with a webcam and microphone!**

1. Make sure you have [Google Chrome or Microsoft Edge](/interview-studies/interview-technical-requirements/interview-browser-compatibility.md) installed on your computer.
2. **If you are running macOS Catalina—version 10.15—or more recent**, [ensure that Chrome or Edge are granted access to the new Screen Recording Permission](/interview-studies/interview-technical-requirements/enable-screen-recording-permissions-for-interviews.md).
3. Complete your interview pre-test by clicking on the session link in your invitation email. Follow the prompts here to test your connectivity, camera, microphone, and speakers to make sure your set-up is good to go for your call!
4. Then return to your interview session link and run through the join call flow all the way through once. Once you reach the waiting room, you will see a screen with yourself in the bottom right corner and a message in the center of the screen that says, “This session is scheduled for…” followed by a series of helpful tips. In addition, you’ll see the moderator’s/moderators’ name/photo and whether they have connected to the session.
5. You can close out this link for now but be sure to come back to this link and follow the same flow when it's time for your session! See the steps outlined [here](/interview-studies/participate-in-interview-studies/participating-in-interview-studies.md).

If your **camera, microphone, or browser** check fails, take a screenshot and email it to us [here](mailto:live@dscout.com) for support, **at least 24 hours before your session,** and check out the following docs for troubleshooting:

* [Troubleshooting camera, microphone and sound issues](/interview-studies/interview-troubleshooting/camera-microphone-and-sound-issues-for-interviews.md)
* [Troubleshooting firewall issues](/troubleshooting/troubleshooting-firewall-issues.md)

If only your **connection** check comes back weak, you don't need to contact support—you'll still be able to join your session. See [Improve your interview session quality](/interview-studies/interview-troubleshooting/improve-your-interview-call-quality.md) for ways to strengthen your connection before your call.


---

# 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/participate-in-interview-studies/your-desktop-interview-to-do-list.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.