> 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/customize/how-to-configure-the-contact-form-on-directory-profile-pages.md).

# How to configure the contact form on directory profile pages?

Each partner profile page in your directory can include a contact form that allows visitors to reach out to a partner directly. The **Contact form** tab lets you control what fields appear on this form, how they are organized into sections, and whether each field is required or optional.

This article explains how to configure the contact form, including adding and removing fields, organizing fields into sections, reordering items, and managing field requirements.

## Accessing the Contact form tab

1. Go to **Manage > Partner Directories**.
2. Click the directory you want to configure.
3. Select the **Contact form** tab.

## Understanding the form structure

The contact form is organized into **sections** and **fields**.

* **Sections** group related fields together. Each section has a **Title** and a **Description** that are displayed on the public form as a heading and explanatory text.
* **Fields** are the individual inputs that visitors fill in. Each field corresponds to a lead property in Kiflo.

For example, you might have a section titled "Tell us more about you" containing basic contact fields (first name, last name, email), and a second section titled "Project" with fields related to the visitor's project details.

## Default fields

Every new contact form includes the following default fields:

| Field            | Default status | Can be removed |
| ---------------- | -------------- | -------------- |
| **First name**   | Required       | No             |
| **Last name**    | Required       | No             |
| **Email**        | Optional       | Yes            |
| **Company Name** | Optional       | Yes            |

**First name** and **Last name** are always required and cannot be made optional. These fields ensure that every lead created through the directory has at least a name.

## Adding fields to the form

You can add any **lead property** from your Kiflo account as a field on the contact form.

1. Click the **Add field** dropdown at the bottom of the form.
2. Use the **Search** box to find a specific property by name.
3. Click on a property to add it to the form.

The field is added at the bottom of the last section.

### Supported field types

Depending on the lead property type, fields render differently on the public form:

| Property type           | How it appears on the form                                |
| ----------------------- | --------------------------------------------------------- |
| **Single-line text**    | A single-line text input.                                 |
| **Multi-line text**     | A multi-line text area for longer responses.              |
| **Date**                | A date picker.                                            |
| **Single/Multi-select** | A dropdown selector with predefined options.              |
| **Number**              | A numeric input field.                                    |
| **Currency**            | A text input prefixed with the currency code (e.g., EUR). |

## Adding sections

Sections let you visually group related fields together on the form. To add a new section:

1. Click the **Add section** button at the bottom of the form.
2. A new empty section appears with **Title** and **Description** fields.
3. Enter a meaningful title and description for the section.
4. Add fields to this section or drag existing fields into it.

{% hint style="info" %}
**Note**

You can add as many sections as you need to logically organize your form.
{% endhint %}

## Making fields required or optional

Each field has a toggle switch that controls whether it is **required** or **optional**:

* **Required** fields must be filled in by the visitor before they can submit the form. Required fields are marked with an asterisk (\*) on the public form.
* **Optional** fields can be left blank.

To change a field's requirement status, click the toggle switch next to the field name.

{% hint style="info" %}
**Note**

The **First name** and **Last name** fields are always required. Their toggles are locked and cannot be changed.
{% endhint %}

## Reordering fields and sections

The order of fields and sections on the contact form configuration directly matches the order displayed on the public form.

To rearrange items:

1. Hover over the field or section you want to move.
2. Click and hold the **drag handle** (the dotted icon on the left).
3. Drag the item to its new position.
4. Release to drop it in place.

You can reorder both fields within a section and entire sections relative to each other.

## Removing fields and sections

To remove a field or section from the form:

1. Hover over the field or section you want to remove.
2. Click the **delete icon** (X) that appears on the right side.

Removing a field from the form does not delete the lead property from your Kiflo account. You can add it back at any time using the **Add field** dropdown.

{% hint style="info" %}
**Note**

The **First name** and **Last name** fields cannot be removed from the form.
{% endhint %}

## Privacy consent

The contact form automatically includes a **privacy consent checkbox** at the bottom of the form. This checkbox is displayed to visitors and must be checked before the form can be submitted.

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

The **privacy policy** link in the consent text points to the URL configured in the **General settings** tab of your directory (the **Privacy Policy** field). Make sure this URL is set so that visitors can review your privacy policy before submitting the form.

## Saving your changes

After making changes to the contact form:

* Click **Save** to apply your changes. If your directory is published, the changes will be reflected on the live form immediately.
* Click **Cancel** to discard unsaved changes and revert to the last saved state.

## Best practices

* **Keep the form short.** Only ask for the information you truly need. Long forms with many fields can discourage visitors from completing them.
* **Use sections to group related fields.** If you need several fields, organize them into logical sections with clear titles and descriptions so the form is easy to follow.
* **Make only essential fields required.** The more required fields you add, the higher the chance visitors will abandon the form. Reserve the required status for fields that are critical to qualifying the lead.
* **Preview your changes.** After configuring the form, visit a partner profile page on your published directory to verify that the form looks and works as expected.


---

# 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/customize/how-to-configure-the-contact-form-on-directory-profile-pages.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.