When deploying Rattle Workflow notifications to your teams there are two different types of alerts that you can send: Visibility alerts and Action-Based alerts.
What are visibility alerts?
Just that! These alerts are intended to provide insights related to your teams or organization (i.e. activity metrics, deal progression, revenue metrics, etc.). Providing better visibility to important events or milestones in your pipeline.
All Rattle notifications will have a “View in SFDC” button that users can utilize to take them directly to the record referenced in the notification.
How do I best deploy these two different types of alerts?
Provide context in the opening message
Make it clear why they are receiving the alert, and tag relevant users.
Example:
Use this icon to add dynamic fields to the notification to clearly identify the object you are referencing (ex. Opportunity : Name), why you are receiving the message (ex. Opportunity : Stage) and tag relevant users (ex. Opportunity : Owner).
Use this icon to add emojis and highlight the emotion of the notification (ex. Celebrate with applauding hands, money bag; Alert with red sirens, fearful face, etc)
See also: Opening Text Formatting
Consider the Delivery Method
Visibility alerts work well in channels. The goal of these alerts is to improve visibility and awareness, so put them where people can see them!
If sending visibility alerts to a channel, consider if you should leverage an existing channel or create a new dedicated channel.
If a channel is already very active, adding passive alerts to the channel may cause them to be missed or ignored. Creating a dedicated channel with a specific purpose of creating visibility around a specific activity can be more impactful.
Other Best Practices:
Encourage engagement with alerts! Some of these notifications can be learning experiences
If being sent to a channel or GroupDM, use the message body and opening text to tag relevant users