瀬下 達也

We are facing the same problem and we want the same solution.

**Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue (e.g., agents, admins, customers, etc.). (2-3 sentences)**

We would like to have a setting where public replies cannot be made without the approval of specific members (reviewers). Additionally, this setting should be configurable on a per-user basis. The purpose is to prevent members who are not familiar with Zendesk operations from making address errors when sending public replies. Another purpose is to apply this setting to members who have made errors, making it effective for a certain period to inconvenience them, thereby raising security awareness.

**What problem do you see this solving? (1-2 sentences)**

It will reduce address errors.

**When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)**

The last address error occurred about a month ago. It happens about once every six months. When it occurs, it requires a polite apology to the customer and consideration and implementation of recurrence prevention measures, which imposes a significant workload. In some cases, it may also result in compensation claims.

**Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)**

We are raising awareness through educational activities. However, since it is not a system-based solution, we are facing difficulties.

**What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)**

For emails not using Zendesk, we can set up a macro function in the mailer that requires the approval of specific members (reviewers) before sending. We would like to have a similar feature in Zendesk.

We are facing the same problem and we want the same solution.