> For the complete documentation index, see [llms.txt](https://docs.pulselabs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pulselabs.ai/participants/recruitment.md).

# Adding Participants

The platform supports several ways to choose participants for your project.

If you want to find and invite participants, you can recruit from the Pulse Voices panel or recruit your own participants via an external recruitment link that can be shared through your own channels.

If you have already chosen your participants, you can add them directly to your project.

### Recruiting participants

#### Pulse Voices panel

Pulse Labs operates its own participant panel — many panel members are already ID-verified.

When recruiting from the Pulse Voices panel, you’ll first be asked to complete a brief feasibility form to ensure our participants are the right fit for your project.

#### External recruitment link

Share a recruitment link through your own channels, such as social media posts, email newsletters, Slack messages or internal comms.

The link directs people to a participant-facing page where they can learn about your study and begin the verification process.

### Bring-Your-Own-Participants

Invite specific people by email:

* **Individual emails** — Under the Recruitment tab, type email addresses one at a time with first name and last name.
* **CSV/Excel upload** — Upload a file with a list of email addresses and names for bulk invitations
* **Re-invite past participants** — Pull from participants who have joined previous studies in your workspace

Inviting your own participants works well when you already know who you want to recruit — existing customers, internal users, or contacts from previous research.

#### **More about BYOPs**

When you invite your own participants by email, they will still sign in and create Pulse Voices accounts. They are not added to the Pulse Voices panel nor marketed to using the platform. Other conditions include:

* **Limited Profile information** — No demographics are captured, only name, email, and location.
* **Blocked from seeing other studies** — In addition to not receiving marketing emails, the Explore tab of the Pulse voices app is disabled until the BYOP study is archived.
* **Blocked from marketing emails** — BYOPs are marked as do-not-market unless they proactively seek to join other studies which they are blocked from doing until the end of the BYOP study.
* **Active opt-in post study** — When the project for which they were originally recruited is archived, net-new BYO participants may, at their next platform sign in, voluntarily opt-in to the platform's general research panel to access future study opportunities.

However, if a BYO participant navigates to an external recruitment link independently, they are permitted to sign up as a Pulse Voices participant. If a panelist is already a Pulse Voices member when they are added to a BYOP project, the researcher adding them is informed of this.

### Recruitment settings (Marketing)

When recruiting from the Pulse Voices panel or through external links, you control how your study appears to potential participants. These settings are configured when adding participants and then can be modified from your project settings.

<table data-header-hidden><thead><tr><th width="151.800048828125"></th><th></th></tr></thead><tbody><tr><td><strong>Setting</strong></td><td><strong>What it Controls</strong></td></tr><tr><td>Visibility</td><td><ul><li><strong>Open</strong> — Study appears in the Pulse Voices directory. Eligible Pulse Voices panelists can discover it and apply.</li><li><strong>Closed</strong> — Study is invite-only. No public listing. Participants can only join through direct email invitation or a shared link.</li></ul></td></tr><tr><td>Details</td><td><ul><li><strong>Display Name</strong> — The study name participants see (can differ from your internal project name)</li><li><strong>Description</strong> — A participant-facing summary of what the study involves</li><li><strong>Tags</strong> — Topic categories that help participants find your study in the directory</li></ul></td></tr><tr><td>Image</td><td>A visual that appears in listings — upload your own, choose stock, or generate with AI.</td></tr><tr><td>Timeline</td><td>Estimated time commitment for participants to complete the study.</td></tr><tr><td>Payout</td><td>Amount that participants will be paid.</td></tr><tr><td>Webpage</td><td>Link to your marketing page. You’ll be able to send this page to potential participants or share it on your social channels to market your study and allow participants to enroll.</td></tr></tbody></table>

All of these settings are viewable to the participants.

#### AI-generated images

Don't have a design team? The platform can generate project images from your study description using AI. You'll be given multiple options to choose from, all at professional quality. You can also search integrated stock image libraries or upload your own.

### Payout

Communicate compensation clearly. Include:

* **Amount** — What participants will be paid
* **Timing** — When payment happens (within three weeks after we receive and verify feedback.)

### Tips for better recruitment

* **Write a clear, honest description** — Participants should understand exactly what they're signing up for. Studies with vague descriptions get lower-quality applicants.
* **Set realistic time estimates** — Overestimating discourages sign-ups. Underestimating leads to drop-offs.
* **Use specific tags** — Tags like "mobile app testing" or "smart home" attract more relevant participants than generic ones like "research study."
* **Choose a good image** — A relevant, professional image makes your listing stand out in the directory.
* **Combine channels when needed** — Use the Pulse Voices panel for broad reach and direct invitations for specific segments you need to fill.

***

### Finding the right participants from the Pulse Voices panel

#### Feasibility form

If you choose to use the Pulse Voices panel, you will first be asked to complete a brief feasibility form. This form allows us to ensure that our pool is a good fit and that you are confident to launch a screener survey as the next step.

<div align="left"><figure><img src="https://3270273690-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCt1H4tz9q0ev1mtKxrm%2Fuploads%2Fgit-blob-f254d148293030d5d5663a81873e584202012757%2FFeasibility%20form%20-%20new.png?alt=media" alt="" width="358"><figcaption></figcaption></figure></div>

You will be asked to complete this form only once for each project.

### Screener survey

A screener is a qualification questionnaire that determines whether a participant meets your study criteria whether from the Pulse Voices panel or BYO participants.

#### How it works

1. Build a screener survey using the same builder used for regular surveys.
2. Use filters to manually review and approve screener responses.
3. Enroll the approved participants into data captures.

#### When to use it

* You need participants with specific experience, behaviors, or demographics
* You want to filter a large pool down to your target audience
* You need to balance your sample across different segments

You will be asked to choose **Open** to launch the screener to the full Pulse Voices panel, or choose **Closed** to send it only to your uploaded BYO participants.

***

\ <br>


---

# 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://docs.pulselabs.ai/participants/recruitment.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.
