Email Interface With Embedded Recipient Action Identifiers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The overwhelming volume of emails leads to productivity losses and chaos, as existing solutions focus on managing the influx rather than controlling it, resulting in constant distractions and inefficiencies.

Innovation Solution

A communication system and method that includes a graphical user interface with writing, reading, and organizing functions, allowing senders to specify recipient actions, read dates, and due dates, which are appended to emails and used by recipients to streamline email management and organization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If email volume increases to accommodate more communication, then communication capacity is improved, but productivity deteriorates due to overwhelming inbox management

Engineering Contradiction:
Improvecommunication capacityVSAvoidproductivity
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the email system into three distinct interfaces: a writing interface for sending emails with embedded instructions, a reading interface for receiving and processing emails, and an organizing interface for managing email folders and categories. This segmentation allows each component to handle specific tasks efficiently, preventing the overwhelming accumulation of unmanaged emails while maintaining high communication capacity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies preliminary action by embedding recipient action identifiers, read dates, and due dates into emails before they are sent. These instructions are prepared in advance and automatically processed by the recipient's system, eliminating the need for manual prioritization and sorting by the recipient, thus maintaining productivity even as communication volume increases.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If manual email management strategies are used to organize emails, then ease of operation is improved, but loss of time increases due to constant sorting and categorizing

Engineering Contradiction:
Improveease of operationVSAvoidtime for sorting and categorizing
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent implements self-service by enabling emails to carry their own organizational instructions (recipient action identifiers, read dates, due dates) that are automatically processed by the recipient's reading interface. The system sorts and categorizes emails based on these embedded instructions without requiring manual intervention, thereby maintaining ease of operation while eliminating time loss to manual sorting.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary organizing interface that automatically processes emails based on embedded instructions. This intermediary system acts as a mediator between the sending and reading interfaces, handling the sorting and categorization tasks automatically based on recipient action identifiers, read dates, and due dates, thus freeing users from manual organization while maintaining systematic email management.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of information

If email instructions and metadata are appended to each email, then information management is improved, but device complexity increases

Engineering Contradiction:
Improveinformation managementVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent applies universality by designing a standardized email structure where recipient action identifiers, read dates, and due dates are appended to all emails in a uniform manner. This multi-functional approach allows the same email structure to serve multiple purposes: tracking recipient actions, scheduling read dates, and managing due dates, thereby improving information management without proportionally increasing system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent merges multiple information elements (recipient action identifiers, read dates, due dates) into the email structure itself, combining these previously separate management functions into a unified email format. This merging reduces the need for separate tracking systems and interfaces, improving information management while actually simplifying the overall system architecture.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9973452B2Method and system for exchanging emails
Publication Date: 2018.05.15 TEMARIS SA
  • US9973452B2 patent drawing
  • US9973452B2 patent drawing
  • US9973452B2 patent drawing

AI summary

A communication system and method for organization, preparation and viewing of emails, including a graphical user interface operating on a display of a computing device. The graphical user interface includes: a writing interface with writing functions; a reading interface with a plurality of reading functions; and an organizing interface with a plurality of organizing functions. The writing functions including a recipient action identifier indicating what is expected of the recipient with regard to the sent email, what folder the writer has designated the email is to be stored in on the recipient computing device, a read date identifying a date on which the writer wishes the recipient to read the email, and a writing block for text associated with a message being sent in accordance with the email. The recipient action identifier and the read date are appended to the email and by a computer system of a recipient upon receipt of the email by the recipient.