> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/administrator-documentation/case-type-settings/creating-contact-custom-fields-contact-type.md).

# Creating Contact Custom Fields (Contact Type)

This lesson will show you how to create contact custom fields of the "Contact Type" category in AgileCase. Before you do this you should know how to create basic contact custom fields which you can see in [this](/administrator-documentation/case-type-settings/creating-basic-contact-custom-fields-person-or-company.md) lesson.

{% stepper %}
{% step %}

### Select "Contact Type" in group details

<figure><img src="/files/RFOMsDFjnDxSwEsWWCKA" alt=""><figcaption></figcaption></figure>

Contact type contact custom fields tie your custom fields to the relationship a contact has to a case and will appear on the case page.

To create a custom field group of this type, select the "Contact Type" option on the radio list when filling in the group details then click "Save Group" to proceed.
{% endstep %}

{% step %}

### Select a Case Type

<figure><img src="/files/qJMsDtuNzcxXF2ioDX3h" alt=""><figcaption></figcaption></figure>

When you go to create your custom fields in a group of this type you will notice two new options; case type and relationship. First, select a case type. This will tie the custom field group to the case type that you want them to be available in.
{% endstep %}

{% step %}

### Select a relationship

<figure><img src="/files/W4NM4QBmaDkXnKBwEGc4" alt="" width="328"><figcaption></figcaption></figure>

Next, select the relationship your contact should hold to the case. This allows the system to indentify the contact that the custom fields will be applied to.
{% endstep %}

{% step %}

### Create custom fields and save changes

<figure><img src="/files/chdOY9HJzgSMeWBJOeg3" alt=""><figcaption></figcaption></figure>

Once you have selected a case type and relationship, create your custom fields as you would in a basic custom field group and click "Save Changes" to complete the custom field group.
{% endstep %}

{% step %}

### View custom fields in case

<figure><img src="/files/C3FGHjjMgVGy9qhbEw9Q" alt=""><figcaption></figcaption></figure>

Your custom fields will now appear under the appropriate contact name on the "Contact Details" tab of the case. Here you can fill out the fields and click "Save Changes" in order to populate them.
{% endstep %}

{% step %}

### Cases with multiple contact types

<figure><img src="/files/kZBluKWMBCbKFbD7FrzU" alt=""><figcaption></figcaption></figure>

In a case where multiple case contact custom field groups apply, each contact will be listed with their custom fields below.
{% endstep %}
{% endstepper %}


---

# 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.agilecase.com/administrator-documentation/case-type-settings/creating-contact-custom-fields-contact-type.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.
