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:
defining boost actions and detract actions for very important person (“VIP”) scoring;
sending the boost and detract actions to a user device for use by at least an email application and a second application, both the email application and second application implementing a software development kit (“SDK”) to detect the boost actions and the detract actions performed by a user, wherein the email and second application each modify a local VIP score based on the boost actions and detract actions at the respective application, and wherein the user device is associated with the user;
receiving, from the user device, the local VIP scores of at least the email application and the second application; and
sending aggregated VIP information to the user device for governing which email application notifications or second application notifications to present on the user device, the aggregated VIP information being based on at least the local VIP scores from the email application and second application.
2. The method of claim 1 , further comprising:
receiving an alias from an identity management server based on an entity identified in the local VIP scores; and
creating the aggregated VIP information for the entity by using the alias to associate additional VIP scores with the local VIP scores.
3. The method of claim 1 , wherein the local VIP scores correspond to the contacts in the email application, wherein the method further comprises:
matching the contacts of the local VIP scores to identities retrieved from an identity provider;
identifying global VIP scores that correspond to the retrieved identities; and
creating the aggregate VIP scores for the contacts based on the local VIP scores and the global VIP scores.
4. The method of claim 1 , wherein the notifications are not displayed unless they are associated with an aggregate VIP score above a threshold, wherein another action is taken if the aggregate VIP score is above a second threshold.
5. The method of claim 1 , wherein the email application and the second application both use the aggregated VIP information to determine which content to display at the user device.
6. The method of claim 1 , further comprising:
sending a first scoring profile to the user device for use in calculating a first local VIP score, the scoring profile defining the booster action and the detract action,
wherein the boost action increases a local VIP score for a contact based on emails sent to the contact, and wherein the detract action decreases the local VIP score when emails from the contact are deleted without being opened.
7. The method of claim 1 , further comprising:
sending the aggregated VIP scores to a mobile flows service, wherein the mobile flows service accesses other applications based on identifying content related to those applications within the email application, and wherein the mobile flows service determines which other applications to access based in part on the aggregated VIP scores.
8. A non-transitory, computer-readable medium comprising instructions that, when executed by a processor, perform stages for notification management, the stages comprising:
defining boost actions and detract actions for very important person (“VIP”) scoring;
sending the boost and detract actions to a user device for use by at least an email application and a second application, both the email application and second application implementing a software development kit (“SDK”) to detect the boost actions and the detract actions performed by a user, wherein the email and second application each modify a local VIP score based on the boost actions and detract actions at the respective application, and wherein the user device is associated with the user;
receiving, from the user device, the local VIP scores of at least the email application and the second application; and
sending aggregated VIP information to the user device for governing which email application notifications or second application notifications to present on the user device, the aggregated VIP information being based on at least the local VIP scores from the email application and second application.
9. The non-transitory, computer-readable medium of claim 8 , the stages further comprising:
receiving an alias from an identity management server based on an entity identified in the local VIP scores; and
creating the aggregated VIP information for the entity by using the alias to associate additional VIP scores with the local VIP scores.
10. The non-transitory, computer-readable medium of claim 8 , wherein the local VIP scores correspond to contacts in the email application, the stages further comprising:
matching the contacts of the local VIP scores to identities retrieved from an identity management service;
identifying global VIP scores that correspond to the retrieved identities; and
creating the aggregate VIP scores for the contacts based on the local VIP scores and the global VIP scores.
11. The non-transitory, computer-readable medium of claim 8 , wherein the notifications are not displayed unless they are associated with an aggregate VIP score above a threshold, wherein another action is taken if the aggregate VIP score is above a second threshold.
12. The non-transitory, computer-readable medium of claim 8 , wherein the email application and the second application both use the aggregated VIP information to determine which content to display at the user device.
13. The non-transitory, computer-readable medium of claim 12 , the stages further comprising:
sending a first scoring profile to the user device for use in calculating a first local VIP score, the scoring profile defining the booster action and the detract action,
wherein the boost action increases a local VIP score for a contact based on emails sent to the contact, and wherein the detract action decreases the local VIP score when emails from the contact are deleted without being opened.
14. The non-transitory, computer-readable medium of claim 8 , the stages further comprising:
sending the aggregated VIP scores to a mobile flows service, wherein the mobile flows service that accesses other applications based on identifying content related to those applications within the email application, wherein the mobile flows service determines which other applications to access based in part on the aggregated VIP scores.
15. A system for device notification management, comprising:
a physical memory storage including a non-transitory, computer-readable medium comprising instructions; and
a management server including a processor that executes the instructions to carry out stages comprising:
defining boost actions and detract actions for very important person (“VIP”) scoring;
sending the boost and detract actions to a user device for use by at least an email application and a second application, both the email application and second application implementing a software development kit (“SDK”) to detect the boost actions and the detract actions performed by a user, wherein the email and second application each modify a local VIP score based on the boost actions and detract actions at the respective application, and wherein the user device is associated with the user;
receiving, from the user device, the local VIP scores of at least the email application and the second application; and
sending aggregated VIP information to the user device for governing which email application notifications or second application notifications to present on the user device, the aggregated VIP information being based on at least the local VIP scores from the email application and second application.
16. The system of claim 15 , the stages further comprising:
receiving an alias from an identity management server based on an entity identified in the local VIP scores; and
creating the aggregated VIP information for the entity by using the alias to associate additional VIP scores with the local VIP scores.
17. The system of claim 15 , wherein the local VIP scores correspond to contacts in the email application, the stages further comprising:
matching the contacts of the local VIP scores to identities retrieved from an identity management service;
identifying global VIP scores that correspond to the retrieved identities; and
creating the aggregate VIP scores for the contacts based on the local VIP scores and the global VIP scores.
18. The system of claim 15 , wherein the notifications are not displayed unless they are associated with an aggregate VIP score above a first threshold, wherein another action is taken if the aggregate VIP score is above a second threshold.
19. The system of claim 15 , wherein the email application and the second application both use the aggregated VIP information to determine which content to display at the user device.
20. The system of claim 15 , the stages further comprising:
sending the aggregated VIP scores to a mobile flows service, wherein the mobile flows service that accesses other applications based on identifying content related to those applications within the email application, wherein the mobile flows service determines which other applications to access based in part on the aggregated VIP scores.