Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

EMAIL SEND-­LOCK TO PREVENT ACCIDENTAL SENDING OF EMAILS

IP.com Disclosure Number: IPCOM000238156D
Publication Date: 2014-Aug-05
Document File: 8 page(s) / 253K

Publishing Venue

The IP.com Prior Art Database

Related People

Kieran Barry: AUTHOR

Abstract

A send-­lock system to avoid accidental sending of emails is disclosed. The send-­lock system provides a disable functionality for sending of emails. When the send-­lock system is enabled, a send button for an outgoing email in an email client can have a visually different color, shape, or size compared to when the send­-lock system is not enabled. Subsequently, when a user selects the send button while the send-­lock system is enabled, the send button can visually change its color, shape, or size and require the user to select the button to send the email. Alternatively, with the send-­lock system enabled, when the user selects the send button, the user can be provided with a pop-­up dialog box. The pop-­dialog box can require further user input to send the email. The described send­-lock system may be implemented via one or more of a menu option, radio buttons, checkboxes, etc. This send lock system avoids accidental sending of emails by visually alerting the user before he/she sends any email.

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

Page 01 of 8

    EMAIL SEND­LOCK TO PREVENT ACCIDENTAL SENDING OF EMAILS   

ABSTRACT 

    A send­lock system to avoid accidental sending of emails is disclosed. The send­lock system  provides a disable functionality for sending of emails. When the send­lock system is enabled, a send  button for an outgoing email in an email client can have a visually different color, shape, or size  compared to when the send­lock system is not enabled. Subsequently, when a user selects the send  button while the send­lock system is enabled, the send button can visually change its color, shape, or  size and require the user to select the button to send the email. Alternatively, with the send­lock system  enabled, when the user selects the send button, the user can be provided with a pop­up dialog box. The  pop­dialog box can require further user input to send the email. The described send­lock system may  be implemented via one or more of a menu option, radio buttons, checkboxes, etc. This send lock  system avoids accidental sending of emails by visually alerting the user before he/she sends any email.    

PROBLEM STATEMENT 

    Emails are a popular form of communication. Emails are not only used for personal use, but are  also heavily used in formal business settings. Users may accidentally send emails they did not mean to  send out, e.g., by mistakenly hitting the send button or keying a send shortcut. The risk of sending emails  unintentionally can be especially high in reply­to­all scenarios, as several different recipient email  addresses can be populated by default. A common practice employed to avoid unintentionally sending  emails is to not fill­in the recipients addresses until the email draft is complete and ready to send.  However, this practice can be labor intensive in the context of a "reply­to­all" email, where the  addresses of the recipients must be first removed and then re­populated when the email is complete. An  advanced and sophisticated mechanism to avoid accidental sending of emails is described.  
 

        
  SEND­LOCK SYSTEM 


Page 02 of 8

  The systems and techniques described in this disclosure relate to a send­lock system that  disables the email send functionality of an email client. The send­lock system can be used to avoid the  unintentional sending of emails, e.g., emails that are incorrect or incomplete. 

    Fig. 1 illustrates an example graphical user interface (GUI) for enabling or disabling a send­lock  system that can be implemented for use in an Internet, an intranet, or another client and server  environment. For example...