Allow Editing of Custom CSAT Link Expiration Period | Community
Skip to main content
Idea Submitted

Allow Editing of Custom CSAT Link Expiration Period

Related products:Ticketing system (Support)
  • December 10, 2025
  • 2 replies
  • 0 views

Gabriela11

Hello Zendesk Community,

We are writing to request a crucial feature for better management of our CSAT metrics and internal reporting: the ability to customize the expiration date of the custom CSAT survey link.

We appreciate that the expiration period was recently extended to 28 days. However, having this long, fixed period without the option to set our own timeframe is significantly disrupting our internal controls and reporting cycles.

 

 

🎯 The Request:

We urgently request that Zendesk allow customers to edit and configure the number of days the custom CSAT link remains active after the ticket is solved/closed.

 

📉 Why the 28-Day Period is Problematic:

A 28-day validity period drastically alters our feedback collection and reporting alignment:

  • Reporting Distortion: Our reporting cycles (e.g., weekly, monthly) are much shorter. Responses coming in up to 28 days later skew the metrics for the period when the service interaction actually occurred, making it harder to link performance directly to agent action.
  • Relevance: Feedback is most valuable immediately after service. Extended periods dilute the relevance and accuracy of the customer’s memory of the interaction.
  • Operational Alignment: We need the flexibility to align the CSAT eligibility window with our internal definition of a closed cycle, which is often much shorter than four weeks.


In summary, we need to choose the expiration period (e.g., 7 days, 14 days) to ensure our CSAT data is timely, accurate, and aligned with our internal business metrics.

Thank you for considering this critical functionality.

2 replies

Emily31
  • December 11, 2025
Hi Gabriela! Thank you for taking the time to provide us with your feedback. This has been logged for our PM team to review. For others who may be interested in this feature request, please add your support by upvoting this post and/or adding your use case to the comments below. Thank you again!
 

  • March 16, 2026

Essa personalização é extremamente importante para a operação.
 

Atualmente, a única garantia que temos sobre a consolidação final das informações de um ticket ocorre após o status “Closed”. No entanto, como a pesquisa de satisfação pode ser respondida em até 28 dias, isso impacta diretamente na finalização e confiabilidade dos dados do atendimento.
 

Por esse motivo, é fundamental que exista a opção de desativar ou reduzir esse prazo, garantindo maior autonomia para que cada operação configure o período mais adequado à sua realidade.
 

Também é importante considerar que o atendimento hoje não ocorre apenas por e-mail. Grande parte do volume está concentrada em canais de mensagens, onde ciclos de resposta são muito mais rápidos. Nesse contexto, um prazo de 28 dias para registro de CSAT acaba gerando impactos operacionais e analíticos relevantes.