# Introduction
## Why use authenticated messaging?
Authenticating your visitors increases the security of the information as the customer’s identity is verified.
Now, as an iAdvize business, you will be able to provide a messaging experience with secured authentication to your customers.
iAdvize authenticated messaging will allow your visitors to feel more confident on sharing sensitive information during their messaging experience and access to past conversations. They will benefit from a better conversation continuity while they are logged-in across multiple devices, browsers, and channels. Respondents will also be able to know that the conversation is secured while they are chatting with your customers.
## Key benefits
* Secured and trusted conversation for visitors and respondents
* Browsing multiple domains: if your brand offers browsing across different websites, domains, and even your mobile app, authenticating the visitor will make them a single visitor across all domains, with the same continuity of conversation and history
* Cross-device experience: the visitor is viewed as the same person as long as they log-in before or during their conversation for a seamless messaging experience on multiple devices
## **How to set up authenticated messaging on your website or on your mobile App?**
* **Step 1**: your developers will first need to generate a public key and provide it to your iAdvize contact so that we can activate Authenticated Messaging. See [here](https://docs.iadvize.dev/~/changes/39J6v2tWi3Ms7Me1qEFP/technologies/authenticated-messaging/web-backend-implementation/signature-and-encryption-detailed-process#sign-and-encrypt) how to generate a public key.
* **Step 2**: after activation, your developers will need to follow frontend ([web](https://docs.iadvize.dev/~/changes/39J6v2tWi3Ms7Me1qEFP/technologies/authenticated-messaging/web-client-side-implementation) and [mobile](https://developers.iadvize.com/documentation/mobile-sdk#%E2%9A%99%EF%B8%8F-setting-up-the-sdk)) and [backend](https://docs.iadvize.dev/~/changes/39J6v2tWi3Ms7Me1qEFP/technologies/authenticated-messaging/web-backend-implementation). Once this step is completed, you will need to get in touch with your iAdvize contact to finalize the feature activation before launch.
## Authenticated Messaging experience
Once an anonymous visitor has logged in during the conversation, they will get the information that they have successfully logged in, and respondents will be able to see that the conversation is secured.
* Visitors will then see a dedicated banner
 
and the following information when hovering the mouse over the chatbox\
\\
* Advisors will see a lock icon
Respondents can know if the conversation is secured if they see the lock icon near the visitor avatar on their desk.
## Limitations
* Visitor profile: the visitor profile is enriched with their unique ID (userId claim)\
with the option to add visitorData claim to the JWT (more info [here](https://docs.iadvize.dev/use-cases/authenticated-messaging/web-backend-implementation/important-information-and-recommendations#sending-visitor-data-in-the-jwt-token)).
* Channels: chat, video, and call only. This is not compatible with 3rd parties channels.
---
# Agent Instructions: 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:
```
GET https://docs.iadvize.dev/use-cases/visitor-experience/authenticated-messaging/introduction.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.