# Allow “Mark as Solution” in group messages **URL:** https://meta.discourse.org/t/allow-mark-as-solution-in-group-messages/370496 **Category:** Feature **Tags:** solved, completed **Created:** [June 17, 2025, 9:47am UTC](https://meta.discourse.org/t/allow-mark-as-solution-in-group-messages/370496 "2025-06-17T09:47:56Z") **Posts on this page:** 1 **Showing post:** 13
### Author: ![Gerard\_Cobas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerard_cobas/32/310434_2.png) [@Gerard\_Cobas](https://meta.discourse.org/u/Gerard_Cobas) #### Post date: [July 14, 2025, 10:55am UTC](https://meta.discourse.org/t/allow-mark-as-solution-in-group-messages/370496/13 "2025-07-14T10:55:16Z")
Hi Dave, thanks for picking this up! A bit of context on our side: we use group private messages as shared inboxes for support, following a pattern similar to what’s described here: [Use Discourse as a private support ticket system](https://meta.discourse.org/t/use-discourse-as-a-private-support-ticket-system/72268) Our support agents rely on the **“Mark as Solution”** button to indicate when an issue has been resolved. This serves two purposes: 1. **Internally** , it helps the team quickly identify and close resolved conversations. 2. **Programmatically** , it acts as a trigger. We have a webhook set up (e.g., `/admin/api/web_hooks/38/edit`) that fires when a post is marked as a solution, syncing with our backend system. Group PMs are core to our support workflow, and we handle a significant number of account-specific topics, which makes public topics unsuitable. The solution marker is more than just a UI element. It is part of our internal process, and without it, agents can’t properly close tickets or trigger the automation that depends on it. Even though it’s a small change on the surface, it breaks a critical part of our workflow, so we’d really appreciate a reconsideration or an alternate approach. Thanks! --- _[View the full topic](https://meta.discourse.org/t/allow-mark-as-solution-in-group-messages/370496)._