G-Suite - Signature Deployment Best Practices and End User Experience

Updated 3 months ago by Tori Scharadin

READ: Whenever deploying the Opensense Signature in bulk

-Announce on an all hands meeting for an engaging launch
-Reduce internal support requests by sending a reminder email (or two!) leading up to launch
-Support requests tend to subside after a week or so after launch

Push to Gmail

Deployment Tips and Best Practices:

  • Best day to deploy: any

User Experience: 

  • When you push to Google, we will write to "My Signature" in Gmail signature settings as shown in your branded Opensense Signature Instructions document. If "My Signature" is already in use, what is currently there will be overwritten.
  • Employees may need to do a browser page refresh for their new signature to show in their account
  • As an extra check, Employees can ensure "My Signature" is set as default for new messages and replies simply by following the instructions in the linked document.
  • In the The Opensense Signature Guide, we share how to prevent Google from moving the signature to the bottom of the email thread. This is not an Opensense setting but employees/admins have found our instruction on fixing this useful!
  • The default signature will appear as plain text, and the recipient will always receive a beautiful email signature design that is centrally managed by Marketing. Your branded Opensense Signature Instructions document explains this transformation.

Push to Email

Deployment Tips and Best Practices:

  • Best day to deploy: early in the week to spur adoption through-out the rest of the week.

End User Experience:

  • Employees will receive their customized Opensense signature in their inbox on every device. They will need to complete a simple one time copy and paste of their Opensense signature into any devices they are sending emails from. Your branded Opensense Signature Instructions document contains set up instructions for Major desktop and mobile devices
  • The default signature will appear as plain text, and the recipient will always receive the robust, beautiful, highly engaging email signature design that is centrally managed by Marketing. Your branded Opensense Signature Instructions document showcases this transformation.

Group Policy Object (GPO) with Azure Active Directory

Deployment Tips and Best Practices:

  • Your System Admin runs the script
  • Best day to deploy: any

End User Experience: 

  • the Opensense signature will be each user's default signature in their Outlook desktop client once the script is run (check with your technical team if they have modified the script and what behaviors to expect). 
  • The default signature will appear as plain text in Outlook, and the recipient will always receive a beautiful email signature design that is centrally managed by Marketing. Your branded Opensense Signature Instructions document showcases this transformation.


How did we do?