Notifications and alerts are triggered upon logging back into the product. It would appear in the home screen and contain a generic message about various issues throughout the application. These notices would be more actionable if they were closer to the source.
A user logs into the product from the browser application. At the moment of logging in, the engine does a quick check for any changes or issues that the user should be notified about. The alert appears on the home screen for a few seconds or until clicked.
DURATION: APPROXIMATELY 3 MONTHS
This is an example of the home screen after a user has just finished logging into the browser application. A quick check for statuses and issues related to the product triggers an alert message that appears as a banner in the top the page.
WHAT WE CHANGED
By identifying the types of records customers are looking for earlier in the process, then guiding them through the rest of the flow, the results sets seemed to be more accurate. This was concluded by the up-tick in conversion rates compared to an A/B test that lasted about 3 months after implementation.
Silicon Valley, California USA