every type of message needs a status for filtering purposes
Currently, the user is forced to receive message notifications in a certain manner: If no tag is selected in notifications then the user sees every-single-notification for birthday reminders, untagged text messages, reminders, etc. This is quite overwhelming. And to say that it is overwhelming is an understatement. Though productivity has increased, the stress level in our office has gone up significantly since initiating Weave. I think that every single notification type deserved a status (review, birthday, reminder, etc.) and the user reserved the right to turn it on or not. Right now, we get so many notifications (from officer manager to provider) for messages that users are beginning to ignore the notifications. The user has no idea if a notification applies to them unless they go to 'actionable'. In the middle of seeing a patient I want the option to glance at a notification (in the desired pop up location) sent to me and respond without have to go to 'actionable' to see whether it was for me or not.
-
Kris Britt commented
New messages coming through need an "auto status" of "uncategorized" (or something of the sort) so that we can filter them out. Also, automated messages sent need their own automatically assigned status...such as birthday text being categorized as "birthday" so that we can choose to turn off the birthday text notifications (and others). Does this make sense? our front office is being inundated with all of the text sent out (abandoned call, birthday, etc.). I'm about to turn them off so that I can give our front office a break.