> For the complete documentation index, see [llms.txt](https://docs.inogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inogic.com/livechat4dynamics/configuration/configuring-record-types.md).

# Configuring Record Types

Users need to configure **Record Types** for all those entities with whom they want to message. Also, at times a record can have **multiple phone numbers**. Messages will be sent to the phone numbers selected in the **‘Phone Number Field’**.

{% hint style="info" %}
**Note:**&#x20;

* By default, a contact Record Type is created.

* Against one Entity, only one Record Type can be created.
  {% endhint %}

* Click on **+New Record Type** to create a New Record.

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

* Mention the **Record Type.**

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

* You can choose any Entity from OOB to Custom ones. However, this is only functional on Entities that have a phone number associated with them.

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

Enter the related record type from the list provided as shown below:

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

&#x20;

{% hint style="info" %}
**Note:** While configuring, in background, we have a logic to create field. Due to this, it is extremely important that System Admins give privileges to the users.
{% endhint %}

* For the system to decide, whether the message should be sent, the message **Compliance Field** is used.
* The **Compliance Field** lists all the Boolean Fields within the **Record.**
  * If the value is selected as **Yes,** messages will be sent.
  * If the value is selected as **No,** messages will not be sent.
* **Phone Number Field:** Add phone number field.
* **Default Country Code:** Provide the required country code.
* **Priority Order:** Enter priority order according to your business needs.

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

{% hint style="info" %}
**Note:** In case the Compliance Field is not set, the message will be directly sent without validation.

In the screenshot below, we have selected **‘Allow SMS’**, you may select a field as per your preference.
{% endhint %}

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

* In the **Phone Number Field**, all the multiple phone number fields within a Record are listed and you can choose whichever contact as preferred. But, note that the particular field selected should have a working contact number.

{% hint style="info" %}
**Note:** The selected contact numbers need to have **Country Codes and must be working.**
{% endhint %}

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

{% hint style="success" %}
For further queries, reach out to us at <crm@inogic.com>
{% endhint %}


---

# 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.inogic.com/livechat4dynamics/configuration/configuring-record-types.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.
