> 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/user-adoption-monitor/configuration/setting-up-other-messages/special-messages.md).

# Special Messages

User Adoption Monitor supports the following special messages apart from the CRUD operations. You will find sample entity configurations created for these when you install the sample data.

| Entity Name | Message           | Description                                                                                 |
| ----------- | ----------------- | ------------------------------------------------------------------------------------------- |
| Lead        | Qualifylead       | This message is triggered when a lead is qualified.                                         |
| Opportunity | Win               | It is triggered when an opportunity is closed as Won.                                       |
| Quote       | Close             | Triggered when the quote is closed.                                                         |
| Quote       | Win               | It is triggered when the quote is won (Post clicking ‘Create Order’).                       |
| Incident    | Close             | This is triggered when an Incident is closed as Resolved.                                   |
| List        | AddListMembers    | This is triggered when a new member is added to a Static Marketing List.                    |
| Email       | Send              | This is triggered once an email is sent.                                                    |
| Application | loginlogout       | To track user log-in & log-out details.                                                     |
| Case        | \*checkincheckout | To keep track of user Check-in & Check-out activities details in particular Entity records. |

{% hint style="info" %}
**Note: 'checkincheckout' is applicable for OOB and custom entities – Lead, Opportunity, Quote, etc.**&#x20;
{% endhint %}

![](/files/-MQocJ_vRDkMIZuveGfF)

#### Example for Entity Tracking

* First, enable tracking for the following entities:&#x20;
  * **For Account:** Set **‘Create’** to period **‘Daily’**&#x20;
  * **For Contact:** Set **‘Update’** to **‘Weekly’**&#x20;
  * **For Lead:** Set **‘Assign’** to **‘Monthly’**

![](/files/-MQocS77TwnRk2yn8tyq)

* Upon Save, you will be notified that the Tracking has been enabled/disabled for selected entities.

![](/files/-MQocZJRdFR8my20Eitz)

* You can verify the configurations by navigating to the Entity Configuration section of User Adoption Monitor.

![](/files/-MQocds9GvyAABbFLhjp)

{% hint style="info" %}
**Note: Through the User Adoption Tracking screen, you can only configure to monitor CRUD operations performed on entities. To monitor other actions performed by the user on the entities you need to create the User Adoption Entity Configuration Record manually.**
{% endhint %}

{% 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/user-adoption-monitor/configuration/setting-up-other-messages/special-messages.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.
