Recent searches


No recent searches

Agent Workspace - add Grammarly support

Completed


Posted Mar 15, 2021

The Zendesk Customer Advocate staff suggested I post this.

Our team has experienced text disappearing issues in the Agent Workspace Composer when using the Grammarly browser extension. It looks like the extension is not supported and can cause issues.

The workaround is to enable the "Enable fix for composer" feature in Agent Workspace. I'd like to eventually disable that, as there are some enhancements I am missing out on with that enabled.


3

8

8 comments

Official

image avatar

Amy Lee

Zendesk Product Manager

Grammarly should be supported with the Agent Workspace composer! Please reach out to our support team if you are experiencing issues. Thank you!

0


image avatar

Kyle Pinkley

Zendesk Luminary

We would also like to see Grammarly support added when "Enable fix for composer" is disabled.

5


I am probably searching in all the wrong places, but where in Zendesk Workspace can I find the feature "Enable fix for composer" ?

0


image avatar

Aubree

Zendesk Customer Care

Hi Edwin,

Upon checking, it seems that this option, "Enable fix for composer" which should be found in the Agent Workspace Settings under Admin icon () > Settings > Agents > Agent Workspace is no longer present for there's no fallback editor. However, there aren't any known issues caused by interactions with Grammarly and the current editor.

I hope this helps! 

 

Aubree Rose Mia | Customer Advocate

0


Hello, Aubree and Zendesk support.

I am still experiencing issues using Grammarly within the Agent Workspace in Zendesk. Most often, the issues related to Grammarly getting confused about spaces. Sometimes the space that should be between two words is removed. Usually, when this happens, the missing space will be perceived by Grammarly, but when the option to correct this is clicked, nothing happens, and a space does not separate the two words. 

Do you know if this is a known issue, and if so, are you aware of a fix for this bug?

I am using a Mac with the following:

  • Mac OS - 13.0.1 v(22A400)
  • Chrome - Version 107.0.5304.110 (Official Build) (x86_64)
  • Zendesk - Version: 16137 (836cc08b5ff0a9217564f358fc1146d46d7aa4ad)
  • Grammarly Chrome extension - Version 14.1087.0
     
     
  • Grammarly Desktop for Mac - Version 1.15.2.0

 



Thank you

1


I can confirm that this is still an issue across browsers with the Grammarly extension.  Something is causing both auto-correct and manual error correction to fail within the Agent Workspace, based on where the cursor is placed within the textbox at the time of correction. This frequently means the corrected word is inserted before, after, or in the middle of the incorrect word, rather than replacing it. 

With the | symbol representing the cursor placement: correcting "delivrey|" generates "delivreydelivery".  If the cursor is in the middle like "deli|vrey" it becomes "delideliveryvrey".  This happens with phrase or sentance correction as well, dropping phrases into random locations in the text block depending where you happened to click.

 

I contacted Grammarly twice about this issue, in July 2022 and again in November 2022, and they indicated both times that this was a known issue. What's particularly funny to me is that Grammarly themselves use Zendesk, so their own CSR's must be unable to use their product, or they must be in the legacy editor still or something.

Please rest assured that our technical team is already aware of the problem you reported, but unfortunately, we don’t currently have a solution to it. We know it's taking a long time to resolve — it turns out there are some technical considerations that our engineers need time to work through. We appreciate your patience and apologize for any inconvenience.

0


I appreciate Matthew's description above and I'm experiencing the same issue. If there's anywhere I need Grammarly's help, it's definitely when using Zendesk to interact with customers!

0


This does not work... Grammarly flickers on and off and rarely stays during the the time it takes to compose a reply. Matt Davis above explains the issue well.

Please look into it Zendesk... Pinning a top comment as "Nah, it's working fine" when it obviously isn't it's a good look.

0


Please sign in to leave a comment.

Didn't find what you're looking for?

New post