Google Push and Stamping Hybrid Launch Guide - Everything You Need To Know

Updated 1 week ago by Tori Scharadin

Summary

Here's everything you need to know about deploying the plain text signature into your employees' Gmail web browser, while also activating signatures for all other email clients and devices through what's known as stamping. This is a hybrid deployment style, meaning you are using two separate deployment methods that work seamlessly together to onboard employees with beautiful email signatures on every corporate email from any device.

Overview

Google Push Deployment Explained

Applies the Opensense plain text signature block to Outlook desktop signature settings for users as scoped by a script. GPO/Intune are Microsoft tools. GPO is used for domain-joined computers, while Intune can be used for Microsoft 365

Deployment Pre-Requisites:
  • On launch day, your Opensense Signature Admin will push to a list of users in Opensense. This push can then be performed for ongoing employee onboarding
  • A list can be generated within Opensense in your Users and Compliance. Here's how
Deployment Tips and Best Practices:
  • Best day to push: anytime
End 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 refresh their browser for their new signature to show in their account
  • As an extra check, Employees should ensure "My Signature" is set as default for new messages and replies by following the instructions in the linked document.
  • In the The Opensense Email Signature Instructions, 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.

Stamping Explained

Appends a signature to all emails from any device, after the email is sent. Note: will only add a signature when plain text signature block is not already present in the body of the email

Deployment Pre-Requisites
  • On launch day, your Google Admin adds users to an access control group/OU in Google. This activates email signatures for the specified users.
  • Coordinate deployment time and date of your Push to Gmail with your IT department so they can activate stamping at the same time
Deployment Tips and Best Practices:
  • Best day to deploy: any day, off-peak email hours.
  • Adding users to the stamping group can take up to 48 hours to fully adjust, though it typically happens much quicker. This is on the Microsoft side, unrelated to Opensense. Consider adding test users first to confirm how long it takes in your environment.
End User Experience: 
  • Employees will need to remove their old signature from their devices if they had one (otherwise, you run the risk of having two email signatures). They do not need to remove their Gmail web browser signature, since the Pusher tool will update that client.
  • Upon deployment, emails sent from their corporate email address(es) will have the Opensense signature "stamped" onto the email after the email is sent.
  • No signature will be visible in the body of sent emails

Internal Launch Communications (send 3 days before launch)

Communicating the Opensense launch before it happens can make the difference between receiving a few support emails and way too many if it's done poorly or not at all. To make it as easy as possible for you to take flight, here's an email example to get you started with your launch communications!

This email template was submitted with love by one of our customers who have successfully launched their email signatures! It's a great place to start, but remember that your email communication should be customized to your unique use case before sending out. This is the best time to prevent confusion for the end user. Additionally, we have highlighted any items that need to be personalized before sending out.

Launch communications should be sent 1-3 days before the day of launch. Bonus points for showcasing your new company signature even sooner than that on an all hands meeting!
If you have a launch communication email that you are proud of feel free to send it to your customer success manager so we can add it onto our knowledge base to help others!

To: All Employees

Subject: Standardized Corporate Email Signature

In an effort to present a stronger unified brand to our customers, we will be implementing a standardized email signature for all employees. Using a service called Opensense, the marketing team will now centrally manage the style and format of email signatures while employee contact information will be synced from our company directory. This ensures corporate email communications have a consistent appearance going forward.

This means your email signature on all emails from any device will be beautiful and up to date with all of the latest messaging, and best of all there is nothing to do on your end! Our IT team will be enabling a policy starting on XX/XX/XX that will automatically update your email signature in Gmail in your web browser. If on that day you compose an email and it is not the plain text signature, you may need to refresh Gmail or log back in. When sending from a mobile device, the email signature will append automatically after you send an email. If you have an existing signature on your mobile device, please turn it off.

Finally, due to contact information being synced with our company directory, any changes made directly to your signature block will be overwritten by directory info when sending email. If your signature contains incorrect info or you require any other assistance setting up your email signature, please contact our IT Helpdesk for support: help@ABC.com

Highlights of the new email signature block are:

Change Requests:

Do not add quotations, tag lines, former acquired company names, memes, videos, alternate legal disclaimers, Manufacturer logos, certifications etc. If you believe that you have a legitimate case for adding or changing something on your signature block please get approval from your manager, place an IT service ticket stating what you want and your request will be reviewed by Marketing for consideration. Do not make changes on your own. Thanks for your cooperation.

*Please note: The signature will appear as plain text when sending an email from Gmail on your web browser, and you will not see an email signature when sending from your mobile device. The recipient will always receive the beautiful, highly engaging email signature design that is centrally managed by Marketing. Your branded Opensense Signature Instructions document showcases this transformation.

Thank you!

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

Placement Issues (Stamped signatures)

Rarely, customers will encounter placement issues, where the stamped signature (when no plain text block is present) may be applied at the footer of the email thread instead of in the last message sent. If you encounter this or notice the signature is being stamped on somewhere it shouldn't be, please follow this guide for placement issues.

How to Send a #debug Email

Individual Edits in Users & Compliance

Opensense on O365


How did we do?