You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A feature that would override silent mode, vibrate-only mode and do-not-disturb mode if a message (optionally only from a prioritised/favourited contact) contains a keyphrase from a list defined by the user.*
This would allow for users to be reachable for urgent messages.
*I.e. urgent, Urgent, NOW, you awake, etc. | Option to chose case-sensitivity and to chose between a contain vs. exact match filter would be nice.
The text was updated successfully, but these errors were encountered:
I'm thinking this keyword feature could be implemented as a new notification category which will be used whenever the sender is in the specified set (starred contacts only, contacts, or anyone) and the message contains one of the specified keywords.
Then users can manage their notification preferences for this special category however they like -- maybe they want these to override do-not-disturb, or maybe they want to silence messages based on keywords.
But maybe it doesn't have to be limited to one rule?
The app could allow the user to create more than one of these rules, and name them. Each rule would have a sender category and list of keywords. The app would create a notification channel for each rule. The user could arrange the rules in priority order for matching -- first match wins. If none match, then a notification channel would be selected according to the sender's category only as suggested in #75.
A feature that would override silent mode, vibrate-only mode and do-not-disturb mode if a message (optionally only from a prioritised/favourited contact) contains a keyphrase from a list defined by the user.*
This would allow for users to be reachable for urgent messages.
*I.e. urgent, Urgent, NOW, you awake, etc. | Option to chose case-sensitivity and to chose between a contain vs. exact match filter would be nice.
The text was updated successfully, but these errors were encountered: