Videoconferencing Policy Engine for Chat Clutter and Missed Tasks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern videoconferencing applications face challenges in managing chat channels with high unread message counts, missed messages, and inactive channels, as well as difficulties in scheduling and managing video conferences and calendars, leading to user interface clutter and missed important tasks.

Innovation Solution

Implementing policies on a video conference provider's policies engine for remote management of chat channels, video conferences, and calendars, including conditions and actions such as hiding inactive channels, reminding participants to record meetings, and notifying users of conflicting calendar events.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If users manually monitor and manage chat channels, video conferences, and calendars, then they can control their own tasks, but it becomes cumbersome and time-consuming, leading to missed tasks and interface clutter

Engineering Contradiction:
Improveautomation of task managementVSAvoidcomplexity of management system
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system enables self-service automation where users define policies once and the system automatically executes them. Users create conditions (e.g., channel inactivity thresholds, meeting duration criteria) and actions (e.g., hide channel, send reminder), then the system autonomously monitors and responds without continuous user intervention, reducing manual workload while maintaining user control over automation rules.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Users prepare management rules in advance by defining policies before the actual tasks occur. The system stores these pre-configured policies and automatically executes them when conditions are met, eliminating the need for real-time manual monitoring and decision-making. For example, users pre-set policies to automatically hide inactive channels after a threshold period, so no manual action is needed when inactivity occurs.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If the user interface displays all chat channels and messages, then users can access all information, but it causes interface clutter and makes it difficult to find important content

Engineering Contradiction:
Improveease of finding important contentVSAvoidnumber of visible channels and messages
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The system extracts and separates important management functions from the main user interface. Instead of displaying all channels and messages at once, the system automatically identifies and hides inactive channels, sends notifications about important events, and manages calendar conflicts in the background. This extraction reduces the visible information load while preserving access to important content through targeted notifications and selective display.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If users manually check for missed tasks and conflicts, then they can ensure nothing is overlooked, but it consumes time and leads to missed important tasks

Engineering Contradiction:
Improvereliability of task completionVSAvoidtime spent on manual checking
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system continuously monitors task status, meeting schedules, and calendar events, then provides automated feedback to users through notifications. When conditions are met (e.g., a meeting is about to start, a channel becomes inactive, a conflict is detected), the system sends timely alerts to inform users of relevant events, ensuring they don't miss important tasks without requiring manual checking. This feedback loop maintains reliability while minimizing time investment from the user.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12382000B2Remote management of videoconferencing applications
Publication Date: 2025.08.05 ZOOM COMMUNICATIONS INC
  • US12382000B2 patent drawing
  • US12382000B2 patent drawing
  • US12382000B2 patent drawing

AI summary

One example method for providing remote management of videoconferencing applications includes receiving, by a computing device, from a first client device, a first indication to generate a first policy, wherein the first policy comprises one or more conditions relating to a first application and one or more actions to be taken. The computing device may receive one or more indications associated with the first application and determine, based on the one or more indications, whether any of the one or more conditions has occurred. The computing device may, responsive to determining that a first condition of the one or more conditions has occurred, cause one or more actions corresponding to the first condition to be executed.