GHL Chat Widget - SSO User Context for Agency Usage
J
Jacob Radcliffe
We want the native GHL chat widget to be functional for agency usage as a support widget. It does not take in the SSO user context about the active user. This is such an easy win for highlevel!
Log In
J
Jenn Buckner
When a contact is logged into the Client Portal, the chat widget should already know who they are.
Right now it doesn’t. Members who are signed into our portal still get asked for their name, email and phone before they can chat. On a new device or browser, they have to enter it all again.
The portal knows who’s logged in, so the widget should too. Asking a paying member to identify themselves again feels broken and creates friction right when they’re reaching out for help.
What we need:
The widget automatically recognizes the logged-in portal contact, with no form
The chat attaches to that contact’s existing record and conversation in Conversations, so our team sees the full history
It works on any device or browser the member logs in from
It’s native in the Client Portal, or there’s a supported, documented way for developers to pass the contact ID to the widget
Support told us custom JavaScript isn’t supported, so right now there’s no official way to do this.
C
Clifford Paulick
I'm requiring they enter an email to start the chat, but that's cumbersome because the chat widget also requires their name... we already know their name and email :'(
#UX
E
Eric Uldall
There should, in general, be a way to link a user email/phone or even an contact id so that we can avoid creating new guest conversations and having to reconnect to contacts.