Browse Prior Art Database

Communities Queue Agent

IP.com Disclosure Number: IPCOM000237848D
Publication Date: 2014-Jul-16
Document File: 3 page(s) / 50K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is an email function for a queue agent, which evaluates email elements such as date, notification vs action required, and priority. The queue agent enables a user to program associated community preferences to help manage and prioritize email messages and tasks.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 3

Communities Queue Agent

Due to the abundance and frequency of information users receive via email from different communities and communication portals, a method is needed to more efficiently manage and prioritize the email messages as well as any action that the user must take in response. Users need a method to create a customized automation delivery of emails from other community members.

The novel solution is an email function for a queue agent, which evaluates email

elements such as date, notification vs action required, and priority. The queue agent enables a user to program associated community preferences, including, but not limited to:

• Holding all notifications during a specified period • Sending, at a specified time of day, a single daily notification of all community activities
• Prioritizing activities by response due-dates
• Setting priorities on communities
• Sorting by community or activity with critical designations
• Tagging critical To-Do tasks

The queue agent is created in the Community. The scheduling and priority preferences are predefined by the end user. These preferences allow a user to define both a personalized schedule and a prioritization system for notifications and activities selections.

The queue agent allows a user to select default settings for all communities as well as different options within specific communities. The queue agent monitors all of the user's communities based on the user's defined preferences. Based on the user's selections the agent sends and incoming mail message.

When the queue agent detects a community notification or an activity (e.g., "To Do" item), it checks the agent and queues the notifications based on time frames and priorities predefined by the user.

Figure 2: Scheduling sample: Hold all notifications/activities during this window. The queue agent is telling the connections to hold the emails it sends until the defined user parameters are met.

1


Page 02 of 3

Figure 3: Scheduling sample: Send notifications at this time of day

Figur...