Contextual Notification System for Streamlined Service Requests

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional network-based services face inefficiencies in user engagement due to unnecessary notifications, cluttered user interfaces, and wasteful use of network and processing resources, particularly on mobile devices with limited screen real estate, as users are often forced to navigate through multiple menus to submit service requests.

Innovation Solution

A network system that generates contextual notifications based on user behavior and preferences, determining the likelihood of user interaction within a given time window, and transmits notifications only when the user is likely to submit a service request, using actionable push or in-app notifications that pre-populate request interfaces for streamlined submission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If conventional network services send notifications to all users regardless of engagement likelihood, then user coverage is maximized, but network resources and processing power are wasted

Engineering Contradiction:
Improvenetwork and processing resourcesVSAvoiduser engagement efficiency
Core Design Contradiction:
Loss of energyVSEase of operation

Solution Approach 1:

The system performs preliminary analysis of user behavior patterns and engagement likelihood before sending notifications. By pre-calculating which users are likely to engage with service requests, the system avoids wasting network and processing resources on users who would not interact anyway, while still maintaining effective user engagement channels for those who will respond.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically changes the notification sending parameter from a binary approach (send to all or send to none) to a probabilistic approach based on user engagement likelihood. By adjusting the notification sending decision based on calculated metrics of user behavior patterns, the system optimizes resource usage while maintaining engagement effectiveness.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If notifications are sent frequently to all users, then user awareness of the service is maintained, but user interfaces become cluttered and experience deteriorates

Engineering Contradiction:
Improveservice awarenessVSAvoiduser interface cleanliness
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system extracts and filters out users who are unlikely to engage with service requests from the notification distribution list. By separating the user base into engaged and non-engaged segments, the system sends notifications only to the relevant subset, maintaining service awareness among active users while keeping the user interface clean and free from unnecessary notifications.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of sending notifications to all users (excessive action), the system sends notifications only to the partial subset of users who are likely to engage. This partial action approach maintains sufficient service awareness among the target audience while avoiding the clutter and negative user experience that would result from universal notification delivery.

Inventive Principle:
Principle #16Partial or excessive action

3Adaptability or versatility

If users must navigate through multiple menus to submit service requests, then comprehensive service options are presented, but time to submit requests increases

Engineering Contradiction:
Improveservice request optionsVSAvoidrequest submission time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system pre-populates service request fields with user profile information and previously selected options when notifications are sent to engaged users. By having this information ready in advance, users can submit service requests with minimal navigation and input, significantly reducing submission time while still maintaining access to comprehensive service options through the pre-configured interfaces.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10575123B1Contextual notifications for a network-based service
Publication Date: 2020.02.25 UBER TECHNOLOGIES INC
  • US10575123B1 patent drawing
  • US10575123B1 patent drawing
  • US10575123B1 patent drawing

AI summary

A network system can transmit notification data to a user device to cause the user device to present a contextual notification that can remind the user to interact with the network-based service. The notification data can be selectively transmitted and the notification can be selectively presented based on a determined likelihood of the user submitting a service request within a given time period. A metric representative of such a likelihood can be determined for the user based on historical data associated with the network-based service. The metric can be compared against one or more threshold values. In response to a user interaction with the notification, the user device can present a request user interface for a streamlined and simplified user experience in submitting a service request.