Skip to main contentMessage Flow Examples
Example 1: Simple Collaboration
User Message: "@product @engineering work together on user authentication"
Event Sequence:
NOTIFICATION_REQUEST_ORCHESTRATION_COLLABORATION_REQUEST - System detects collaboration
NOTIFICATION_PLAN_ORCHESTRATION_COLLABORATION_PLANNING_INITIATED - Planning begins
NOTIFICATION_PLAN_ORCHESTRATION_COLLABORATION_PLANNING_COMPLETED - Planning complete
NOTIFICATION_MULTI_ASSISTANT_COLLABORATION_STARTED - Collaboration session starts
- Contains: collaborationId, list of @product and @engineering agents
NOTIFICATION_MULTI_ASSISTANT_COLLABORATION_ASSISTANT_RESPONSE_IN_PROGRESS - @product starts responding
NOTIFICATION_MULTI_ASSISTANT_COLLABORATION_ASSISTANT_RESPONSE_COMPLETED - @product finishes
NOTIFICATION_MULTI_ASSISTANT_COLLABORATION_ASSISTANT_RESPONSE_IN_PROGRESS - @engineering starts responding
NOTIFICATION_MULTI_ASSISTANT_COLLABORATION_ASSISTANT_RESPONSE_COMPLETED - @engineering finishes
NOTIFICATION_MULTI_ASSISTANT_COLLABORATION_UNIFIED_RESPONSE_STARTED - System synthesizes responses
NOTIFICATION_MULTI_ASSISTANT_COLLABORATION_COMPLETED - Collaboration complete
Example 2: No Unified Response Required
User Message: "@support help @sales with this customer issue"
Event Sequence:
NOTIFICATION_REQUEST_ORCHESTRATION_COLLABORATION_REQUEST
NOTIFICATION_PLAN_ORCHESTRATION_COLLABORATION_PLANNING_INITIATED
NOTIFICATION_PLAN_ORCHESTRATION_COLLABORATION_PLANNING_COMPLETED
NOTIFICATION_MULTI_ASSISTANT_COLLABORATION_STARTED
NOTIFICATION_MULTI_ASSISTANT_COLLABORATION_ASSISTANT_RESPONSE_IN_PROGRESS - @support responds
NOTIFICATION_MULTI_ASSISTANT_COLLABORATION_ASSISTANT_RESPONSE_COMPLETED - @support done
NOTIFICATION_MULTI_ASSISTANT_COLLABORATION_ASSISTANT_RESPONSE_IN_PROGRESS - @sales responds
NOTIFICATION_MULTI_ASSISTANT_COLLABORATION_ASSISTANT_RESPONSE_COMPLETED - @sales done
NOTIFICATION_MULTI_ASSISTANT_COLLABORATION_NO_UNIFIED_RESPONSE_REQUIRED - Individual responses sufficient
NOTIFICATION_MULTI_ASSISTANT_COLLABORATION_COMPLETED