John Ritterbush

Has anyone found any solutions to this problem? I am running into a similar issue. I am using a custom launcher as well which means the click to open chat may happen at the same time as the JWT/loginUser step. If I call open and loginUser too close together with the custom launcher, the chat opens and immediately closes so they can't get in. If I had a way to at least check if they are already authenticated to the Zendesk messenger, I can skip the loginUser and just open the chat at least. I don't think I can even do that though.

I'm also curious is there a Zendesk log of when these login attempts fail? I want to be able to log errors when they happen, but even if we can audit a log for an id or some information to pinpoint which users had problems accessing chat we can at least fix them in our database.

Is there any way to change the title on the contactOptions view? I do not see anything documented and only see screenshots with "Help" as the text.

Is there a way to control which view to open in the widget? Basically we would like for a way to use external links in our app to open different views directly. So a "Live Chat" button that opens directly to the Widget's chat view and a "Contact Us" that opens to the Contact Options view. 

I found some hacky solutions using the `suppress` option but it feels messy. It would be great if the `zE('webWidget', 'show')` call took a 3rd param that included the view to show. There is already a get display, maybe even a set display option that could be called prior to show?

Any other tips on direct linking to a display in the Zendesk Widget using the API would be helpful. Thanks.

Jimmy you might try setting the helpCenter suppress option:

helpCenter: {suppress: true}

With contactOptions set and that suppress on, I was able to get the widget to open with the ticket and chat buttons as the first thing, no help center.