Henderson Pinto

Hey again, I just noticed that the email is also missing from our tickets. This could be the reason why the Contextual Data can't query the right user. Any idea of why the email is not being propagated when the user is logged in. I have double checked with the backend engineers and the JWT used to authenticate the users all MUST include an email so the JWT is not missing it. 

I am also attaching the code we use to authenticate an user:

 

Hi Erica, 

1. We don't seem to have any errors while creating the ticket. However, ALL of our tickets are still missing contextual data since the Contextual Data App does not load.

Here is an example from yesterday (#280555)

This is another example with both a random name and missing contextual data (#279609):
 

We are facing an issue with the tickets created via the Messaging Web SDK, here is a summary of the issue with tickets missing contextual information:

1. There are some tickets created via the chat widget that correctly display the name for the authenticated user on the "Agent Workspace". However, on these tickets we are missing the email to be shown in the Zendesk Agent Workspace. I have checked and verified that the email is included in the JWT we use to authenticate against Zendesk, so I am wondering if this is an issue after we authenticate with Zendesk or if it is something we are missing.


2. There are other tickets (not sure about how many or what percentage of the newly created tickets fall in this category) that include a weird name such as this ticket and no email again.

Hey!

Thanks for such a cool feature, this is definitely a dealbreaker in our current migration from the competitor company.

However, I would like to also confirm all of the issues that Viachaslau is facing.  Especially the “archive folder” or being able to hide conversations that are solved would be extremely helpful!