실시간 채팅 및 웹 위젯(클래식) 사용 시 메시징용 웹 위젯 설정하기



image avatar

Aimee Spanier

Zendesk Documentation Team

2025년 4월 17일에 편집됨


0

0

댓글 30개

I have been using the classic Web Widget.

I haven't done any changes but since today, I'm getting this error.

Method webWidget.helpCenter:setSuggestions does not exist.

What should I do?

0


Hi, 

Any feedback please?

0


Hi, I am trying to do this: 

1. Introduce conversational bots to the current mobile SDK classic we are using 

Referencing: https://support.zendesk.com/hc/en-us/articles/6774958972442-Zendesk-SDK-for-Unity-with-messaging-is-now-available

From the different articles that I read including this one, can you help me confirm if the below understanding is correct: 

a. To enable conversational bots in mobile SDK to be set up, we need to convert to SDK unity.  
b. And also enable messaging.  
c. If we are on the Professional plan, there should not be additional costs for this conversion? 

If we are not able to address it here, can you kindly initiate a ticket and channel it to the right department to assist me as I have a bunch of follow up questions too. 

Thank you.

0


Is it possible to send a automatic message from the client side using Zendesk messenger?

0


Hi, I have the same question as James Skene and wonder if there is any news on this in the meantime. Can urls be passed automatically in the new web widget?

0


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?

0


Thanks Gab

I did explore that but from a user perspective, I preferred having the form available in the Web Widget (Classic) and also for my support team, capturing the url automatically is such a good feature that I will stick to the Web Widget (Classic) for now. 

0


Hi James, 
 
You can use the bot builder to create answers for your conversation bots, giving your customers the opportunity to self-serve their support issues before connecting with agents. If you want to include ticket forms/fields where you ask more details from end users, with the use of the bot builder, the Ask for details step can be added anywhere in your flow, which will allow you to choose a custom field you've created in your Zendesk instance. 
 
Here are some articles that might help: 

0


Hi 

In Web Widget (Classic) I have the ability to add a ticket form within the chat which when used on an external site such as our software platform, includes the url from where the form was submitted from. Is this available in the updated Web Widget (Messaging)? 

We don't always get url's from customers so having the ability to capture that url at the point they raise an issue is very useful.

Thanks

0


Hi Lucy,
 
Switching/turning on Messaging with Flow Bot would have an impact much more related to the different functionalities that would be offered compared to the Classic Web Widget (with Live Chat).
 
We would suggest reading this article: Messaging vs. live chat: Which is right for you?
 
I hope that helps. Thank you!
 

0


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