## Summary The `assignee_name` and `user_name` variables are swapped in the Chinese (zh/zh_CN) locale files for conversation assignment activity messages, causing the rendered text to show the wrong person as the assignee. ### Before (incorrect) | Template | English (correct) | Chinese (incorrect) | |---|---|---| | `assignee.assigned` | Assigned to **AgentA** by **Admin** | 由 **AgentA** 分配给 **Admin** | | `team.assigned` | Assigned to **TeamX** by **Admin** | 由 **TeamX** 分配给 **Admin** | | `team.assigned_with_assignee` | Assigned to **AgentA** via **TeamX** by **Admin** | 由 **AgentA** 分配给 **TeamX** 团队的 **Admin** | The Chinese text reads as if the conversation was assigned **to Admin** (the API caller), when it was actually assigned **to AgentA**. ### After (correct) | Template | Chinese (fixed) | |---|---| | `assignee.assigned` | 由 **Admin** 分配给 **AgentA** | | `team.assigned` | 由 **Admin** 分配给 **TeamX** | | `team.assigned_with_assignee` | 由 **Admin** 通过 **TeamX** 团队分配给 **AgentA** | Now correctly matches the English template semantics. ## Files Changed - `config/locales/zh_CN.yml` — 3 lines - `config/locales/zh.yml` — 3 lines ## How to Verify 1. Set locale to `zh_CN` 2. Have an admin assign a conversation to an agent 3. Check the activity message in the conversation — the assignee name should appear after "分配给", not before it Co-authored-by: Sojan Jose <sojan@pepalo.com>