Cross-Vendor Support Platform with Segmented Knowledgebases

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current customer support systems lack efficient mechanisms for providing cross-vendor support services, proactive support, and cost-effective communication channels, particularly in mobile technologies, and struggle with sharing knowledge across multiple vendors without compromising confidentiality.

Innovation Solution

A support center system that uses a one-touch application on mobile devices to register products via machine-readable codes, providing access to multiple communication channels and a knowledgebase, while ensuring confidentiality by isolating client-specific information and enabling proactive support through touch plans that identify related product changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a support center handles support services for multiple vendors' products, then the versatility and scope of support services is improved, but the complexity of managing multiple knowledgebases and ensuring information security increases

Engineering Contradiction:
Improvesupport service scopeVSAvoidknowledgebase management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the knowledgebase into multiple isolated instances, one for each vendor. Each knowledgebase is separately managed and accessed only by authorized agents, eliminating the complexity of managing a single large multi-vendor knowledgebase while maintaining versatile support capabilities across multiple vendors.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary layer (the support center platform) that mediates between multiple vendor knowledgebases and customer support agents. This intermediary manages the complexity of knowledgebase access control, authentication, and information routing, allowing agents to access only their authorized vendor's knowledgebase while the system handles the overall coordination.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If customer support systems share knowledge across multiple vendors, then the efficiency and productivity of support services is improved, but the risk of exposing confidential vendor information increases

Engineering Contradiction:
Improvesupport service efficiencyVSAvoidinformation security risk
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The knowledgebase is segmented into separate isolated instances for each vendor, eliminating the security risk of cross-vendor information exposure. Each vendor's confidential information remains contained within their own knowledgebase instance, accessible only to authorized agents while maintaining efficient support operations within each vendor's domain.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system applies different access control policies to different knowledgebases based on their vendor-specific security requirements. Each knowledgebase has its own authorization rules and access permissions tailored to its specific security needs, allowing efficient information sharing within each vendor's ecosystem while maintaining strict security boundaries between vendors.

Inventive Principle:
Principle #3Local quality

3Device complexity

If manual product registration processes are used, then the system complexity is reduced, but the time consumption and customer effort increase

Engineering Contradiction:
Improvesystem complexityVSAvoidproduct registration time
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The system enables automated self-service product registration where customers can independently register their products through the support center platform without requiring manual agent assistance. This automation significantly reduces registration time and customer effort while the system manages the complexity of processing and integrating product information across multiple vendor knowledgebases.

Inventive Principle:
Principle #25Self-service

4Device complexity

If traditional communication channels are used for customer support, then the system complexity is minimized, but the effectiveness and customer satisfaction decrease

Engineering Contradiction:
Improvecommunication system complexityVSAvoidsupport effectiveness
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The support center platform provides universal multi-functional communication capabilities, allowing customers to access support through multiple channels (voice, video, chat, email) within a single integrated system. This multi-functionality improves support effectiveness and customer satisfaction by allowing customers to choose their preferred communication method while the system manages the complexity of coordinating multiple communication protocols and channels.

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

Data Source

PatentUS9990635B2Methods for providing cross-vendor support services
Publication Date: 2018.06.05 TTEC HOLDINGS INC
  • US9990635B2 patent drawing
  • US9990635B2 patent drawing
  • US9990635B2 patent drawing

AI summary

An analysis is performed on first and second product information to determine a relationship between a first product and a second product. In response to a first notification from a first backend system, a first message is transmitted to a mobile device of the user indicating that the change of a first activity is needed. It is determined whether a modification of a second activity is needed based on the relationship information of the first product and the second product and in response to determining that the modification of the second activity is needed, a second message is transmitted to the mobile device, indicating a possible modification of the second activity and offering a list of one or more options to modify the second activity. A live communications session is established between the user and a support agent of the server to discuss the possible modification of the second activity.