> 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/getting-started/setting-up-the-case-contact-relationship.md).

# Setting up the Case / Contact Relationship

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

In AgileCase, the most basic relationship is that between a contact and a case. By linking a contact to a case, their details will be listed under the **Contacts** tab. This makes it easy to communicate with everyone involved in a case, as all relevant contacts will be listed under this tab once their relationship to the case has been established.

{% stepper %}
{% step %}

## Create a contact

Select the **Add Contact** icon in the **Contacts** tab and fill in the appropriate information.
{% endstep %}

{% step %}

## Go to the case contacts tab

With a set of contacts established, you can relate them to your cases. Go to the **Contacts** tab under the main **Case** tab.
{% endstep %}

{% step %}

## Select the contact

Enter the name of the contact you wish to associate with the case. A search function helps you find the contact you want.
{% endstep %}

{% step %}

## Assign a relationship

Select one of the preset relationships, or type your own into the text box to create a new one.
{% endstep %}

{% step %}

## Link the contact

Click the **Link Contact** icon to establish the relationship. Once you have done this, your contact will be linked to the case.
{% endstep %}
{% endstepper %}

It is also possible to edit the relationships available via the settings screen. This allows you to remove the default data and edit existing relationships. You can also associate relationships with particular case types—in much the same way you relate a case type with a practice area—allowing you to create separate sets of relationships for different areas of your business.

With a relationship established, your contact will now be listed in the **Contacts** tab. The advantage of this relationship system is that it is specific to the case, not the contact, so one contact can perform multiple roles in several cases at the same time. For example, a contact could serve as a solicitor in one case and a consultant in another without the need to edit any contact details.

For more information about linking contacts to cases, please view the documentation topic [here](/administrator-documentation/case-type-settings/creating-contact-relationships.md).

In the next part, we will look at creating custom fields within a case, allowing you to configure your workflow by managing what information is required in each case type.


---

# 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/getting-started/setting-up-the-case-contact-relationship.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.