Chatbot Event Notification System for Proactive User Assistance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current chatbot systems require user-initiated interactions, limiting their ability to respond proactively to events or conditions generated by software applications, which can lead to missed opportunities for providing timely assistance.

Innovation Solution

Implementing a method where chatbot systems can initiate conversations based on events generated by software applications, using electronic notifications that include user, chatbot, and conversation state information, allowing for automated and context-aware interactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If chatbot conversations are initiated only in response to user input, then the system maintains simple operation and clear user control, but the chatbot cannot proactively respond to events or provide timely assistance

Engineering Contradiction:
Improveproactive response capabilityVSAvoiduser control simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system performs preliminary actions by monitoring events and conditions in the software environment before the user needs assistance. When conditions are satisfied, the chatbot proactively initiates a conversation, anticipating the user's needs before they explicitly request help.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The chatbot system serves itself by automatically detecting events and conditions, determining when user assistance is needed, and initiating conversations without requiring explicit user commands. This self-service capability enables proactive assistance while maintaining operational simplicity.

Inventive Principle:
Principle #25Self-service

2Reliability

If the chatbot system monitors software application events to initiate conversations, then timely assistance can be provided, but the system complexity increases

Engineering Contradiction:
Improvetimely assistance provisionVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system introduces an event notification mechanism as an intermediary between the software application and the chatbot. Software applications publish events to a notification system, which the chatbot subscribes to, creating a decoupled architecture that reduces direct complexity while enabling reliable event monitoring and timely response.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If multiple chatbots are available to handle different tasks, then task specialization improves, but determining which chatbot to invoke becomes more complex

Engineering Contradiction:
Improvetask handling capabilityVSAvoidchatbot selection complexity
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The system extracts the chatbot selection logic from the event notification process. Instead of embedding complex selection algorithms in each event handler, the system separates event monitoring from chatbot invocation, allowing the chatbot system to automatically determine which specialized chatbot should handle each event based on its capabilities and the event type.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11283737B2Application initiated conversations for chatbots
Publication Date: 2022.03.22 ORACLE INT CORP
  • US11283737B2 patent drawing
  • US11283737B2 patent drawing
  • US11283737B2 patent drawing

AI summary

Techniques for described for invoking a chatbot in a chatbot system, in response to an event notification from a software application. The event notification can be sent to the chatbot system based on the software application determining that one or more conditions associated with an event are satisfied. In certain embodiments, the event notification contains information indicating a dialog flow state for starting a new conversation between a particular chatbot and a user. The event notification can also identify the user and/or the particular chatbot. In some instances, a prompt is output to the user requesting the user to confirm a start of the new conversation. Whether the prompt is output or not can depend on whether there is an existing conversation between the user and a chatbot in the chatbot system.