Mounika Sanikommu

Zendesk se complace en anunciar la disponibilidad general de los estados de ticket personalizados basados en formularios. Con los estados de ticket basados en formularios, se puede definir qué estados de ticket aparecerán en ciertos formularios de ticket.

Este anuncio incluye los siguientes temas:

• ¿Qué va a cambiar?
• ¿Por qué Zendesk va a hacer este cambio?
• ¿Qué debo hacer?

¿Qué va a cambiar?

Estamos ampliando la funcionalidad de los estados de ticket personalizados mediante la introducción de estados de ticket personalizados basados en formularios.

Los administradores ahora pueden definir qué estados de ticket deben aparecer en ciertos formularios de ticket. Cuando se vinculan estados de ticket a formularios, se aplican automáticamente al formulario especificado cada vez que se usa.

Los estados de tickets basados en formularios mejoran la flexibilidad porque permiten adaptar los flujos de trabajo de gestión de tickets al contexto específico o al tipo de consulta, lo que garantiza que los agentes tengan a su disposición los estados más pertinentes. Los agentes solo ven los estados pertinentes al formulario de ticket en el que están trabajando.

Por ejemplo, si tiene un formulario de ticket para “Informe de error”, podría definir estados personalizados como “En investigación” o “En espera de corrección”. Estos estados están disponibles automáticamente cada vez que un agente selecciona el formulario asociado.

¿Por qué Zendesk va a hacer este cambio?

Estamos haciendo este cambio en respuesta a sus comentarios de que la falta de estados de tickets dinámicos y basados en formularios creaba desafíos para los agentes. Los agentes a menudo tenían que navegar a través de estados irrelevantes o seleccionar manualmente las opciones apropiadas, lo que ralentizaba el manejo de los tickets y aumentaba la probabilidad de errores.

Con este cambio, ahora tiene la flexibilidad de personalizar qué estados de ticket se asocian con ciertos formularios. Esto garantiza que los agentes solo vean los estados más relevantes en el contexto correcto y, en última instancia, respalda los flujos de trabajo de soporte cada vez más diversos y complejos.

¿Qué debo hacer?

Esta función está disponible automáticamente. Consulte Acerca de los estados de ticket de formulario si desea más información.

Si tiene comentarios o preguntas relacionadas con este anuncio, visite el foro de la comunidad donde recopilamos y administramos los comentarios de los clientes sobre los productos. Si desea asistencia general con sus productos Zendesk, contacte a Atención al cliente de Zendesk.

We're excited to announce the expansion of our beta program for form-based custom ticket statuses! Due to the positive feedback and success we've seen so far, we're extending this feature to a select group of additional customers.

This enhancement allows you to tailor ticket statuses to better fit your workflow, providing more flexibility and improving overall efficiency. If you're interested in participating in this expanded beta, please fill out this form. Your feedback is invaluable in helping us refine and perfect this feature before its general release.

Thank you for your continued support and collaboration!

We are writing to inform you about an important update to the Form Ticket Statuses Beta feature. These changes are designed to improve your experience and streamline your workflows. We appreciate your participation in the beta and your valuable feedback, which has guided us in enhancing the experience. Please read the following information carefully to understand the changes and any actions required on your part.

Previous Behavior:

• Previously, forms with no statuses associated would show all statuses in the Ticket UI, but this proved confusing and restrictive based on your feedback.

New Behavior:

• We executed a one-time conversion for any forms that had no custom statuses selected (and therefore all statuses selected) in order to maintain your current functionality.
• We will create associations for all default statuses only for forms with no existing associations.
• Default statuses will always be selected on all forms.
• When a new custom status is created, it will not be added to any existing forms and must be configured on each form.
• We are currently working on an enhancement to the custom status creation workflow that allows you to associate a new status to all desired forms.
• The status picker will now show only default statuses for forms with no associations.
• Existing associations will remain unchanged.

What You Need to Do:

• Update Form Statuses: Please review and update your form status associations as needed to ensure they reflect your desired configurations.

When will the enhancement be available:

• The enhancement is scheduled to be available by the end of next week.

 As always if you have any questions or concerns please post them in this community, your feedback has already been invaluable in improving this beta and I really appreciate everyone that has chimed in thus far.

Hey everyone, thank you for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.

This is a great feature request and I have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community. 

Hey everyone, thank you for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.

This is a great feature request and I have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community. 

Hey everyone, thank you for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.

This is a great feature request and I have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community. 

Hey Brandon, thank you for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.

We wanted to let you know that at this time we are not able to commit to building this feature. We understand this may be frustrating but wanted to ensure we closed this loop to remain transparent.

Hey everyone, thank you for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.

This is great feedback and I have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community. 

Hey CJ Johnson, thank you for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.

We wanted to let you know that at this time we are not able to commit to building this feature. We understand this may be frustrating but wanted to ensure we closed this loop to remain transparent.

Thank you all for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.

This is a great feature request and I have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community.