# Viewing sent Notifications and responses

**URL:** <https://community.fibery.io/t/viewing-sent-notifications-and-responses/2014>\
**Category:** Ideas & Features\
**Tags:** notifications\
**Created:** [September 14, 2021, 2:24pm UTC](https://community.fibery.io/t/viewing-sent-notifications-and-responses/2014 "2021-09-14T14:24:53Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [September 14, 2021, 2:24pm UTC](https://community.fibery.io/t/viewing-sent-notifications-and-responses/2014/1 "2021-09-14T14:24:54Z")

</div>

As my team tries to use Fibery as a source-of-truth, we are hoping to keep our communication around our work, which we are attempting to bring entirely into Fibery, in Fibery.

We use commenting extensively to discuss our various tasks, meetings, projects, vendors, etc. etc. that we have tracked in Fibery. One thing we are starting to see over time however is that a lot of the comments with @mentions asking questions, or requesting feedback, from one team member to another, get lost. What happens is 1) the recipient of the comment might not respond, or 2) the sender of the comment isn’t able to track the request easily, because there is no place in Fibery to see @mentions or comments you have made in one place, similar say to “sent” in your Email client.

A few tools like Wrike and ClickUp have this feature, and it really helps keep communication organized in an app, without the need to out and out create a task for something like “hey, could you fill in the description in this entity” or other more “lite” requests within a team using Fibery. However this is a very important part of communication within Fibery, and without both the ability to see if your requests are responded to, and track the ones you sent, we are getting lost and stuff is getting through the cracks.

This would go great with my other request around being able to “assign” @mentions to insure they are read and responded to:

> [@Next iteration of Comments - Commenting when Resolving & assigning as tasks/reminders](https://community.fibery.io/t/next-iteration-of-comments-commenting-when-resolving-assigning-as-tasks-reminders/527):
>
> Hi once more, I wanted to make some suggestions for comments as you guys evolve them. This is coming mainly from my extended use of a ton of apps in the last several years, and none seem to be able to pull all the best methods for implementing comments all in one place. You guys have a good chance to do that now! Resolving Comments I’ve seen a great way to close out comment resolutions in some apps where they will prompt an extra comment around the “resolve” action. In most cases, you can…

Happy to expand on this idea if I didn’t communicate this clearly to the community. Thanks!

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [September 14, 2021, 2:40pm UTC](https://community.fibery.io/t/viewing-sent-notifications-and-responses/2014/2 "2021-09-14T14:40:46Z")

</div>

> [@B\_Sp](#):
>
> What happens is 1) the recipient of the comment might not respond  
> …  
> without both the ability to see if your requests are responded to, and track the ones you sent, we are getting lost and stuff is getting through the cracks.

Just to be clear, is the problem that people being @mentioned are not responding, or is it that the requester finds it hard to see the response?

If the former, then perhaps the focus needs to be on making notifications more visible/persistent/nagging, rather than putting the onus on the requester to investigate/chase up unresponsive colleagues.

If the latter, then perhaps the focus needs to be on making the request/response chain more discoverable

Interested to hear where you see the root cause of the problem to be…

---

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [September 14, 2021, 5:00pm UTC](https://community.fibery.io/t/viewing-sent-notifications-and-responses/2014/3 "2021-09-14T17:00:10Z")

</div>

If I read it correctly: the Requester finds it hard to _track_ whether or not their `@mention`s have been responded-to.

I don’t know how Wrike and ClickUp handle it, but _some_ sort of functionality to help track “_anything I decide needs follow-up_” would certainly be very useful!

I like the way Gmail handles this, where you can “Snooze” anything in your Inbox, which makes it disappear, but automatically pop up again in your Inbox after `x` days.

One way to handle this in Fibery might be:

- Have the ability to Snooze **any** Notification.
- A new tab on the Notifications window that shows Snoozed (upcoming) notifications.
- An new tag (maybe `@followup`?) that works similarly to `@mention`, but creates a Snoozed notification for you. Basically a shortcut to `@mention`ing yourself, with a delayed notification.
- Also the ability to _directly_ tag any entity for follow-up via a menu in the entity-view; i.e., so you can tag an entity without having to enter a `@followup` comment in text somewhere.
- It would also be useful to be able to associate a short description with a follow-up tag, that would appear in the follow-up notification, for a little extra context (“Um, why did I tag this?”).
- And a new script action: “Tag entity for follow-up” (optionally specify User and description)

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [September 14, 2021, 6:35pm UTC](https://community.fibery.io/t/viewing-sent-notifications-and-responses/2014/4 "2021-09-14T18:35:54Z")

</div>

As someone who is in favor of [a _universal_ reminder/snooze function](https://garden.oshyan.com/t/idea-ubiquitous-reminder-snooze-scheduling-functions-in-messaging-apps-operating-systems-etc-etc/87), I love the idea of snoozable Fibery notifications.

I agree it would be good to have a bit more information about how ClickUp and/or other apps handle this though, to see if there are transferrable ideas.

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [September 14, 2021, 6:54pm UTC](https://community.fibery.io/t/viewing-sent-notifications-and-responses/2014/5 "2021-09-14T18:54:20Z")

</div>

Guys @Oshyan @Matt_Blais and @Chr1sG , appreciate the quick responses on this one!

To clarify further, what I think would be extremely helpful is some kind of area, possibly in the future Dashboards feature, where you could track @mentions and comments - both of which are key parts of Notifications.

We have issue with both being able to see if somebody has responded to your mention, and keeping track of how many mentions you generate. In the above example, I don’t have a way to go back and see that I asked the colleague to fill in that Entity description unless I remember that I did that. So it’s easy to forget about it and ultimately lose track. But in this case I don’t want to go to the extent of creating a full-on entity for this need, that seems too much.

ClickUp handles this with something called “Assigned Comments”.

> **[Assigned Comments](https://docs.clickup.com/en/articles/924291-assigned-comments)**

This is a good solution. In a nutshell, you can simply “Assign” a comment. What that does is that instead of just an @mention going to the recipient, the Assigned comments collect in an inbox, and both the sender and recipient can keep track of them. So this handles both of my needs. However, in the ClickUp version, which allows you to “resolve” the Assigned Comment, you aren’t required to make an additional comment when resolving. That is another feature I’d love to see in Fibery that I quoted above. Without that, somebody can simple “check off” the assigned comment, but not actually write anything about what was done. So the originator of the assigned comment is missing info that might be important. This is similar to the limitation of a checklist vs. a task that has a comments area for further detail.

In Wrike, you have an area where you can see all the mentions you sent. So like in Gmail, you can at least go back and get a list of all the requests you made, so you don’t have to remember them.

Really eager to see how much of this makes its way into Fibery, would be very helpful. Thanks again guys.

Oh and PS I really appreciate the extra votes @Chr1sG and reverting my status as “regular.” I had that for the longest time, but of late I’ve had “life” stuff to deal with and don’t have so much time to post around here. I will use those votes judiciously!

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [September 14, 2021, 6:59pm UTC](https://community.fibery.io/t/viewing-sent-notifications-and-responses/2014/6 "2021-09-14T18:59:00Z")

</div>

> [@B\_Sp](#):
>
> of late I’ve had “life” stuff to deal with

I know the feeling! Hope it’s been good stuff rather than bad 🤞
