Live Conversation Authentication

Modified on Thu, 5 Sep at 1:40 PM

Live Conversation Authentication


This section of the user guide is focused on configuring live assistant authentication. To help you navigate the article we have broken it down into the following sections:

Live Conversation Authentication Overview

Live conversation authentication allows customers to choose on an office-by-office basis whether or not a live conversation participant needs to authenticate (log in using their SSO credentials) at any time during the conversation. 


Prior to configuring the live conversation authentication settings, you will first need to set up your single sign-on authenticator via the admin portal on the Connectors>Authentication Providers page.  

For information on how to set up a new authentication provider, please review the Adding An Authentication Provider article.


After you have set up your authentication provider(s), you will need to configure the Behavior Settings tab. 


Configuring the Live Conversation Authentication Settings

  1. Under the Virtual Assistant section, select the Behavior Settings tab.

  2. There are three steps to enabling the live conversation authentication feature.

3. In the Live Conversation Authentication dropdown, select On.


Note: On the Office tab, in the Live Conversation Authentication dropdown, you will have the additional option of Default/No Office. Selecting this option will refer to the settings on the Default/No Office tab.


4. In the SSO Authentication Provider field, from the dropdown select your SSO authentication provider that was set up on the Authentication Providers page.


5. Set the Display Student ID toggle as either Off or On. If the toggle is on, the Student ID will display in the live assistant Active Conversation Details pane. 

Virtual Assistant user experience

If live conversation authentication has been configured, the live conversation participant must agree to log in to be added to the queue. Live conversation participants will also be required to log in to leave a message as well (i.e. fill out the contact form). 


The virtual assistant message displayed to the live conversation participant is slightly different if live conversation authentication is turned on: 

  • If a live assistant agent is available, the live conversation participant will receive the following message: “I have someone available now to chat. Would you like to log in to connect to them?"
  • If a live agent is not available, the live conversation participant message will depend on the communication opportunities settings.
    • If the communication opportunities settings are set to contact form, the live conversation participant will receive the following message: “Would you like to log in to leave a message?"
    • If the communication opportunities settings are set to custom response, the live conversation participant will receive the custom response configured in the communication opportunities section.


Live Conversation First will work the same as if the live conversation were initiated after engaging with the virtual assistant in that the live conversation participant is asked if they would like to log in to connect to a live agent. 


  • Once a live conversation participant chooses to authenticate (whether it’s to enter the live conversation queue or leave a message), they are automatically redirected to the SSO login site configured by the institution. 
  • Upon successfully logging in, they are automatically redirected back to the virtual assistant. 
  • If the live conversation participant is already logged into the SSO in the browser in which they are engaging with the virtual assistant, then they are not required to re-authenticate and will automatically be redirected back to the virtual assistant. 


Transferring to an office that requires live conversation authentication


If a live conversation participant is engaged in a live conversation with an office that does not require authentication and is transferred to an office that does require authentication, the live conversation participant will receive the following message: “You are being transferred to an office that requires you to log in to connect to an agent. Would you like to log in to continue?”. 


In the admin portal, the live agent is prevented from sending messages until the user successfully logs into the SSO.


  • If the live conversation participant is required to authenticate but is unsuccessful, they can start a new conversation in a different window or clear the conversation to start a new one. 
  • If the live conversation participant selects the back button, they will eventually be returned to the secure virtual assistant and will no longer be able to engage with the virtual assistant unless they perform one of the options just mentioned. 
  • If the live conversation participant selects to log in but does not attempt to log in (for example, they changed their mind and do not wish to log in), and then select the “back” button, they are returned to the virtual assistant and can engage with the virtual assistant.


Using Live Assistant Authentication as a Live Agent

At any time during a live conversation, the agent can prompt a live conversation participant to authenticate via SSO by selecting the new prompt authentication button in the conversation panel tools.




If multiple authentication providers are configured, the live agent must select which one the live conversation participant should use. If only one provider is set up, no selection is needed.



The student will receive a message saying, "I need to access your personal information. Would you like to log in to continue?"


Once the live conversation participant logs in, the agent is notified. If the participant has already authenticated, the agent will receive a message stating this when they prompt for authentication. 


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article