Using chat:connected Callback in Web Widget (Classic)
Can I use the chat:connected callback for multiple commands in Web Widget (Classic)?
Thechat:connectedcallback in Web Widget (Classic) is best used for commands you only wish to execute once. This is ideal for initial setup tasks that should not be repeated every time the widget reconnects.
If you have commands that need to be executed multiple times, such as whenever a department's status changes, consider using thechat:departmentStatuscallback instead. This approach ensures that your widget's behavior is consistent and only executes commands when necessary.
More related questions
How can I modify the Web Widget (Classic) behavior using JavaScript APIs?
You can modify the Web Widget (Classic) behavior using JavaScript APIs by applying specific workflows at different times. Some workflows should be executed when a department's status changes, while others should be run when the widget first…
When should I apply widget settings in Web Widget (Classic) API workflows?
The timing of applying widget settings in Web Widget (Classic) API workflows is crucial. Some settings should be applied when a department's status changes, while others should be applied when the widget first connects or reconnects. For instance,…
How can I handle department status changes in Web Widget (Classic)?
Handling department status changes in Web Widget (Classic) can be managed using thechat:departmentStatuscallback. This allows you to apply specific settings based on the department's availability. For example, if a department named 'CRM' is…
Is it necessary to hide the Web Widget (Classic) on page load?
Hiding the Web Widget (Classic) on page load is not strictly necessary, but it can be part of your workflow if desired. The initial steps of hiding the widget and then showing it when an unread message appears can be omitted without affecting the…
Interested indeflectingover 70% of your Zendesk support tickets?
Zendesk Support Tickets
Zendesk Messaging (live chat)
Join1,000+ companies reducing their support costs and freeing up support agents for more important work
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
Reduce support costs.Spend more time on customer success.
