Management of contextual device notifications with VIP rankings
Examples described herein include systems and methods for management of contextual notifications on user devices. Entities can be categorized as VIP status based on scoring profiles sent from a management server to the user device. Applications on the user device can implement an SDK that reads the profiles and sets certain actions to boost scores and others to reduce scores. These local VIP scores can be sent periodically from the user device to the management server. The management server can use them in conjunction with global VIP scores for the same entities to create aggregated VIP information. This can be sent back to the user device, allowing the user device to then visualize different notifications or workflows based on whether an entity's aggregated VIP information exceeds one or more thresholds.
1. A method for contextual notifications, comprising:
detecting, at a user device, boost actions and detract actions performed by a user at first and second applications, wherein the first and second applications implement a software development kit (“SDK”) that defines the boost and detract actions;
modifying a set of local very important person (“VIP”) scores according to the detected boost and detract actions, wherein the local VIP scores are associated with different entities;
sending the local VIP scores to a server;
receiving, from the server, a VIP scoring profile that includes scores or rankings of entities based on aggregation of local VIP scores for the entities; and
changing, at the user device, visibility of first or second application content according to the entity scores or rankings in the VIP scoring profile.
2. The method of claim 1 , wherein at least some of the different entities correspond to contacts in the first application, wherein the contacts are used in the aggregation of local VIP scores.
3. The method of claim 1 , wherein changing visibility includes declining to display notifications unless they are associated with an aggregate VIP score or rank above a threshold.
4. The method of claim 1 , wherein the first application and the second application both use the aggregated VIP information to determine which content to display at the user device.
5. The method of claim 1 , wherein the VIP scoring profile defines VIP entities and very VIP (“VVIP”) entities, and wherein the SDK causes the first and second applications to change visibility differently based on whether content is associated with an entity that the VIP scoring profile defines as VIP versus VVIP.
6. The method of claim 1 , wherein a first boost action increases a local VIP score associated with a contact based on messages sent to the contact, and wherein a first detract action decreases the local VIP score when messages from the contact remain unopened for a threshold period.
7. The method of claim 1 , wherein aggregation of the local VIP scores by the server includes:
determining multiple aliases that correspond to a single entity; and
for the single entity, aggregating local VIP scores associated with the multiple aliases.
8. A non-transitory, computer-readable medium comprising instructions that, when executed by a processor, perform stages for notification management, the stages comprising:
detecting, at a user device, boost actions and detract actions performed by a user at first and second applications, wherein the first and second applications implement a software development kit (“SDK”) that defines the boost and detract actions;
modifying a set of local very important person (“VIP”) scores according to the detected boost and detract actions, wherein the local VIP scores are associated with different entities;
sending the local VIP scores to a server;
receiving, from the server, a VIP scoring profile that includes scores or rankings of entities based on aggregation of local VIP scores for the entities; and
changing, at the user device, visibility of first or second application content according to the entity scores or rankings in the VIP scoring profile.
9. The non-transitory, computer-readable medium of claim 8 , wherein at least some of the different entities correspond to contacts in the first application, wherein the contacts are used in the aggregation of local VIP scores.
10. The non-transitory, computer-readable medium of claim 8 , wherein changing visibility includes declining to display notifications unless they are associated with an aggregate VIP score or rank above a threshold.
11. The non-transitory, computer-readable medium of claim 8 , wherein the first application and the second application both use the aggregated VIP information to determine which content to display at the user device.
12. The non-transitory, computer-readable medium of claim 8 , wherein the VIP scoring profile defines VIP entities and very VIP (“VVIP”) entities, and wherein the SDK causes the first and second applications to change visibility differently based on whether content is associated with an entity that the VIP scoring profile defines as VIP versus VVIP.
13. The non-transitory, computer-readable medium of claim 8 , wherein a first boost action increases a local VIP score associated with a contact based on messages sent to the contact, and wherein a first detract action decreases the local VIP score when messages from the contact remain unopened for a threshold period.
14. The non-transitory, computer-readable medium of claim 8 , wherein aggregation of the local VIP scores by the server includes:
determining multiple aliases that correspond to a single entity; and
for the single entity, aggregating local VIP scores associated with the multiple aliases.
15. A system for device notification management, comprising:
a physical memory storage including instructions; and
a processor that executes the instructions to carry out stages comprising:
detecting, at a user device, boost actions and detract actions performed by a user at first and second applications, wherein the first and second applications implement a software development kit (“SDK”) that defines the boost and detract actions;
modifying a set of local very important person (“VIP”) scores according to the detected boost and detract actions, wherein the local VIP scores are associated with different entities;
sending the local VIP scores to a server;
receiving, from the server, a VIP scoring profile that includes scores or rankings of entities based on aggregation of local VIP scores for the entities; and
changing, at the user device, visibility of first or second application content according to the entity scores or rankings in the VIP scoring profile.
16. The system of claim 15 , wherein at least some of the different entities correspond to contacts in the first application, wherein the contacts are used in the aggregation of local VIP scores.
17. The system of claim 15 , wherein changing visibility includes declining to display notifications unless they are associated with an aggregate VIP score or rank above a threshold.
18. The system of claim 15 , wherein the first application and the second application both use the aggregated VIP information to determine which content to display at the user device.
19. The system of claim 15 , wherein the VIP scoring profile defines VIP entities and very VIP (“VVIP”) entities, and wherein the SDK causes the first and second applications to change visibility differently based on whether content is associated with an entity that the VIP scoring profile defines as VIP versus VVIP.
20. The system of claim 15 , wherein a first boost action increases a local VIP score associated with a contact based on messages sent to the contact, and wherein a first detract action decreases the local VIP score when messages from the contact remain unopened for a threshold period.