Feedloop AI
  • GETTING STARTED
    • Discover Feedloop AI
    • Authentication
      • Sign Up
      • Login
    • Platform
      • Workspace
      • Project
      • People
      • Usage
  • WHAT IS AGENT
    • What is Agent
      • ⚪Manage Agent
    • Basic Agent
      • ⚪Instruction
        • Who
        • What
      • ⚪Training
        • Rules
        • Example
      • ⚪Skill
        • Knowledge
        • Analys
      • ⚪Style
    • Procedures
    • Advance Reasoning
      • ⚪Creating New Agent
      • ⚪Advance Agent Activation
      • ⚪Deleting Agent
      • ⚪Advance Agent Managing Existing
  • AGENT SETTINGS
    • Instruction
      • Who
      • What
      • Additional Instruction
    • Training
      • Chat Rules
      • Retrieval
      • Answering
    • Context
      • Primitive Context
      • Array
    • Tools
      • Knowledge
      • API - Call
        • Manage API Call
        • Basic Configuration
        • Header
        • Body Field
          • Input Binding
            • Page 2
          • Output Binding
        • Testing API Call
        • Trouble Shooting
        • Example Implementation
          • API Call Covid
      • Data Connector
    • Card
      • Intro & Summary Text
      • Data Visualization Card
      • Analyze Card
    • Procedure Basic Info
      • Activation Condition
      • Goal
      • Action
    • Procedures Interaction
      • Procedures Step
      • Procedures Context
      • Procedures Tools
  • AGENT UTILITY
    • Resource
      • Document PDF
        • Preparing your PDF
      • Data Connector
        • Create new data connector
        • Configure dataset, table, and column
        • Using Data Playground
        • Dataset in Data Playground
        • Training in Data Playground
        • SQL generation and modification
        • SQL Execution
    • Apps
      • Chat Widget
      • Web App
    • Testing
    • Monitoring
      • Customer Chat
      • Context
      • Document
  • TASK
    • ⚪Image Analyzer
      • Building Analyzer
      • ID Identifier
    • ⚪Document Analyzer
      • Contractual Document Analyzer
    • ⚪Database Analyzer
    • ⚪Additional Solution
      • Text Sentiment Analyzer
      • Customer Complaint Analyzer
  • For Developer
    • API Chat
      • Chat Initialization
      • Chat Message
      • Chat History
      • Error Handling
    • Embed Widget
      • Embedding the Widget
      • Identity Attributes
      • Widget Attribute Details
Powered by GitBook
On this page
  • Logic
  • Description Section
  • Purpose
  • How to Configure
  • Start Condition Section
  • Purpose
  • How to Configure
  • Key Considerations for Start Conditions
  1. AGENT SETTINGS
  2. Procedure Basic Info

Activation Condition

PreviousProcedure Basic InfoNextGoal

Last updated 6 months ago

Activation Condition defines the specific trigger that initiates a procedure.Configuring the activation condition ensures that the procedure starts only when the defined conditions are met.


Logic

Activation Condition Logic - How it works
  • Activation Logic: The procedure shall activate only when the specified start condition is met. This ensures that the procedure aligns with the user's input or system events and triggers at the right time.

  • If the start condition is not met, the procedure remains inactive. Once the condition is fulfilled, the system initiates the procedure and continues with the subsequent steps in the workflow.

  • The start condition logic ensures that the procedure fits seamlessly into the larger workflow, preventing it from being triggered prematurely or in unintended scenarios.

Description Section

Purpose

The Description field provides an overview of the procedure.

How to Configure

  1. Click Edit: Click the Edit button next to the description field.

  2. Enter the Description: Clearly describe the purpose and functionality of the procedure. This could outline what the procedure is meant to achieve within the user journey or system workflow. Example: If the procedure is for handling support tickets, you could write: This procedure is designed to guide the user through submitting a support ticket, ensuring that all necessary information is collected and routed to the appropriate team.

  3. Save Changes: After modifying the description, click Save to apply the changes.


Start Condition Section

Purpose

The Start Condition determines when the procedure will automatically start. It ensures that the procedure is triggered based on specific user actions or system events.

How to Configure

  1. Click Edit: Click the Edit button next to the Start Condition field.

  2. Define the Start Condition: In the Start Condition field, specify the condition or event that triggers the procedure. This could be based on user input, a system event, or any predefined condition.

    • Example: For a procedure related to booking appointments, you could enter procedure starts when the user wants to submit a claim and provides the necessary claim details (e.g., item description, date of purchase, reason for claim).

  3. Save Changes: Once you’ve defined the start condition, click Save to ensure your changes are applied.


Key Considerations for Start Conditions

  • Make sure the condition is clear and specific to avoid incorrect triggers.

  • Test the start condition to verify it aligns with the intended workflow.

  • Update the condition if the user’s interaction flow changes over time.


Edit Description
Input Description
Edit Start Condition
Input Start Condition