⏱ Your bot sends three messages in a row, half a second apart. The customer reads the third one before the first has finished landing. They feel sold to. They bounce. None of that is the copy's fault. It's the cadence.
🎉 Today we shipped the smallest, most boring primitive in Wexio Flows - and probably the one with the biggest day-one impact on how your flows feel. Meet the Wait card.
🧠 The cadence problem
People pattern-match "bot" by rhythm before they read a single word. Three messages in a row, half a second apart? Their brain files it as "automation, mute it." Same three messages with 2-3 seconds between them? They read every one. The copy is identical. The trust gap is the gap between the messages.
This isn't a Wexio-specific problem. Every flow builder has it. The way you've worked around it so far is probably one of:
🔧 Adding fake "Wait Timeout" cards with no retries just to insert a delay (wrong tool - Wait Timeout is for reply deadlines, not pacing)
🔧 Cramming multi-message scripts into a single 400-character text block (kills readability)
🔧 Just shipping it fast and hoping nobody notices (they do)
We watched these workarounds enough times that the right answer became obvious: just add the primitive.
✨ How it works
Open the flow editor. Drag the Wait card from the Logic category in the palette. Connect its input to the card that should fire before the pause, its output to the card that should fire after. Click it, type how many seconds you want, save.
That's the entire feature. No retries, no nudges, no branching - that's all Wait Timeout's job, and it's a different card. Wait is pure wall-clock pacing. Anywhere from 5 seconds (good for "human catching their breath" moments) to 30 minutes (good for slow-drip onboarding that spans a coffee break).
When the runtime hits the Wait, it sends the upstream card, holds the run, then dispatches the downstream card exactly on schedule. The customer experiences a natural pause. The bot stops feeling like a script firing.
🎯 Where it pays off
🌅 Greeting sequences. "Hi {{firstName}} 👋" → Wait 3s → "I'm here to help you set things up." → Wait 3s → "Want to get started, or just look around?" - the welcome lands as a conversation, not a wall.
🎟 Operator handoffs. "Let me connect you with someone…" → Wait 10s → Assign Operator. The pause gives the on-shift queue a moment to breathe instead of every handoff slamming the team at once.
🤖 AI follow-ups. Your AI card generates a thoughtful answer → Wait 3s → "Anything else I can help with?" Without the pause, the follow-up clobbers the AI's reply before the customer's had a moment to actually read it.
🛒 Pacing inside a Branch. Different branches deserve different rhythm. "Yes → reply right away" vs "No → wait 5 seconds, then ask why". Putting a Wait inside each branch is the difference between feeling responsive and feeling pushy.
🛡 Guardrails the editor enforces
🚫 Two Wait cards in a row don't make sense - combine them into one longer pause. The canvas warns you on the connection before you publish.
🚫 A Wait card can't lead into a Wait Timeout. Wait Timeout needs an input-accepting predecessor (a Question, Buttons, etc.) and a Wait provides no input. The canvas warns you here too - put a real input card between them.
📏 The 5-second floor exists for a reason. Anything below that is indistinguishable from "no delay" to a human reading the chat, so we make you commit. The 30-minute ceiling is a soft "you probably want a Broadcast for this" hint - for genuinely long delays, the Broadcast tool is the right primitive.
🚀 Try it now
🔥 Wait is live on Standard, Pro, and Enterprise plans. Open any flow you've already shipped, find the spot where two messages fire back-to-back, drop a Wait between them, set it to 3 seconds. Republish. Send the flow to yourself. The difference is small, calm, and impossible to unsee.
🤝 Not on Wexio yet? Start a free trial - no credit card. The flow editor and the Wait card are both included from the Standard plan up, so you can build, test, and feel the difference in an afternoon.
🧵 We'd love to hear how it lands. Reply to this announcement or tag us - every message gets a real reply from a real person, in a chat that's probably running its own Wait cards too.