Switch from ticket.conversations to ticket.comments
Why should I switch from ticket.conversations to ticket.comments?
Switching from ticket.conversations to ticket.comments is necessary because ticket.conversations is being deprecated. The ticket.comments property is a supported and documented feature that provides the same functionality as ticket.conversations.
By using ticket.comments, you ensure that your application remains functional and compliant with Zendesk's current API standards. This change is crucial for maintaining the stability and reliability of your integrations with Zendesk.
More related questions
What is happening to the Zendesk ticket.conversations property?
Zendesk is deprecating the ticket.conversations property. This property, which is part of the Zendesk Apps framework’s Support API, is an unsupported and undocumented feature that will no longer be available after July 1st, 2020. Instead,…
How can I update my app to use ticket.comments instead of ticket.conversations?
To update your app, replace any instances of ticket.conversations with ticket.comments in your code. This change is necessary because ticket.conversations is being deprecated and will no longer be supported. Ensure that your app is thoroughly…
What should I do if I encounter issues after switching to ticket.comments?
If you experience issues after switching to ticket.comments, it's recommended to contact Zendesk Support. They can provide guidance and help troubleshoot any problems you may encounter. In the meantime, ensure that your code is correctly…
When is the deprecation date for ticket.conversations?
The deprecation date for the ticket.conversations property was July 1st, 2020. After this date, the property is no longer supported or available for use in the Zendesk Apps framework’s Support API. Developers should have transitioned to using 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.
