> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/products/crm-automation/communication-channels/communication-properties-for-user-interaction.md).

# Communication properties for user interaction

This document describes the different communication properties that Smartico supports to detect user interaction to use that info for improving engagement and segmentation.

Understanding how users engage with different communication channels is essential for optimizing outreach strategies, improving responsiveness, and personalizing experiences. The **Communication Properties** outlined in this documentation serve as key indicators of user interaction across interfaces such as Inbox, Email, SMS, Push notifications, and broader General interactions.

These properties are designed to help operators monitor and respond to engagement signals using three primary event markers:

* **Last Clicked Date** – when the user last actively engaged with a communication.
* **Last Open Date** – the most recent time a user accessed a message or notification.
* **Last Send Date** – the timestamp of the latest communication dispatched to the user.

Together, these signals form a behavioral fingerprint of user interaction, enabling smarter decision-making, from re-targeting efforts to segment-based automation. Whether you're triggering workflows, assessing engagement trends, or refining message timing, these properties provide a foundation for interpreting user intent and responsiveness.

The following tables detail these properties per channel, outlining their structure, intended use, and operational impact.

***

### Inbox

<table><thead><tr><th width="328">Property tag</th><th width="141">Type</th><th>Note</th></tr></thead><tbody><tr><td>{{state.inbox_last_clicked_date}}</td><td>Date &#x26; Time</td><td>Timestamp of user's most recent Inbox Click</td></tr><tr><td>{{state.inbox_last_open_date}}</td><td>Date &#x26; Time</td><td>Timestamp when Inbox impression was registered</td></tr><tr><td>{{state.last_marketing_inbox_sent_date}}</td><td>Date &#x26; Time</td><td>Date/time when last Inbox was sent <em>(only campaigns of category "Marketing" are counted)</em></td></tr></tbody></table>

### Email

<table><thead><tr><th width="328">Property tag</th><th width="141">Type</th><th>Note</th></tr></thead><tbody><tr><td>{{state.mail_last_clicked_date}}</td><td>Date &#x26; Time</td><td>Timestamp when user clicked last time on any link in the mail sent by Smartico</td></tr><tr><td>{{state.mail_last_open_date}}</td><td>Date &#x26; Time</td><td>Timestamp when user opened last time any mail sent by Smartico</td></tr><tr><td>{{state.last_marketing_email_sent_date}}</td><td>Date &#x26; Time</td><td>Date/time when last Email was sent <em>(only campaigns of category "Marketing" are counted)</em></td></tr></tbody></table>

### SMS

<table><thead><tr><th width="328">Property tag</th><th width="141">Type</th><th>Note</th></tr></thead><tbody><tr><td>{{state.sms_last_clicked_date}}</td><td>Date &#x26; Time</td><td>Timestamp when user clicked last time any SMS sent by Smartico</td></tr><tr><td>{{state.last_marketing_sms_sent_date}}</td><td>Date &#x26; Time</td><td>Timestamp when last SMS was sent <em>(only campaigns of category "Marketing" are counted)</em></td></tr></tbody></table>

### Push

<table><thead><tr><th width="328">Property tag</th><th width="141">Type</th><th>Note</th></tr></thead><tbody><tr><td>{{state.push_last_clicked_date}}</td><td>Date &#x26; Time</td><td>Timestamp when user clicked last time on any link in the push notification sent by Smartico</td></tr><tr><td>{{state.push_last_open_date}}</td><td>Date &#x26; Time</td><td>Timestamp when user have seen last time any push notification sent by Smartico</td></tr><tr><td>{{state.last_marketing_push_sent_date}}</td><td>Date &#x26; Time</td><td>Date/time when last Push notification was sent <em>(only campaigns of category "Marketing" are counted)</em></td></tr></tbody></table>

### Viber, Telegram, and RCS

<table><thead><tr><th width="328">Property tag</th><th width="141">Type</th><th>Note</th></tr></thead><tbody><tr><td>{{state.vb_last_clicked_date}}</td><td>Date &#x26; Time</td><td>Timestamp when user clicked last time any Viber message sent by Smartico</td></tr><tr><td>{{state.vb_last_open_date}}</td><td>Date &#x26; Time</td><td>Timestamp when Viber message impression was registered</td></tr><tr><td>{{state.tg_last_clicked_date}}</td><td>Date &#x26; Time</td><td>Timestamp when user clicked last time any Telegram message sent by Smartico</td></tr><tr><td>{{state.rcs_last_clicked_date}}</td><td>Date &#x26; Time</td><td>Timestamp when user clicked last time any RCS message sent by Smartico</td></tr></tbody></table>

### Pop-up

<table><thead><tr><th width="328">Property tag</th><th width="141">Type</th><th>Note</th></tr></thead><tbody><tr><td>{{state.last_marketing_popup_sent_date}}</td><td>Date &#x26; Time</td><td>Date/time when last Popup was sent <em>(only campaigns of category "Marketing" are counted)</em></td></tr></tbody></table>

### General

<table><thead><tr><th width="328">Property tag</th><th width="141">Type</th><th>Note</th></tr></thead><tbody><tr><td>{{state.core_last_visit_date}}</td><td>Date &#x26; Time</td><td>The date/time when user clicked on any link in any type of communication sent to user <em>(except popups and inbox)</em></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.smartico.ai/welcome/products/crm-automation/communication-channels/communication-properties-for-user-interaction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.