Admin Rights Required
Any configuration within this article can be handled only by Chili Piper Admins. You will also need an Admin from Slack's side.
Slack notifications can be used in Chat by adding the 'Send a Slack Notification' node in your Journeys at various points to notify the team of new visitors wanting to chat or other alerts the team should be aware of.
Below, we will cover how to set up Slack notifications, the required permission scope, and what to expect from them.
How to Setup?
To set up the integration, you will first need your Slack admin to connect Slack via the Integrations page in the Admin Center (please note that this user also needs to be an Admin at Chili Piper to be able to access the Admin Center):
Permission Scope
Once the status shows "Connected", a new Slack app will be added to your org called ChiliBot. You can view the scope/permissions required here and also in the screenshot below:
How will the notifications be sent?
Any notifications that come from Chili Piper will be sent via ChiliBot.
In your Journeys, when adding a "Send a Slack Notification" node, if you are using the "Send to Channel" option, you must ensure that @chilinbot is added to the channel before going live if the channel is private. You can do this by @ mentioning the bot in the channel and inviting it to join when the prompt appears:
You are now ready to start using the Slack integration in your Journeys:
Which Notifications Are Sent?
By default, without requiring any additional configuration besides the one mentioned in this article, we send the following notifications:
Meeting Booked through Chat
If a meeting is scheduled through one of your Chat Journeys, the assignee will receive a Slack notification like this:
Chat conversation reassigned
If a Chat conversation gets reassigned, the new assignee receives a notification like this:
You can also have a "Send Slack Notification" node in your Chat Journey to be notified on certain situations. Click here to learn more!