Require log in for ticket submission via the Web Widget
Our help center allows our visitors to view almost all the content without logging in. However, when the user wishes to submit a ticket from the help center they must log in with their email and password. We have been looking into the Web Widget for our help center but the widget will allow any user to submit a ticket without being prompted for their credentials.
We will be blocking the email channel in order to force users to the help center. We identify users via their email in other systems that integrate with Zendesk. The web widget allowing anonymous users to submit tickets defeats the purpose of the integrations we already have in place and our future plans to block ticket submission via email.
I propose another option in the web widget config that would force the user to log in if/when they wish to submit a ticket while still allowing them to access unrestricted content through the widget.
Agreed, so +1. This would be a nice additional option.
Until then, there is a way the achieve the same more or less.
Here's how that might work.
- Suppress the ticket form in the web widget whenever a user is not authenticated
- Suppress all other channels whenever a user is authenticated
- Add a link Didn't find your answer? Login here to create a ticket. to the end of each article (soon with Dynamic content this should be even easier).
It's not the picture perfect, but still might give you what you need in the meantime.
From my research, the web widget is not very useful even if you do follow Kay's advice and suppress it for users who are not logged in. We've spent a few weeks trying to get it working and will likely give up, due to its inability to work seamlessly. It has these issues:
1) Any submission from the web widget will show up with a warning saying "...was not signed in when this ticket was submitted" when the ticket is viewed by an agent.
2) The web widget doesn't allow you to remove the 'Email' field, so a user can edit that value to whatever they want, so there is no way for you to know whether the person who submitted the ticket is who they say they are. You can disable the ability edit that field (but it still looks like a field you can edit, which gives a bad user experience), but you cannot hide it.
3) The chat component of the web widget doesn't let you remove either the 'Name' or the 'Email', so is even worse.
It seems to me that not much thought was put into the design of the web widget to allow it to properly function when placed in a customer's own App.
Web widget we have can search Zendesk articles based on credentials of the user who logged into our website. But it fails miserably in carrying the user's credentials when article is expanded from the widget as It asks the user to login again. The transfer should have been smooth.
Anyone got success in finding a solution to it.
Does anyone have a solution for this yet?
Our desired solution for our support desk is that all ticket submissions require a sign in, sign in is via an SSO / JWT authentication method from our custom provider, and the widget will prompt for sign in if the only resolution for a query would be for the user to raise a new ticket..
Thank you for the great question and feedback on a way to leverage an SSO feature with the widget. Unfortunately that is not a possible option, but I will certainly mark this thread for product review so our team might be able to roadmap that for the future.
Are there any updates to this?
Any updates on this, perhaps?
Please sign in to leave a comment.