Max also provides default mobile notifications for Contract Management flow to alert you of important milestones, stages in contract negotiations and offers context-specific quick action links to act on them. Notifications are stored in a custom object, Conga Event. Notifications are delivered to you using Conga Events and contain more information about the event, link to navigate to the contextual object, and a quick action button to launch Max.
The following table describes the types of notifications supported by Max and the quick action links provided for each of them.
Type of Notification
Event Notifications are triggered immediately. They alert you about the change in the status of your contract and provide quick action links to take immediate actions to advance the deal.
Agreement stage changes to Ready for Signatures
Send for Signature
Agreement state moves to Approved Request
Send for Review
Agreement state changes to Approval Required
Submit for Approval
Review Cycle is Cancelled / Completed
Reminder Notifications alert you about inactivity in the contract and provide the contact information of the current owner to get in touch about advancing the deal.
Get in touch with the current owner
Upcoming Event Notifications
Upcoming Event Notification alert you about upcoming contract milestones and suggest proactive actions to get you in front of customer interactions.
NDAs expiring in the next month.
MSAs expiring in the next 3 months.
With each notification, the user will be provided with contextually relevant follow-up actions, that they can immediately use to take the next step and advance the negotiation or deal in progress. Follow-up actions are categorized as follows:
- Quick Actions: Actions such as send for review, send for signature, submit for approval are examples of quick actions.
Get-in-Touch Actions: Actions such as calling the customer or sending emails to customers are examples of Get in Touch Actions. Get in touch actions are related to Reminder Notifications only. They involve quick links for you to call your customer or send a pre-composed email to relevant stakeholders. These actions are useful in scenarios where you are waiting for inputs from someone else. For example, pending review cycles or pending approvals.
Notification Quick Actions: These actions are provided by default with every notification. They involve handling the notification, especially when you cannot interact with the notification immediately. Notification quick actions are of two types:
- Snooze - You can snooze the notification by clicking the Snooze button or by asking Max to snooze the notification using natural language commands. The notification is snoozed for 15 minutes.
- Dismiss - You can dismiss the notification clicking the Dismiss button or by asking Max to dismiss the notification using natural language commands. When you dismiss a notification, the notification is removed from the notification queue.
Mobile notifications are available for you on multiple channels enabled by Max administrator using the Notification Control Center. Currently, Notifications are supported on Slack, Teams, and Salesforce1 Mobile App.
Triggered notifications are delivered when you sign-in, end a conversation, or you have been inactive for longer than two minutes. For Salesforce1 mobile app, you will receive the notification using your Salesforce's native notification mechanism and the follow-up actions are performed using the conversational interface of Max.