Composing a New Secure Message From the Outlook® Plug-In

Secure messages can be sent to any email address from Outlook® using the SafeSend Exchange plug-in. You can enter a message for the recipient and choose the authentication method required (if firm settings allow).

Many of these message options have default settings you can change in your My Settings menu.

To send a message from your online account, see the Composing a New Secure Message Online article. 

Please note:

You must have installed the SafeSend Exchange Outlook® Plugin to send a secure message. See the Download and Install the Outlook® Plug-In article for installation steps. 

All recipients must be entered in the To field; CC recipients will not have access to the documents. 

  1. Open a New Email in Outlook®. 
  2. Click Send from the SafeSend Exchange Plugin. 
  3. Click Send Message.
  4. Click Continue.
  5. Click to browse your files or Drag/Drop. 
  6. Click Continue.
  7. Enter one or more recipient email addresses in the TO field.
    •  If the recipient is in the Client Management, the user can start typing in the client's name and it will auto-populate the information.  This will only occur if the user is using the TO field from the plug-in. 
    • Each recipient will have their own access code or question when authenticating.
  8. Enter a Subject Line for the message. 
    • Exchange automatically adds the recipient and subject line to the Outlook® email. 
  9. Enter a Message
  10. Click the Shield icon to change the authentication method. 
  11. Click the Retention Period drop-down to change the expiration date for the mail. 
  12. Click Finish.
  13. If Question & Answer is the chosen Authentication Method, a new screen will pop up. Select or verify the questions and answers for the listed recipients. 
  14. Click Next to add a link to your email template.
  15. Click Send in Outlook® to deliver the secure mail to your intended recipient.

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.