Skip to main content
New Participant
March 18, 2025
4. Future Consideration

Prevent Duplicate Tickets by Disabling Double Click

  • March 18, 2025
  • 13 replies
  • 204 views

Sometimes, while creating an incident, users accidentally multi-click the "Open a ticket " button, resulting in multiple duplicate tickets being generated. To prevent this, can we implement a functionality that disables the button after the first click or prevents multiple submissions? This would help avoid duplicate ticket creation.

 

13 replies

New Participant
April 16, 2025

Hi! I am having this issue as well!

rraj
Community Manager
April 17, 2025

Hi ​@Ajay Chikane ​@brandon.ridberg We will get back to you shortly on this!

rraj
Community Manager
April 17, 2025

Could you please reproduce this issue for us and share the conversation ID for your example? You can get this ID from the reference popup, which can be accessed by clicking on the ℹemoji underneath the bot’s response. Thanks!

New Participant
April 17, 2025

Hi Raj,

Please find the conversation ID below where the duplicate ticket issue was reproduced

Conversation ID: Zbd3cN67kdGA

 

New Participant
April 17, 2025

Hi Raj!

Thank you for looking into this. This is just in a month and these are only the duplicated ticket clicked on back to back in the conference ID. There are many more but this are the most obvious ones. 


-_htcQVkk2tS
4aqeUz4KrkWp
5dqhWLr4Znzp
5wrLIofrN7tI
6JxL3BFZ-_MJ
6qwMtpXyov9U
AjwO_PuinuZ8
C-NO4195OYHd
CwBp77uy1Jdc
DNDK5wb7to8c
G-Yxxaa5PgI5
HvTfJdv17myX
N_381-KrE7I9
PXfTt1upFqmu
QxtjPBn-ELoD
TgYywTJAYS7i
Xv5hvlVl9IuX
bpuKRJESPFIh
dYM4OTzpEXCo
do57iW1LXjrt
eRPePyuYWsYh
h0gukRCjcp_V
lws6aer1Zdrk
p-UWjrh23h0w
pbDdCaZVkUM_
r-TpgEKS1F4E
t_ZZ69QAHkGt
xNsHavX2B0mx

New Participant
April 24, 2025

We are also experiencing this issue on our side. We have also experienced this with Creator/Agent Studio requests.

New Participant
April 24, 2025

We are experiencing this issue on our Creator/Agent Studio requests.

rraj
Community Manager
April 29, 2025

Hi everyone. Thank you for adding your feedback. Currently, we do not block the button from being clicked more than once. We have made a note of this as a candidate item for the future roadmap and will look to prioritize it in the future. I am not able to share an ETA for this at this point, but it is on our backlog. 

cc ​@anaTyler 

Community Manager
June 6, 2025

Hey folks, 

I want to acknowledge this feedback and let you all know that our product team is evaluating this issue as a candidate for our H2 (Aug 2025-Jan 2026) roadmap. The specific issue mentioned here is not unique to the “File a ticket” button—it applies more broadly across all of our confirmation card experiences with buttons (e.g., “Talk to an agent,” “Approve,” “Yes”). Right now, when users make a selection, the confirmation card doesn’t reflect that action, which can lead to confusion about whether their input was received. We want our AI Assistant to be transparent and responsive. That means clearly showing when an action has been taken, so users aren’t left guessing whether their input went through. 

Please stay tuned for more updates as we work through our H2 planning exercise. We expect to share our H2 roadmap for AI Assistant by August 2025. 

Known Participant
June 12, 2025

@ioanna.tzanetou ​@pavithra.babu