Configure Emails to Send From Cockpit

Gainsight NXT

Overview

CSMs can send emails directly to contacts from Cockpit using the Email Task and Send Email features. For example, a CSM might want to send an email directly from Cockpit when they need to reach out to a customer to determine a suitable time to conduct an EBR; or to gather more details about a negative response to an NPS® Survey. (More ideas for templates here.)

Email Task: A new CTA Task Type called Email Task is available for inclusion in your Playbooks. During Playbook creation, you’ll select a Journey Orchestrator email template to associate with the email task. You’ll also have the opportunity to Map any Tokens in the email template. Once the Playbook is applied to a CTA (via a Rule or manually in Cockpit), the Email Task will be visible to the CSM, and the email template can be customized and sent to contacts of their choosing.

Emails are sent using the Gainsight Email Service. The Email Task type is available to add in Account and Relationship Playbooks.

This article includes instructions for users who have access to create Playbooks and therefore Email Tasks (typically Admins, but depends on your org).

Note: Users cannot manually add Email Tasks to CTAs in Cockpit. However, they can manually add a Playbook containing an Email Task to their CTAs.

Send Email: this feature allow the CSMs to send emails using any email template from Cockpit (within a CTA), without applying a playbook. To allows CSMs to send Ad-Hoc emails from Cockpit, admins must first configure an email template, and then CSMs can select the email template to associate with the email task.

For instructions on how CSMs can send emails from Cockpit, refer to Send Emails from Cockpit (aka, Email Assist and Send Email option).

Email Task

1. Navigate to Administration > Playbooks.
2. Click +PLAYBOOK to create a new Playbook, or click +TASK next to an existing Playbook’s name to add a new task. Create New Playbook Task window appears.
3. In the Create New Playbook Task window, you can see the usual options and the Type drop-down with two options: Task and Email. Select Email to create an Email Task.

4. After you select the Email Task Type, an additional drop-down is displayed that allows you to select an Email Template from Journey Orchestrator. For instructions, on how to make email templates, refer to Create Journey Orchestrator Email Templates.

5. After selecting the email template, click the Map Tokens icon to display the Map Email Tokens window. In this window, you can map any placeholders in the email template (similar to how you map tokens in email templates during Journey Orchestrator Program configuration).

6. In the Map Email Tokens window, hover by the placeholder text and click the mapping icon; then select the appropriate field for mapping. Click MAP.
   Note: Tokens can come from these source objects -- Person, Company, CS Task, Call To Action and User. If you are using a Relationship Playbook, you can also pull in Relationship attributes. Tokens will be replaced dynamically when the end user selects a user in the To field, and sends the email. If a token is null, the end user will have the option of deleting it and replacing with plain text.

7. (Optional) Click the Refresh button highlighted in the below image to import the latest content from Email Templates, and reset the existing token mappings. However, the latest content will not be reflected in the existing CTAs (where a Playbook containing this Email Template is used).
   Note: If you click the button highlighted in the image below, you must configure the token mappings again.

8. Back in the Create New Playbook Task window, finish making your selections (Due Date, Priority, etc.), and click SAVE.

The Playbook is available for use with Rules that generate CTAs, as well as users can apply the Playbook manually to CTAs in Cockpit.

Send Email

Send Email feature allows the CSMs to send emails using any email template in a CTA, without applying a playbook. For example, a Sales Representative will call the customer to discuss the renewal and based on interaction, they must send out a follow-up email.

The advantages of sending emails from Cockpit are:

• Email Task will be created within the CTA which allows for better tracking.
• Email is automatically logged to Timeline
• CSMs can use Email Analytics

Sending emails from cockpit can be enabled or disabled based on the CSM’s requirements in the Email Configuration page.

To enable this functionality:

1. Navigate to Administration > Email Configuration.
2. Click the COMPLIANCE tab.
3. Turn on the Allow sending emails directly from CTA's toggle button.
4. Click Save.

Edit Default Mapped Fields from Cockpit 

Once an Email Template is configured, CSMs while sending emails from Cockpit via Send Email (Ad-hoc email)/Playbook can now edit the value of the Default Mapped fields for reports and surveys, if the selected email template has a default mapping.

Use Case: For instance, if an admin configures an email template with a default mapping on a field such as First Name, and while sending email from Cockpit the CSM wants to replace First Name with Name, they can just edit the default mapped field.

