Unified Multi-API Interface for Telephonic Service Flow

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Insurance claim associates face inefficiencies while providing telephonic services due to the need to manually organize information from multiple non-unified and disorganized APIs, leading to visual overlap and distraction during the service flow.

Innovation Solution

A frontend application with a multi-API interface that dynamically renders user interface elements based on the service flow, allowing claim associates to interact with multiple APIs without manual text input, by anticipating and presenting claimant-specific responses, thus minimizing distractions and enhancing the flow of telephonic conversations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If claim associates manually organize information from multiple APIs using conventional software services, then information can be accessed, but visual overlap and distraction occur during telephonic service delivery

Engineering Contradiction:
Improveinformation organizationVSAvoidservice flow continuity
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent combines multiple separate API windows and information displays into a single unified user interface. This integration allows claim associates to access information from multiple non-interoperable APIs (rental management, repair management, claim filing services) without manual window manipulation, eliminating visual overlap while maintaining comprehensive information access during telephonic service delivery.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The unified user interface serves multiple functions simultaneously: displaying claim information, rental vehicle availability, repair facility status, and communication tools in one interface. This multi-functional design eliminates the need for separate windows for each API, allowing claim associates to handle diverse tasks without leaving the unified interface during customer interactions.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Loss of information

If claim associates access multiple non-interoperable hosted service APIs, then comprehensive information can be retrieved, but manual input and window manipulation are required

Engineering Contradiction:
Improveinformation completenessVSAvoidservice efficiency
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically retrieving and organizing information from multiple non-interoperable APIs before the claim associate needs it. The unified interface pre-loads claim details, rental options, and repair facility information, eliminating the need for manual input and sequential API access, thereby reducing service time while maintaining information completeness.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The unified user interface acts as an intermediary layer between claim associates and multiple non-interoperable APIs. It translates and integrates data from different API formats into a consistent presentation, automatically managing information exchange without requiring manual input or window manipulation, thus improving service efficiency while accessing comprehensive information.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of information

If conventional software services spawn separate windows for each API, then information from multiple sources can be displayed, but display space is exceeded and organization becomes complex

Engineering Contradiction:
Improveinformation presentationVSAvoidinterface organization
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent merges multiple separate window displays into a single unified interface that presents information from all APIs in an organized layout. This consolidation eliminates the need for window manipulation and complex spatial organization, fitting all necessary information within the display space while maintaining clear structure and accessibility.

Inventive Principle:
Principle #5Merging (Combining)

4Loss of information

If claim associates focus on manual API management, then information can be accessed, but telephonic conversation quality deteriorates due to distractions

Engineering Contradiction:
Improveinformation accessVSAvoidservice quality
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The unified user interface performs self-service by automatically managing information retrieval and presentation from multiple APIs without requiring continuous manual intervention. This allows claim associates to access needed information passively during telephonic conversations, maintaining conversation quality while ensuring information availability through the system's autonomous information management capabilities.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20240168777A1User interface for telephonic services
Publication Date: 2024.05.23 STATE FARM MUTAL AUTOMOBILE INSURANCE COMPANY
  • US20240168777A1 patent drawing
  • US20240168777A1 patent drawing
  • US20240168777A1 patent drawing

AI summary

In the course of booking a vehicle rental on behalf of the claimant, a claim associate needs to submit a variety of information to multiple private hosted service APIs and public hosted service APIs. Conventionally, the claim associate must request, transcribe, and manually input this information on a client computing system during telephonic services, resulting in substantial silences over the phone call decreasing quality of the claimant's service experience. A multi-API interface is provided, which configures the client computing system to anticipate information which the claim associate will need, based on a type of claimant, to send to multiple APIs, assemble this information from a variety of data records, and present this information to the claim associate, using persistent interface elements and flow control elements allowing the claim associate to review and select information to send to multiple APIs with minimal interruption in the service flow of telephonic services.