Natural Pacing
Introduce realistic delays between messages so the conversation unfolds at a comfortable, human-like speed instead of firing all at once.
Pause & Delay Node
Natural Chat Workflow Timing
The Pause node introduces a configurable delay between workflow steps, giving your automated conversations a natural, human-like rhythm. Show a typing indicator while visitors wait, and ensure they have time to read each message before the next one arrives.
- No credit card
- 14-day free trial
- UK hosted
- Visual builder
What Is the Pause & Delay Node?
The Pause node introduces a timed delay between two steps in your chat workflow. When the workflow reaches a Pause node, it waits for a configurable duration — anywhere from 0.5 to 30 seconds — before advancing to the next step. During this interval a typing indicator (the familiar animated dots) is displayed in the chat widget, signalling to the visitor that a response is being prepared.
Without pauses, every message in an automated workflow fires instantaneously. The result is a wall of text that appears in a single frame — unnatural, overwhelming, and immediately recognisable as a bot. The Pause node solves this by simulating the thinking and typing time a real person would take, transforming a mechanical script into a conversation that feels genuinely human. It is one of the simplest modules in the builder, yet its impact on visitor engagement and trust is profound.
Typing Indicators
Display animated typing dots during the pause, giving visitors a visual cue that a response is on its way and keeping them engaged.
Reading Time
Give visitors enough time to read longer messages before the next one appears. Essential after detailed instructions or multi-line content.
Human-Like Flow
Create a cadence that mirrors how a real support agent would type — short pauses after brief replies, longer pauses after detailed explanations.
How the Pause Node Fits Into a Workflow
The Pause node is placed between any two workflow steps where you want a deliberate gap. The most common position is between consecutive Message nodes — for example, a greeting followed by a question. Place a one- to three-second pause in between and the visitor sees the first message, watches the typing indicator animate briefly, and then receives the follow-up. The effect is subtle but powerful: it transforms a scripted blast of text into what feels like a real-time conversation.
You can also use the Pause node before a Button Group to give visitors a moment to absorb context, before a Human Chat handoff to build anticipation, or after a Collect Info step to simulate processing time. Because the Pause node doesn't collect or send any data, it adds zero complexity — just drag it between two steps and set the duration. The workflow engine handles the rest, including displaying the typing indicator and resuming execution once the timer expires.
Example: Onboarding Flow with Natural Rhythm
A SaaS platform uses Pause nodes between messages to create a relaxed, conversational onboarding experience.
START
Pause
1.5 s delay
Pause
2 s delay
Step-by-Step Breakdown
- Welcome Message: The first Message node greets the visitor by name if available. It sets a warm, personal tone from the very first second.
- Short Pause (1.5 s): A brief pause with a typing indicator gives the visitor a moment to read the greeting before the next message appears. It feels like the agent is typing a follow-up.
- Follow-up Message: A second Message explains the purpose of the conversation. Because of the pause, it arrives naturally — not as part of a single dump of text.
- Longer Pause (2 s): A slightly longer pause gives the visitor time to absorb the context before being asked to make a choice.
- Button Group: The visitor selects an onboarding path. By this point the conversation feels relaxed and guided, not rushed or robotic.
Best Practices & Tips
The Pause node is deceptively simple — a single timer setting. But how and where you use it makes the difference between a workflow that feels alive and one that feels mechanical. Follow these guidelines for the best results.
Match Pause to Message Length
Short, single-sentence messages need only a 1–2 second pause beforehand. Longer, multi-line messages deserve 3–5 seconds so the visitor has time to read everything before the next step lands. A good rule of thumb: roughly one second per line of text in the preceding message.
Don't Over-Pause
Too many long pauses make the conversation feel sluggish and test the visitor's patience. Keep individual delays under five seconds in most cases, and avoid placing more than two or three consecutive Pause-then-Message sequences without an interactive step like a Button Group or Collect Info.
Use Typing Indicators
Always keep the typing indicator enabled (it's on by default). A pause with no visual feedback looks like the chat has stalled. The animated dots reassure visitors that something is happening and dramatically reduce early abandonment during automated flows.
Place Before Important Messages
Insert a pause before key moments — a pricing reveal, a confirmation, or a handoff announcement. The brief gap creates a micro-moment of anticipation that draws the visitor's attention and makes the following message feel more significant.
Frequently Asked Questions
What's the maximum pause duration?
You can set a pause anywhere from 0.5 seconds to 30 seconds. For most conversational use-cases, a duration between 1 and 5 seconds strikes the best balance between feeling natural and keeping the visitor engaged. Anything above 10 seconds is best reserved for special situations like simulating a processing step.
Does the visitor see a typing indicator during the pause?
Yes. By default the Pause node displays an animated typing indicator (three bouncing dots) in the chat widget while the timer is running. This gives visitors a visual cue that a response is being prepared, which prevents them from thinking the chat has frozen or disconnected. You can disable the indicator in the node settings if needed.
Can I chain multiple pauses together?
Technically yes — you can place Pause nodes back-to-back and their durations will run consecutively. However, this is rarely recommended. A single pause with a longer duration achieves the same effect without cluttering your workflow canvas. Multiple pauses are better used when separated by Message or interaction nodes to build a natural conversational cadence.
Does it slow down the overall experience?
A well-configured Pause node actually improves the perceived experience rather than slowing it down. Research shows that users perceive conversations with natural pacing as faster and more helpful than instant message dumps, even though the total elapsed time is longer. The key is moderation — short, purposeful pauses feel natural, while excessive delays feel frustrating.
Related Modules
The Pause node works best alongside these modules to create polished, naturally paced conversational workflows.
Add Natural Timing to Your Workflows Today
Drop a Pause node between your messages and watch your automated conversations come alive. No code, no complexity — just set the duration and publish.