For information on how to configure Default Mapping in Email Templates, refer Create Email Templates article.

Prerequisite: Admins must first enable the Edit default token mapping in cockpit toggle button, to allow CSMs to edit the default mapped fields.

To enable Edit default token mapping in cockpit button:

1. Navigate to Administration > Email Configuration.
2. Go to the Compliance page.
3. Enable the Edit default token mapping in cockpit toggle button.
4. Click Save.

BCC the Admin

Domains and Default Domain

You can create multiple custom domains based on your business requirements, and allow your CSMs to use while sending emails from Cockpit. For instance, you may want to send an email to a customer with a custom domain name as 'customerfeedback'.com, to collect feedback. 

The domain(s) configured in the Email Configuration is displayed in the consumption area if the Email Assist Domain Configuration option is selected. For more information, refer to the Configure General Settings article.

To create a Domain:

1. Click the + button.
2. Enter the domain name in the Domain is required text box.
3. Click Save.

Default Domain: All the custom domains created in the Domains section are shown in the dropdown list.You can select the required domain from the Default Domain dropdown list, and the selected domain is used by default, while sending emails from Cockpit. 

Note: If you have not created a single domain here, the logged-in user's domain is used while sending emails from Cockpit.

The following images show how CSMs can make use of the custom domains, while sending emails from cockpit.

CSMs can either save the email by clicking 'Save as Draft' or simply ‘Preview and Proceed’.

Reporting on Email Tasks

Email Tasks are not included in out-of-the-box Journey Orchestrator Analytics. However, you can build a report on the Email Logs object and display it on the Gainsight Home page or in a C360 section, if you would like users to be able to view open/click/view stats on their emails. The email engagement data is only available on the Email Logs object.

For Cockpit Email Assist open rates, use Email Logs Object and filter use case = Cockpit. In Email Logs, we have a field called Batch ID which has the ID of the CS Task when the email is sent from Cockpit. The "Email Opens" data that's visible in the task detail view comes from the Batch ID. Open count is the number of times the email has been opened and this includes stats for the recipient in the "To" field.

To track Email Assist usage by team member, use CS Task Object, Filter type name = email and use the IsEmailSent field on CS Task object.

Limitation to Tracking Email Opens

Even with Link Tracking enabled, Tracking whether the email was opened by the recipient may not work if it has been purposefully blocked by the customer's email client security settings.

For Email Assist tasks, Gainsight tracks open statistics by using a small invisible image attached to each email. When that image is loaded, it sends information back to the Gainsight logs to say that the email was opened. This tracking method is fairly standard among email providers.

With the Email Assist feature, it is observed that sometimes the tracking image is blocked when the email is received. Unless the user clicks "Show all images" in the email, we cannot track whether or not the email was opened. This is a common limitation that all email service providers encounter.

In Journey Orchestrator emails, the tracking link itself is embedded in the URL, so this is not an issue.

On a related note, if the contact in 'To' forwards an email to 10 other contacts, then those 10 emails will be tracked against her name. The open rate count will be added against the 'To' ID when the forwarded email is opened.

Template Ideas

Here are some additional ideas for email templates you could setup in Journey Orchestrator for use with Cockpit Email Tasks:

• NPS® Followups (promoter, passive, detractor)

• Customer Anniversary CTAs
• Reference Request Emails
• Usage Drops
• Support Risks
• CSM Transitions
• New Feature Explanations
• Customer Escalations
• Scheduling Meetings
• Helpful/Recommended Resources
• Training/Webinar Invitation

Playbook with Most Common Email Templates

Although end users can't manually create an Email Task from Cockpit, you can create a Playbook containing your top 5 email templates as tasks, and allow end users to apply the Playbook to a CTA in Cockpit. In this scenario, most likely your end user created a CTA manually, and the primary task is to send an email, so they just need a Playbook containing the most common email templates. Then, they can delete any of the unnecessary email templates/tasks from the CTA.  

Other Use Cases and Recommendations

If you have a team of people managing the same company, then the CTA owner could be different from the Email task owner. In this case, we recommend using CS Task > Owner Name in the email signature section, instead of CSM Name. This way, the name of whoever is sending the email displays in the signature.

If you’re using Email tasks to send internal emails, then in the body of the email, Gainsight recommends using the token User > First Name, instead of Person > First Name.