Developer Platform
  • Home
  • Getting Started
    • General Information
    • Features Overview
    • Security
  • APPs
    • Public Apps
      • Shopify
      • Salesforce
      • Zendesk
      • Google Analytics
    • Build your App
      • Getting started
      • My Apps
      • App information
      • App Parameters
      • App Plugins
      • Add Webhooks
      • Submit your Apps
      • App security
      • Developer Policy
  • Use Cases
    • Copilots
      • Product Catalog sync through API
      • FAQ sync through API
    • Visitor experience
      • Integrating custom buttons into your site
      • Check availability before escalating to iAdvize
      • Authenticated Messaging
        • Introduction
        • Web client-side implementation
          • Authenticated Messaging overview
          • Brief timeline of the integration process
          • How to enable authenticated mode in the administration portal?
          • How to implement the customer authentication backend (token provider)?
          • How to authenticate with iAdvize in client's website?
          • How to deal with activation success or failure?
          • How to logout?
          • Compatibility with Mobile SDK
          • FAQ
        • Web backend implementation
          • Important information and recommendations
          • Signature and Encryption Detailed Process
          • Technical backend implementation
          • FAQ
      • Cross-domain Conversation Continuity
      • Customize replies with Markdown
    • Agent workspace
      • Custom App example and step-by-step tutorial
        • Get Started
        • Work with the Desk
        • Intent / Trigger
        • JWT
        • References
    • Administration
      • Users
        • SAML SSO Authentication - Implementation Guide
        • Create, update and delete users via API
        • Manage the availability of your users with the iAdvize API
        • Integrate the iAdvize conversation panel into an existing tool
    • Data & Analytics
      • Anonymize a conversation or visitor data
      • Create a custom dashboard
      • Find contact data using GraphQL
      • Retrieve conversations data
      • Retrieve messages exchanged within a conversation
  • Technologies
    • GraphQL API
      • Terminology
      • Reference
      • Authentication
      • Schema lifecycle
      • Error Management
      • Pagination
    • REST API (deprecated)
      • Statistic (deprecated)
      • Group (deprecated)
      • Call meeting (deprecated)
      • Operator (deprecated)
      • Skill (deprecated)
      • Transaction (deprecated)
      • Visitor (deprecated)
    • Webhooks
      • Reference
      • Guides
    • Desk events
      • Reference
    • Web & Mobile SDK
      • Javascript Web SDK
        • Reference
      • Javascript Callbacks
        • Reference
        • Guides
      • Mobile SDK
        • Fourme (latest)
        • Epoisses
        • Dauphin
        • Cantal
        • 🤝Support Policy
        • 🤔Frequently Asked Questions
    • Custom App
    • External Bot
      • Implementation
        • Configuration flow
        • Conversation flow
        • Conversation objects
      • Configuration
      • FAQ
      • Best practices
Powered by GitBook
On this page
  • Why use authenticated messaging?
  • Key benefits
  • How to set up authenticated messaging on your website or on your mobile App?
  • Authenticated Messaging experience
  • Limitations

Was this helpful?

  1. Use Cases
  2. Visitor experience
  3. Authenticated Messaging

Introduction

PreviousAuthenticated MessagingNextWeb client-side implementation

Last updated 1 year ago

Was this helpful?

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 how to generate a public key.

  • Step 2: after activation, your developers will need to follow frontend ( and ) and . 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

  • 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

  • Channels: chat, video, and call only. This is not compatible with 3rd parties channels.

and the following information when hovering the mouse over the chatbox

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
web
mobile
backend
here