Wait Block

The Wait Block introduces a deliberate pause in the conversation for a specified duration in seconds. This allows you to control the pacing of the interaction, giving users time to absorb information or preparing them for subsequent actions, such as a redirection.

Key Features

• Precise Timing Control: Set exact pause duration in seconds
• Flow Pacing: Create natural conversation rhythm and reading time
• Action Preparation: Build anticipation before important actions
• Processing Time: Allow time for backend operations to complete
• User Experience: Give users time to digest information

Configuration Options

Pausing the Conversation Flow

The Pause the Flow option enables you to insert a pause at a specific point in the conversation flow. By default, the bot processes all blocks between input blocks in sequence. However, enabling this option allows you to display messages or content before executing a time-consuming action, ensuring a smoother user experience.

How It Works

1. Without Pause the Flow: The wait happens silently, and all content appears after the delay
2. With Pause the Flow: Content before the Wait Block displays immediately, then the pause occurs

Example Usage

Building Anticipation

Create suspense before revealing results:

1. Display "Analyzing your responses..."
2. Add a Wait Block for 2-3 seconds
3. Show the personalized results or recommendations

Processing Indicator

Simulate processing time for complex operations:

1. Show "Processing your request..."
2. Wait for 1-2 seconds
3. Display the confirmation or next steps

Reading Time

Allow users to read important information:

1. Present a detailed message or instructions
2. Add a Wait Block (calculate based on text length)
3. Continue to the next interaction

Redirect Preparation

Prepare users before redirecting:

1. Display "You will be redirected in 3 seconds..."
2. Add a 3-second Wait Block
3. Execute the redirect action

Best Practices

• Keep Waits Short: Avoid pauses longer than 5 seconds to prevent user frustration
• Provide Context: Always explain why there is a pause (e.g., "Loading your results...")
• Use Typing Emulation: For natural message pacing, use typing emulation settings instead
• Test User Experience: Verify that wait times feel appropriate during testing
• Consider Mobile Users: Mobile users may have shorter attention spans
• Combine with Loading Messages: Pair waits with status messages to keep users informed
• Avoid Excessive Use: Too many waits can make the bot feel slow and unresponsive