Context-Aware Support Interface for Service Grievance Reporting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current service provider systems overwhelm users with numerous support options, complicating the reporting of service-related issues and leading to negative experiences.

Innovation Solution

A server provides a customized support interface to users based on their specific service experiences, tailoring the interface with relevant support categories to simplify issue reporting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a standard support interface with all support options is provided to users, then comprehensive support coverage is achieved, but user complexity and difficulty in finding relevant options increases

Engineering Contradiction:
Improvesupport coverageVSAvoidinterface complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The support interface is segmented into context-relevant portions based on the user's current service experience. Instead of presenting all possible support options, the system divides the support menu into segments showing only those options related to the user's recent events, such as payment issues, delivery problems, or service complaints, thereby reducing interface complexity while maintaining comprehensive support coverage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The support interface applies local quality by customizing the displayed options according to the specific context of each user's experience. Different users receive different support menus based on their individual event histories, ensuring that each user sees high-quality, relevant support options rather than a generic comprehensive list.

Inventive Principle:
Principle #3Local quality

2Device complexity

If a generic support interface is provided to all users, then system simplicity is maintained, but user satisfaction decreases due to irrelevant options

Engineering Contradiction:
Improvesystem simplicityVSAvoidissue reporting ease
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The system performs preliminary action by analyzing the user's service experience and pre-filtering support options before the user even requests help. The server examines recent events in the user's history and prepares a customized support menu in advance, so when the user needs assistance, they immediately see relevant options without having to search through generic categories.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses feedback from the user's service experience data to dynamically adjust the support interface. By monitoring events such as completed deliveries, payment transactions, and previous support interactions, the system feeds this information back into the interface generation process to personalize the support options presented to each user.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10740856B2Dynamic support information based on contextual information
Publication Date: 2020.08.11 UBER TECHNOLOGIES INC
  • US10740856B2 patent drawing
  • US10740856B2 patent drawing
  • US10740856B2 patent drawing

AI summary

A server provides a customized support interface to a user that is requesting assistance regarding a service that the user received. The server provides a support interface that is customized for the user based on data related to the service and the user's past behavior. By providing a customized support interface, the user is more easily able to report any grievances that the user may have had with the service thereby reducing any further user aggravation.