> For the complete documentation index, see [llms.txt](https://features.scnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.scnd.com/v2.0/dashboards/messages-dashboard.md).

# Messages dashboard

{% hint style="info" %} <mark style="color:blue;">Path: Dashboard > Messages</mark>
{% endhint %}

* [Definition](#id-1.14.x-messagesdashboard-definition)
* [Create a message](#id-1.14.x-messagesdashboard-createamessage)
  * [Thread linked to a booking](#id-1.14.x-messagesdashboard-threadlinkedtoabooking)
  * [Thread not linked to a booking](#id-1.14.x-messagesdashboard-threadnotlinkedtoabooking)
* [Read a message](#id-1.14.x-messagesdashboard-readamessage)
  * [Threads list](#id-1.14.x-messagesdashboard-threadslist)
  * [Threads detail](#id-1.14.x-messagesdashboard-threadsdetail)
* [Update a message](#id-1.14.x-messagesdashboard-updateamessage)
* [Delete a message](#id-1.14.x-messagesdashboard-deleteamessage)
* [Related resources](#id-1.14.x-messagesdashboard-relatedresources)

## Definition <a href="#id-1.14.x-messagesdashboard-definition" id="id-1.14.x-messagesdashboard-definition"></a>

Messages can be sent through the platform in given circumstances: when performing a booking, when browsing a listing page, or from a public profile page.

A message is always sent between two users, usually an offeror and an asker (this varies according to the platform’s configuration). When a message is first sent, a dedicated thread is created and allows users to follow their exchanges. There are 2 types of threads:

* Thread linked to a booking
* Thread not linked to a booking

<mark style="color:red;background-color:yellow;">WHO CAN USE THIS FEATURE?</mark>

**Switch users:** All logged-in users

**Non-Switch users:** All logged-in offerors

**Non-Switch users:** All logged-in askers

## Create a message <a href="#id-1.14.x-messagesdashboard-createamessage" id="id-1.14.x-messagesdashboard-createamessage"></a>

### Thread linked to a booking <a href="#id-1.14.x-messagesdashboard-threadlinkedtoabooking" id="id-1.14.x-messagesdashboard-threadlinkedtoabooking"></a>

A thread is automatically created upon each booking request. The offeror receiving the request can either directly accept the booking or decide to first discuss with the asker.

### Thread not linked to a booking <a href="#id-1.14.x-messagesdashboard-threadnotlinkedtoabooking" id="id-1.14.x-messagesdashboard-threadnotlinkedtoabooking"></a>

A thread is automatically created when a message is sent from the contact button available on each listing page or profile page.

## Read a message <a href="#id-1.14.x-messagesdashboard-readamessage" id="id-1.14.x-messagesdashboard-readamessage"></a>

The messages dashboard displays all messages in a date organized threads.

### Threads list <a href="#id-1.14.x-messagesdashboard-threadslist" id="id-1.14.x-messagesdashboard-threadslist"></a>

Users can search through their messaging threads via the in-built keywords search bar ( figure 1). A thread is displayed in the search results should it contain at least one iteration of the searched word.

<figure><img src="/files/dE5UWJgzpngwDa87s69d" alt=""><figcaption><p>figure 1</p></figcaption></figure>

Each messaging thread is displayed as a thread block (figure 2.2) displaying:

* The recipient user and his rating
* If applicable, the listing’s title
* The message sent

<figure><img src="/files/9KzD1JJQ2AIvklIer1gZ" alt=""><figcaption><p>figure 2.1</p></figcaption></figure>

An intuitive “reverse” arrow icon lets users respond quickly to a messaging thread. This icon opens a pop-up message box (figure 2.2) in which the user can write his message as well as attach files via the paper clip icon.

<figure><img src="/files/QzP1Fqg0BM6oRQmmllHa" alt=""><figcaption><p>figure 2.2</p></figcaption></figure>

Clicking the discussion bubble icon redirects the user to the detailed view of the messaging thread.

{% hint style="info" %} <mark style="color:blue;">Path: Dashbaord > Messages > Discuss with…</mark>
{% endhint %}

### Threads detail <a href="#id-1.14.x-messagesdashboard-threadsdetail" id="id-1.14.x-messagesdashboard-threadsdetail"></a>

Entering a thread’s detailed view gives quick access to related information.

The “Access listing” button (figure 3.1) located at the top of the thread block redirects the user to the related listing (if applicable).

<figure><img src="/files/7h1VZIv9BOcuojFvVZlY" alt=""><figcaption><p>figure 3.1</p></figcaption></figure>

The “Access booking” button (figure 3.2) redirects the user to the related booking (if applicable).

<figure><img src="/files/n5Vdkg3zHjvZxfAk9keo" alt=""><figcaption><p>figure 3.2</p></figcaption></figure>

The “Access profile” button (figure 3.3) redirects the user to the related recipient user’s profile page.

<figure><img src="/files/dyU3zJxzR7N6hmEX03qn" alt=""><figcaption><p>figure 3.3</p></figcaption></figure>

Clicking the recipient user’s avatar or name in a messaging thread also redirects the user to their profile page (figure 3.4).

<figure><img src="/files/kPagmrbtkEMdRmWFlJd7" alt=""><figcaption><p>figure 3.4</p></figcaption></figure>

In the main conversation body, messages are displayed in a staggered fashion according to who is sending the message (figure 4). Each message indicates the sender, the message, and the date.

<figure><img src="/files/wuVby4ZRvJnDOvcbfCRb" alt=""><figcaption><p>figure 4</p></figcaption></figure>

Users can write a message and attach a file in the dedicated field located at the bottom of the thread (figure 5).

<figure><img src="/files/nhHCzD5QhHzgGobsfEo3" alt=""><figcaption><p>figure 5</p></figcaption></figure>

## Update a message <a href="#id-1.14.x-messagesdashboard-updateamessage" id="id-1.14.x-messagesdashboard-updateamessage"></a>

Users cannot update sent or received messages. Authorized administrators can update messages through the SBO for moderation purposes. See: [Users messages management](/v2.0/superadmin/users/users-messages-management.md)

## Delete a message <a href="#id-1.14.x-messagesdashboard-deleteamessage" id="id-1.14.x-messagesdashboard-deleteamessage"></a>

Users cannot delete sent or received messages. Authorized administrators can delete messages through the SBO for moderation purposes. See: [Users messages management](/v2.0/superadmin/users/users-messages-management.md)

## Related resources <a href="#id-1.14.x-messagesdashboard-relatedresources" id="id-1.14.x-messagesdashboard-relatedresources"></a>

**SBO :**

* [Users messages management](/v2.0/superadmin/users/users-messages-management.md)

**Front:**

* [Profile page (Time-Based) - Profile block](https://features.scnd.com/v2.0/dashboards/pages/KPk6z3TZBXkifzLriQ6o#id-1.14.x-profilepage-basicsolution-profileblock)
* [Listing pages](broken://pages/pAQKrHdWV6KoNY37tg9k)
* [Booking requests](broken://pages/PhwbGsEwTW84AuPMArSu)
* [Quote requests (Quote feature)](/v2.0/front-office/quote-requests-quote.md)
* [Bid proposals (RFP rendering type)](/v2.0/front-office/rendering-types/uncommoditized-rendering-types/request-for-proposal-rfp/bid-proposals-rfp.md)


---

# 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://features.scnd.com/v2.0/dashboards/messages-dashboard.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.