FlowsCards

Wait Card

Insert a wall-clock pause between two cards for natural pacing - no user input, no retries

The Wait card adds a fixed pause between any two cards in your flow. Pick a duration between 5 seconds and 30 minutes, and the run holds for that long before it continues. The contact gets natural pacing instead of three messages in a burst.

Wait card on the canvas between two text cards

No user input cancels the pause. There are no retries and no nudges.

This card is available on Standard, Pro, and Enterprise plans. Free orgs see it greyed out in the palette with an upgrade hint.

Where It Lives

  • Logic category in the card palette, next to Wait Timeout.
  • Hourglass icon.
  • Anywhere between two cards. Two wirings are blocked, see Connection Rules.

Wait vs Wait Timeout

The two cards share a palette icon but solve different problems. To make the bot feel less spammy, use Wait. To escalate when a contact goes silent, use Wait Timeout.

WaitWait Timeout
What it doesStatic pause between two of your own messagesReply deadline on a question / button / list card
Cancelled by user input?No - wall-clock onlyYes - incoming message cancels the deadline
Duration range5 s – 30 min60 s – 30 days
Retries / nudges?NoYes - re-send the prompt or a custom nudge
Where it goes in the flowAnywhere, between any two cardsMust follow an input-accepting card
Plan tierStandard, Pro, EnterprisePro, Enterprise

Configure the Card

The Wait card has one setting: how long to pause.

Wait card settings panel with the Pause duration field in seconds
SettingDescription
Pause durationA number of seconds, from 5 to 1800 (30 minutes). The panel shows Any value between 5 and 1800 seconds.

A new card starts at 10 seconds. The canvas footer shows the duration in its most compact form, such as 5s, 1m 30s or 15m.

Connections

The Wait card has one input and one output. The input is the card that fires before the pause. The output is the card that fires after it. The Wait card sends nothing to the contact.

Text - "Hi {{contact.first_name}}!"
   │
   ▼
Wait - 5 s
   │
   ▼
Text - "Quick question for you…"
   │
   ▼
Question - "What brings you here today?"

Connection Rules

The publish validator blocks two wirings. Both show an inline warning on the canvas before you publish.

PatternWhy it's blocked
Wait → WaitMeaningless. Combine the two into one longer pause - the canvas suggests this on hover of the warning.
Wait → Wait TimeoutWait Timeout requires an input-accepting predecessor (Question, Buttons, AI Classification, etc.) so it has something to deadline. A Wait card produces no input. Put a real input card between them, or remove the Wait.

The reverse direction, Wait Timeout → Wait, is allowed on both the reply path and the timeout path. Use it when the deadline branch needs to pace its fallback messages.

Common Patterns

Natural Pacing Between Messages

Let each message breathe instead of sending a wall of text.

Text  "Welcome to Wexio 👋"
  → Wait (5 s)
  → Text  "I'm here to help you set things up."
  → Wait (5 s)
  → Text  "Want to get started, or just look around?"
  → Buttons  [Get started] [Look around]

Beat After AI Before Follow-Up

Send the AI answer, then give the contact a moment to read it. Without the Wait, the follow-up lands on top of the AI reply.

AI Text  (generates a thoughtful answer)
  → Wait (5 s)
  → Text  "Anything else I can help with?"

Queue Throttle Before Operator Handoff

Let the bot greet the contact and hold for 10 s so the on-shift team isn't hit all at once, then hand off.

Text  "Let me connect you with someone…"
  → Wait (10 s)
  → Assign Operator

Per-Branch Pacing After Buttons

Use a different beat per branch to match the tone of the response. The Wait card sits on each branch independently.

Buttons - "Still interested?" [Yes] [No]
   │
   ├─ Yes ─▶ Wait (5 s)  ─▶ Text "Great! Let me show you."
   │
   └─ No  ─▶ Wait (10 s) ─▶ Text "No problem, catch you later."

Picking a Duration

DurationFeels like
5 sMinimum - a real person catching their breath between messages
5–10 s"They're thinking" - good after a complex question
10–15 sQueue throttle, AI generation cover
30 sCustomer rereads the previous message, no rush
1–5 minPacing inside a longer onboarding sequence
30 minMaximum - for slow drips that span a coffee break

