In any of the embodiments, a single graphical user interface action (e.g., one-click of a button, one-touch of a button) may be sufficient to trigger the notification to be sent to the network device. Examples of such a graphical reporting button are illustrated in FIG. 16 and FIG. 17. The graphical user interface can include a label to the effect of “Report Phishing” as a button 520, or may be presented as a contextual menu item 510. In some embodiments, a single click of a user-interface element may be sufficient to report a simulated phishing message generated by the system described herein. In such embodiments, identifying information relating to the reported message and/or the user who reported the message may be communicated to the network server device while the body of the message is not transmitted to the network server device. In further embodiments, when reporting a suspicious message not generated by the system, an additional confirmation dialog may be presented to the user before all of some the message is communicated to the network server device for further processing.
Additionally, the system can receive a suspicious message from a reporter in a variety of other ways. In one embodiment, the system is associated with a designated email address for receiving reports. A reporter may report a message as suspicious by sending the suspicious message directly to the system, attaching the suspicious message to an email that is sent the system, or forwarding the suspicious message to the system via the associated email address.