Bot Search Interface Pre-displaying Stored User Consent
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for managing access to bots, such as chatbots, require users to repeatedly enter identifiers and provide consent, making the process tedious and not user-friendly, while also needing to ensure compliance with GDPR regulations.
Innovation Solution
A method where a bot search interface on a user's terminal stores the identifier and consent during the first access, allowing for pre-display and confirmation during subsequent accesses, facilitating user interaction with bots without re-entering information and ensuring GDPR compliance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If users are required to enter identifier and provide consent each time a bot is launched, then GDPR compliance is ensured, but user convenience deteriorates
Solution Approach 1:
The system performs preliminary actions by storing the user's identifier and consent during the first access. During subsequent accesses, the pre-stored information is automatically retrieved and used, eliminating the need for repeated entry while maintaining GDPR compliance through persistent valid consent records.
2Ease of operation
If user identifier and consent are stored for subsequent accesses, then user convenience is improved, but data security requirements increase
Solution Approach 1:
The system creates a copy of the user's identifier and consent information and stores it locally on the terminal. This copy can be automatically reused during subsequent bot launches without requiring the user to re-enter data or re-authenticate, thereby improving convenience while maintaining security through controlled local storage.
3Loss of time
If the system stores user-specific information locally, then repeated data entry is eliminated, but storage requirements and data management complexity increase
Solution Approach 1:
The system extracts only the essential user-specific information (identifier and consent indication) needed for bot access and stores it locally. This minimal data extraction approach reduces storage requirements and simplifies data management complexity while still eliminating the need for repeated data entry during subsequent accesses.
Data Source
AI summary
Method for managing access to a plurality of bots, in which the following are performed by a search interface run on a first terminal. During a first access by a user to the search interface: receiving an identifier associated with a target mobile terminal and an indication of the user's consent; storing, on the first terminal, the identifier associated with the target mobile terminal and the indication of consent; and receiving a request to launch a lookup operation with a view to selecting a bot and opening a conversation between the latter and the target mobile terminal. The method includes during a subsequent access: pre-displaying the stored identifier and indication of consent; and receiving a new request to launch the lookup operation with a view to selecting a new bot and opening a conversation between the latter and the target mobile terminal.