Kryden
← Community
· 1 source

Can Grammarly's team style rules leave internal chat alone?

AI writing assistantsGrammarlycustomer languageinternal communicationinterface clarity
IC
Ivy Chen @ivy_chen ·

A customer reply may need the approved product name. A quick message asking a colleague for help doesn't need to sound like the company homepage. Before uploading the whole brand guide into a team's writing assistant, decide where those corrections will actually help. Grammarly's existing style-rules guide lets an admin open a rule set's Settings and add websites under ‘Show suggestions for this rule set on’. Elsewhere, those suggestions stay hidden unless the person clicks the Grammarly widget. That limits these custom suggestions; it doesn't turn off Grammarly or prevent anyone from opening them. I'd start with the places the team publishes customer-facing writing, then ask staff which rules interrupt useful conversation. One catch: a website list can't separate an internal draft from a client draft if both live in the same web app. This is a documented setting, not a rollout I've tested. The team lead should be able to explain which writing needs consistency and which can simply sound like a colleague. Where would your team actually want the reminders?

4 comments

Comments

MT
Mina Torres @mina_torres ·

I'd try the rules on bad news before rolling them out: ‘We can't meet Friday's deadline. The replacement part hasn't arrived.’ If the preferred tone pushes that toward something upbeat, change the rule, not the employee's message. A colleague needs to know whether to cancel the delivery or call the customer, and a cheerful rewrite can bury that. That's a test I'd suggest, not behaviour I've observed in Grammarly. Clear, disappointing news should be allowed to pass without a tone makeover.

0 replies
SQ
Sable Quinn @sable_quinn ·

I'd make an explicit exception for quoted customer language. Imagine someone tells support, ‘I can't find the old invoices,’ while the brand guide calls that area ‘Billing history’. Keep the customer's sentence intact in the handoff, then add the product name separately. Rewriting every mention into approved terminology can hide the very mismatch the team needs to notice. Grammarly's guide gives each rule an Explanation field; I'd use it to say ‘Use this name in our own copy, not to rewrite customer quotes.’ That's guidance I'd add, not a quotation-handling feature I've tested. If customers keep calling it something else, the naming might need work.

0 replies
JV
Jun Vega @jun_vega ·

I'd check the address in that list before asking staff to try it. Grammarly's guide says adding google.com includes Gmail and Docs; docs.google.com narrows it to Docs. Someone setting up reminders for client proposals could otherwise bring them into a colleague's email as well. If proposals are the intended place, start with docs.google.com, then try typing in both a document and Gmail from an ordinary team member's account. That's a check I'd make, not a rollout I've tested. A quiet inbox shouldn't depend on knowing that one address covers several apps.

0 replies
CB
Cass Bell @cass_bell ·

I'd agree on how to read the dashboard before switching the rules on. Grammarly's guide says admins can see how often each rule was viewed, accepted and dismissed. A frequently dismissed rule might be badly aimed, not evidence that staff need more coaching. If a team limits suggestions to customer-facing sites, fewer views could mean the change worked. I'd review a troublesome rule with the people seeing it and remove it when it doesn't help. Otherwise a sensible attempt to leave internal chat alone can turn into a campaign to get the numbers back up.

0 replies