> For the complete documentation index, see [llms.txt](https://law-centres-network.gitbook.io/enquirydesk-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://law-centres-network.gitbook.io/enquirydesk-documentation/fundamentals/enquiries.md).

# Enquiries

{% hint style="info" %}
**Good to know:** Enquiries are person-centred. That means that each enquiry must have a contact associated with it and people can have more than one enquiry. 
{% endhint %}

### Adding details about an enquiry

Each enquiry has two parts:

1. **Enquiry Details** (the information that can be gathered about the nature of an enquiry)
   * *Enquiry form* collects details about the nature of the enquiry
   * *Comments* collects messages between users about the enquiry
2. **Contact Details** (the personal information that can be gathered about a contact)
   * *Contact Details* collects details about the contact
   * *Contact Methods* allows you to add further contact methods to the Contact's record

To edit the Enquiry or the Contact details, select the relevant field. 

{% embed url="<https://www.loom.com/share/8977687382404ccbbfb4cbebe443b6a9>" %}

To customise what information is recorded about the Enquiry or the Contact, select **Configure > Forms**.&#x20;

### Managing enquiries

A communication becomes an enquiry if the contact details are not recorded on the system. That means if a person emails, and then calls, you will need to merge these enquiries together. See more on [**Merge enquiries**](/enquirydesk-documentation/guides/managing-your-enquiries/merge-enquiries.md).

When an existing contact contacts the Law Centre, their communication will fall within their existing enquiry. That means if a person is seeking help with a new matter, you will need to duplicate these enquiries and make a new enquiry for the new legal matter. See more on [**Duplicate enquiries**](/enquirydesk-documentation/guides/managing-your-enquiries/duplicate-enquiries.md).&#x20;

To manage the to do list, you can **Pin** enquiries to the top of the list. This will pin enquiries for you ONLY. &#x20;

![](/files/YJXIqd5nE3ZjkwB04W33)

### Assigning enquiries

All enquiries that have not yet been assigned to an individual or team can be found under **Unassigned**. This becomes, in effect, a to do list. When you assign an enquiry to an individual or team, they will be notified and the enquiry will move to the **Assigned** list. See more on [**Assigning an enquiry**](/enquirydesk-documentation/guides/assigning-an-enquiry.md).

### Actioning an enquiry

All enquiries should eventually be closed, which means you will need to select an Action from the list of available options. See more on [**Actioning an enquiry**](#actioning-an-enquiry).&#x20;

### Enquiry History

The Enquiry History provides an overview of every action taken on the enquiry, including who, when and what.&#x20;

![How to access Enquiry History](/files/FnW3JUD7yIYUSYDDXmnD)

### Type of enquiry

To change the type of enquiry, select from the list available options. To customise the list of options, see [**Customisation**](/enquirydesk-documentation/guides/customisation.md).

### Viewers

To ensure you know who is looking at the enquiry at the same time you are, EnquiryDesk shows you who is active and has the current enquiry open.&#x20;

![Viewers allows you to see who is also look at the enquiry](/files/0iLVhPKVnoUy0CcYOtZG)


---

# 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://law-centres-network.gitbook.io/enquirydesk-documentation/fundamentals/enquiries.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.