Cross-Channel Pull Notifications for Missed Push Alerts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Customers may miss critical messages, such as real-time fraud prevention alerts, due to intentionally or unintentionally disabling push notifications on their mobile devices.
Innovation Solution
Implementing a system that uses pull notifications and interactions on both web and mobile channels, where messages are stored with a message identifier and displayed during customer login, even if push notifications are disabled, allowing for customer verification and response through mobile applications or browsers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If push notifications are used to deliver messages to customers, then message delivery speed is improved, but message reliability deteriorates when customers disable push notifications
Solution Approach 1:
Instead of pushing notifications to customers' devices (traditional approach), the system inverts the approach by having customers pull/messages retrieve notifications from the server during login. This is implemented through the backend computer program storing messages with message identifiers and providing them to mobile applications or browsers that retrieve and display them, ensuring delivery regardless of push notification settings.
Solution Approach 2:
The patent introduces an intermediary mechanism - the message identifier system - that bridges the gap between the service provider system and the customer's device. The backend computer program acts as a mediator that stores messages, marks devices to receive messages on next login, and provides message identifiers that enable reliable retrieval without depending on push notification capabilities.
2Reliability
If pull notifications are implemented to ensure message delivery, then message reliability is improved, but system complexity increases
Solution Approach 1:
The system segments the message delivery process into distinct functional components: (1) the service provider system that generates messages, (2) the backend computer program that stores messages with unique identifiers and marks devices, (3) the mobile application or browser that retrieves messages using identifiers, and (4) the display component that presents messages to customers. This segmentation allows each component to remain relatively simple while achieving reliable overall delivery.
Solution Approach 2:
The backend computer program performs preliminary actions by pre-storing messages with message identifiers and marking customer electronic devices before the customer actually logs in. This preliminary preparation ensures that when the customer logs in and retrieves messages, the delivery is reliable without requiring complex real-time processing during the login event.
Data Source
AI summary
A method may include: receiving, by a backend computer program and from a service provider system, a message for customer; storing, by the backend computer program, the message with a message identifier for the message; marking, by the backend computer program, a customer electronic device associated with the customer to receive the message on a next customer login on the customer electronic device; receiving, by the backend computer program and from a mobile application or a browser executed by the customer electronic device, a login from the customer; authenticating, by the backend computer program, the customer; confirming, by the backend computer program, that the customer electronic device is marked; and providing, by the backend computer program, the message identifier to the mobile application or the browser; wherein the mobile application or the browser may be configured to retrieve the message using the message identifier and to display the message.