For pauses longer than 30 minutes, use a Broadcast or a Scheduled Trigger. Those tools are built for delays measured in hours and days.

What the Contact Sees

Nothing during the wait. The chat is quiet for the duration you set, then the next message lands as normal. There is no "typing…" indicator, no system row and no spinner.

If the contact sends a message during a Wait, the wait still fires because it is wall-clock. Their message arrives in the chat and goes to whatever is listening downstream (operator, AI, the next trigger run).

Validation

The card shows these errors through a red warning icon in the title bar.

TriggerMessage
Duration is blankSet the wait duration.
Duration is under 5 sWait must be at least 5 seconds.
Duration is over 1 800 s (30 min)Wait can't exceed 30 minutes.
Previous card is another Wait cardTwo Wait cards can't follow each other - combine into a single longer pause.

A Wait card that leads straight into a Wait Timeout card shows a dashed red connection with the tooltip A Wait card can't lead into a Wait Timeout. Put an input card such as a Question between them.

When the waits in a flow add up to more than the flow's execution timeout, Publish is refused with Flow cannot be published due to validation errors and a line naming the Wait card. Raise the timeout or shorten the waits.

Crashes and Republishing

EventEffect
Worker crash mid-pausePause survives. Each armed wait is persisted and scheduled for its exact time, so the pause still fires on schedule. A 60 s check runs as a safety net to recover waits after a crash.
Flow republishedAll pending waits for that flow are cleared cleanly. In-flight runs end naturally; new runs use the new flow definition.
Flow execute timeoutIf the wait would push the run past the flow's execute timeout, the run ends at the cap. No stray dispatches. The publish validator warns about this combination before you save.

Operations Cost

Arming a Wait card costs 1 operation, charged once when the pause starts. A Wait that is skipped because the pause could not be armed is not charged.

The card that fires after the pause costs what it normally costs (1 op for a Text, 2 ops for a Condition, variable for an AI card, etc.). The Wait itself adds the 1 op above and nothing more.

Limits

LimitValue
Minimum duration5 seconds
Maximum duration30 minutes (1 800 seconds)
Late-fire grace window5 minutes (worker downtime / deploy)
Per-org inflight cap10 000 active waits (soft limit)

Common Use Cases

  • Slow-drip onboarding. Pace a multi-message welcome so each line lands with breathing room.
  • AI generation cover. Let the AI reply land, then take a beat before the follow-up.
  • Queue throttle. Pause before Assign Operator so spikes don't hit the on-shift team.
  • Per-branch pacing. Use different beats on different branches of a Buttons or Condition card.
  • Fallback pacing. After a Wait Timeout fires its timeout branch, add a Wait so the escalation isn't instant.

FAQ

Can I set 0 seconds for a no-op? No, the minimum is 5 s. To jump between cards with no pause, connect them directly.

Does the contact see a "typing…" indicator during the wait? No. Some channels support it natively (Telegram does, WhatsApp doesn't), and the card's behaviour is not tied to one channel. On Telegram, the platform sends a typing indicator automatically while an AI generates.

Can I chain Wait cards for an hour-long pause? Two Wait cards can't sit back-to-back, but you can put any other card between them, such as a Note, a Text or an Update Contact, and the delays add up. For long delays, use a Scheduled Trigger or a Broadcast.

Does a Wait inside a Branch (if/else) work? Yes. Each branch can have its own Wait downstream, and they are independent. For example, "Yes → wait 5 s → reply" and "No → wait 10 s → ask why".

What if a contact sends a message during the wait? The wait still fires when its timer elapses. The message routes through whatever is listening (operator, AI auto-reply, another trigger). To let an inbound message end the wait, use a Wait Timeout.

Was this page helpful?

  • Wait Timeout - the sibling card for reply deadlines (60 s – 30 days, with retries and nudges).
  • Broadcasts - delays measured in hours and days, or one-off sends at a specific time.
  • Scheduled Trigger - fire a flow on a cron schedule or relative to a contact date field.
  • Flow Editor - palette, connections, publishing.

On this page