web-sdk not working with Conversation API
-
Hi Panos! Before I jump too far into this, it sounds like there are a few things going on that may be outside of our scope of support and I want to make sure that I'm understanding the underlying issue.
It sounds like the problem isn't with the Web SDK method functioning to send a message on behalf of a user, instead there is something that your server is looking for which is not present in that scenario. What methods are you using to send this data back and is there any debugging that has been done to see what the difference in these two events may be?
You had asked if the Web SDK is compatible with Chat Conversations, however I'm having a hard time seeing what their interaction would be in this scenario. Could you explain more about how these two tools are working together on your side?
Regarding Agent Workspaces and the Chat Conversations API...that's a tough question to answer., but a completely valid question! There are quite a few limitations with AW and we have not identified all of them at this time, so it is possible. That being said, my gut tells me that this should not have any affect on it, so let's place that on the back burner as a possible resolution for now.
-
Hi Greg,
Thanks for your prompt response.
I actually figured out there was a bug in our web-sdk implementation where we were using async functions, so it all works out now.
Unfortunately we just realized that examples similar to the Zendesk sample app (https://github.com/zendesk/zopim-chat-web-sdk-sample-app) don't provide code to render carousels, images, quick replies etc. Would you happen to know if there are any code samples for these that would work? or do we have to implement our own?
Please sign in to leave a comment.
2 Comments