Tagging and Hotkeys | Community
Skip to main content
Answered

Tagging and Hotkeys

  • August 12, 2026
  • 2 replies
  • 89 views

Have there been any updates or recent changes to the tagging/hotkeys product?

Previously, when adding multiple tags to a conversation, you could type a tag, press Enter, and remain in the tag window to immediately enter the next one. Since yesterday, it looks like pressing Enter after adding a tag kicks you out of the tag window instead.

This means users have to click back into the tag field before every new tag. If they don’t, the letters they type can trigger hotkeys instead, such as opening Reply, moving to the next ticket, or snoozing the conversation.

Was there a recent change to this behavior, or is this a known issue being worked on? See attached video.

I appreciate any insight into this!

Best answer by Adam Warden

Hi Louise!
 

I tried replicating the error you are having, but didn’t run into the same issue. I tried by clicking the tagging button on the message and by using the hotkeys Shift+T/Cmd+T . Then I used Enter to select and deselect the tags.

I know this doesn’t solve your issue, but maybe shows it could be localized on your device or workspace. It might be worth trying a different browser or an anonymous tab to see if it still happens there as well.

2 replies

Adam Warden
Innovator ✨
Forum|alt.badge.img+4
  • Innovator ✨
  • Answer
  • August 13, 2026

Hi Louise!
 

I tried replicating the error you are having, but didn’t run into the same issue. I tried by clicking the tagging button on the message and by using the hotkeys Shift+T/Cmd+T . Then I used Enter to select and deselect the tags.

I know this doesn’t solve your issue, but maybe shows it could be localized on your device or workspace. It might be worth trying a different browser or an anonymous tab to see if it still happens there as well.


Forum|alt.badge.img+7

Hi ​@LouiseKlein, Sean here from Fin tech support, thanks for the video. I had the same as ​@Adam Warden when trying to replicate it. It could be a browser extension or something else causing this as well. Are you still seeing this issue?