Instead of using an out-of-the box notification, you can customize the look and feel of these notifications in SharpSpring. Choose a trigger, develop the notification and let SharpSpring do the work. This article will detail how to create and apply custom email notifications.
|
Available with: | ||||
Marketing Automation | ✓ | ||||
CRM Ultimate | ✓ | ||||
CRM PRO | ✓ | ||||
CRM Free | ✓ | ||||
Toolbar: | |||||
![]() |
|||||
Users: | |||||
Administrators | ✓ | ||||
Company Managers | ✓ | ||||
Marketing Managers | ✓ | ||||
Sales Managers | |||||
Salespersons | |||||
Jr. Salespersons | |||||
Understanding Notifications
There are two different types of notifications:
SharpSpring provides a stock set of notifications and form notifications that provides the necessary information about who has done what when interacting with your tasks. However, you may want to personalize these emails to your tastes. You can use these notification types to create customized email notifications. |
Note: SharpSpring users that have not opened an email or logged into the application for 180 days will have their system notifications suppressed. This includes VisitorID, billing, and automation-based notifications.
|
|
Creating Notifications
You can create email custom notifications as necessary. To create a custom email notification, do the following:
|
For example, the default notification email template has the following text and merge variables:
Hey {$recipient!"there"},
We are notifying you because {$firstName} {$lastName} triggered the task {$taskName} and was placed on the workflow {$workflowName}.
The merge variables in this email template will change based on:
- The user receiving the email
- The name of the individual who triggered the specific automation
- The automation itself
- Which workflow the individual was associated with
Merge Variable Breakdown
The available merge variables are as follows:
Merge Variable | Appearance | Definition |
||
Recipient | {$recipient} | The name of the user receiving the notification. | ||
Task Name | {$taskName} | The name of the automation that triggered the notification. | ||
Action Group | {$workflowName} | The name of the workflow branch that contained this notification. | ||
Lead Details | {$leadData} | First name, last name, email, and lead score of the lead who triggered the task. | ||
Form Name | {$formName} | The name of the form that the lead filled out and submitted. | ||
Form Data | {$formData} | All information that was submitted by the lead through filling out a form. |
Applying Notifications
Once you have created a custom notification email, you will need to apply it to an action group in order to send it. To apply a custom email notification to an action group, do the following:
|
||
Note: Custom notifications cannot be used with post back lead info alone. That notification action will need to be paired with either of the send a notification actions to send custom notifications.
|