> For the complete documentation index, see [llms.txt](https://docs-vnext.kiflo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-vnext.kiflo.com/partner-directory/how-to-get-leads-from-your-partner-directory.md).

# How to get leads from your partner directory?

Your partner directory includes a contact form on each partner's profile page. When a visitor fills out and submits this form, a lead is automatically created in Kiflo. This article explains how these leads are created and how to find and filter them.

## How it works

1. A visitor browses your public partner directory and opens a partner's profile page.
2. The visitor fills out the contact form with their information (name, email, company, etc.).
3. Upon submission, Kiflo automatically creates a new lead record.
4. The lead is associated with the partner whose profile the visitor was viewing.
5. The lead appears on your **Leads** page with the source set to the originating directory.
6. The lead is shared with the partner, and the partner is notified.

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-3ea64a906554066ca8ba4aed9517736ddb9d85bf%2F698dcb6261d50f00d53fb449.png?alt=media)

The fields shown on the contact form are configurable from the **Contact form** tab of your directory settings under **Manage > Partner Directories**.

**See**: [How to configure the contact form on directory profile pages?](/partner-directory/customize/how-to-configure-the-contact-form-on-directory-profile-pages.md)

## Finding partner directory leads

Leads generated from your partner directory are identified by the **Source** column on the Leads page.

1. Navigate to the **Leads** page.
2. Look at the **Source** column for each lead.
3. Leads from a partner directory will display the source as **Partner Directory ({Directory Name})**.

For example, if your directory is named "Service Partners", the source will show **Partner Directory (Service Partners)**. The directory name in the source column is a clickable link that takes you directly to the corresponding directory settings.

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-64c14b2245a65011e5a02406c34e339a6bc4f48e%2F698dcc1201066426f096e039.png?alt=media)

## Filtering leads by source directory

To view only leads that came from a specific partner directory, use the **Source directory** filter.

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-ffd0840499d5e14e43662180970cecd64746b1d6%2F698dccb861d50f00d53fb45d.png?alt=media)

### Step 1: Open the filters panel

1. Go to the **Leads** page.
2. Click the **Show filters** button.

### Step 2: Add the Source directory filter

1. Click on the property dropdown to add a new filter.
2. Select **Source directory** from the list of available properties.

### Step 3: Choose your filter criteria

The following operators are available for the Source directory filter:

| Operator         | Description                                                                                                                                     |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| **is any of**    | Show leads from one or more specific directories. A **Search directories** dropdown appears, allowing you to select the directories to include. |
| **is none of**   | Exclude leads from specific directories.                                                                                                        |
| **is empty**     | Show leads that did not originate from any partner directory.                                                                                   |
| **is not empty** | Show only leads that originated from a partner directory (any directory).                                                                       |

### Step 4: Apply the filter

1. After selecting your operator and values, click **Apply**.
2. The Leads list will update to show only the leads matching your filter criteria.

## Tips

* **Combine filters**: You can combine the Source directory filter with other filters (such as date range, status, or assigned partner) to narrow down your results further.
* **Use "is not empty" for reporting**: To get a quick count of all leads generated across all your partner directories, use the **is not empty** operator. This is useful for measuring the overall lead generation impact of all your directories.
* **Configure the contact form**: To control which fields visitors must fill out, go to **Manage > Partner Directories**, open your directory, and select the **Contact form** tab. You can add fields and reorder them.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs-vnext.kiflo.com/partner-directory/how-to-get-leads-from-your-partner-directory.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.