Pesquisas recentes


Sem pesquisas recentes

Ryan Nally's Avatar

Ryan Nally

Entrou em 28 de dez. de 2023

·

Última atividade em 22 de jul. de 2024

Seguindo

0

Seguidores

0

Atividade total

9

Votos

0

Assinaturas

5

VISÃO GERAL DA ATIVIDADE

Atividade mais recente por Ryan Nally

Ryan Nally comentou,

ComentárioEnd users and organizations

How do I populate user fields from my BE? I'm using the users/create_or_update call and send a request body that has user_fields object but it doesn't seem to update these fields on the user profile and they come back null.  I then updated these fields on the user profile and now when I inspect that call I see that value reflected.  So it seems that the call I make reads the values from the user profile instead of populating them.  Please advise.

Exibir comentário · Publicado 22 de jul. de 2024 · Ryan Nally

0

Seguidores

0

Votos

0

Comentários


Ryan Nally comentou,

ComentárioWeb Widget documentation

Hey Thomas, What do mean by adding that code snippet to the Help Centers's head.  How are you doing this?  Form what I'm seeing, my company has setup and managed the help center all from the zendesk UI.  It is completely separate from our application's codebase. 

Exibir comentário · Publicado 18 de mar. de 2024 · Ryan Nally

0

Seguidores

0

Votos

0

Comentários


Ryan Nally comentou,

ComentárioUsing legacy AI agent functionality

In our app we've implemented a JWT using signing key and the login method outline in the sdk doc.  I can see this call returning with a 200 status. Yet in our chatbot flow the Authenticated Status is not equating to true.  Any suggestions on why this might be the case?

Exibir comentário · Publicado 05 de mar. de 2024 · Ryan Nally

0

Seguidores

0

Votos

0

Comentários


Ryan Nally comentou,

ComentárioMigrating to messaging

I'm running into a caching issue when enabling Messenger. Here is the flow: Classic web widget is being used. the zendesk snippet is cached.  I enable Messenger and merge code to use the Messenger API. A user goes on to my app but the snippet is pulled from the cache and this cached version used the classic web widget not the messenger.  My console complains about trying to use functions that don't exist (ie. Messenger functions against the classic web widget).  This causes issues around authenticating end users, etc.

I've tried busting the cache by appending a timestamp as a query param to the Zendesk snippet but this doesn't work.  

For those who have made the switch from classic web-widget to Messenger how have you handled this issue?

Exibir comentário · Publicado 28 de dez. de 2023 · Ryan Nally

0

Seguidores

0

Votos

0

Comentários