Communication Workflow State Machines for Profile State Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems face challenges in generating and managing communication workflows that automate communication based on user actions and scheduled events, leading to users being mistakenly placed in multiple steps simultaneously, resulting in redundant and irrelevant messages that negatively affect user experience.

Innovation Solution

The implementation of event filters and state machines to map user events to communication workflows, ensuring profile state consistency by preventing simultaneous placement of users in multiple steps, and using a state machine to process events based on predefined conditions and transitions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If automated communication workflows are implemented to send messages based on user actions and scheduled events, then productivity and automation extent are improved, but users may be mistakenly placed in multiple steps simultaneously resulting in redundant and irrelevant messages that worsen user experience

Engineering Contradiction:
Improveautomated communication workflowsVSAvoiduser experience
Core Design Contradiction:
Extent of automationVSReliability

Solution Approach 1:

The system implements feedback mechanisms by continuously monitoring user state and workflow progress, detecting when a user is mistakenly placed in multiple steps simultaneously, and correcting the state to prevent redundant message sending. This feedback loop ensures automated workflows maintain reliability while providing customized communications.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

An intermediary state management layer is introduced between the automated workflow engine and the communication system. This intermediary tracks user progress through workflows, prevents duplicate step placement, and filters out redundant messages before they are sent, thereby maintaining automation benefits while eliminating harmful duplicate communications.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple communication workflows are executed simultaneously based on different user actions, then adaptability and customization are improved, but system complexity and difficulty of managing profile state consistency increase

Engineering Contradiction:
Improvecustomized communicationsVSAvoidprofile state consistency management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the complex state management problem into independent, manageable components by creating separate state tracking mechanisms for different workflows. Each workflow maintains its own state context, and an orchestrator coordinates between them, allowing multiple customized workflows to run simultaneously without creating unmanageable complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces a new dimensional layer of abstraction by implementing a hierarchical state management structure with workflow-level and step-level states. This multi-dimensional state organization allows the system to track user progress across multiple simultaneous workflows independently, reducing the complexity of managing profile state consistency while maintaining high adaptability.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS20250217210A1Generation and management of communication workflows using profile state consistency approach
Publication Date: 2025.07.03 TWILIO INC
  • US20250217210A1 patent drawing
  • US20250217210A1 patent drawing
  • US20250217210A1 patent drawing

AI summary

Various embodiments described herein support or provide operations including detecting an event associated with an entity; determining that the event is mapped to a journey that comprises a plurality of steps configured by the entity; placing the entity in a current step in the journey; evaluating one or more factors to determine that the entity is not simultaneously placed in another step of the journey; and using a state machine to process the event based on an operation associated with a step subsequent to the current step in the journey.