Require log in for ticket submission via the Web Widget

3 댓글

  • Kay
    Community Moderator

    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.

    1. Suppress the ticket form in the web widget whenever a user is not authenticated
    2. Suppress all other channels whenever a user is authenticated
    3. 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.

  • Charlie

    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.

  • Raman Kalia

    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.


댓글을 남기려면 로그인하세요.

Zendesk 제공