Wait

Pause the run for a duration or until a time of day, optionally held to business hours or a daily window.

Quick start

  1. Go to Automate → Workflows and open a workflow. Click + and pick Wait.
  2. Choose Wait for a duration (seconds 1–15, or minutes, hours, days) or Wait until a time of day.
  3. Optional: tick Only continue during business hours or Only continue between set hours, every day (not both).
  4. For set hours, fill in From and to (default 09:00–21:00).
  5. Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.

Watch out

  • Stopping or unpublishing a workflow drops every queued wait — except one after an answered Ask a Question. Publish changes on a live workflow keeps them.
The Add Steps menu open on the canvas, with Wait highlighted.
The step panel waiting 4 hours, a short duration wait.
Only continue between set hours ticked, with the From and to time fields.
Details

Getting here

Automate → Workflows, open a workflow, click + on the canvas, then pick Wait under Add Steps.

Before you start

  • An owner, admin or agent can add this step and save the workflow. Publishing it is an owner or admin action.
  • Building and running workflows depends on your plan; see pricing.
  • Nothing outside Inchat has to be connected. Holding a wait to business hours needs them set in Settings → General.

Set up

  1. Open the workflow and click + where the pause belongs.
  2. Pick Wait.
  3. Choose Wait for a duration (seconds, minutes, hours or days) or Wait until a time of day.
  4. Optional: tick Only continue during business hours, or Only continue between set hours, every day — not both.
  5. Save the step. To publish: set Status to Published in the toolbar at the top of the editor, click Save, then confirm with Publish. The dropdown on its own changes nothing until you save.

Fields

Wait for a duration
A number and a unit — seconds, minutes, hours or days.
Limits: Seconds must be 1 to 15, or 60 (one minute) or more — nothing in between. The overall cap is 90 days.
Wait until a time of day
A time of day. Resumes at the next occurrence of that time — tomorrow, if it has already passed today.
Limits: There is no time zone picker for this mode — it always resumes against Asia/Kuala_Lumpur time, whatever time zone the workspace or the contact is in.
Only continue during business hours
If the wait would end outside the workspace's business hours, it is held until the workspace next opens.
Default: off
Limits: Uses the hours set in Settings → General. Cannot be combined with the daily-hours hold below.
Only continue between set hours, every day
If the wait would end outside a fixed daily window (every day of the week, including weekends), it is held to the nearest moment still inside that window.
Default: off; 09:00–21:00 when switched on
Limits: A wait held this way that would land outside the window is pushed to the next window start — for example, a night wait is sent the next morning. If that morning is still outside the messaging window (WhatsApp's 24-hour window, for instance), the message goes out at the last moment before the window closes instead, so it still arrives. This pull only applies to a wait under a day long; a longer wait crosses the window regardless, which is not corrected for. If no moment inside the window fits at all, nothing is pulled back and the send can fail when it fires. Cannot be combined with the business-hours hold above.

How it works

  • A short wait — 15 seconds or less, and only while the run's total of such short waits so far still fits in that same window — actually pauses the run in place.
  • Everything longer is scheduled instead, and resumes the next time the queue is checked, not held open.
  • A scheduled wait resumes when a check for due waits runs, about once a minute — a different check from the one that handles incoming messages.
  • When a scheduled wait comes due, the workflow and the conversation are checked again before resuming.
  • If the workspace's plan no longer includes workflows, the wait is quietly cancelled rather than resumed.
  • If the workflow has been deleted, the resume is always refused.
  • If it has been stopped or unpublished since the wait began, the resume is refused too — even if the workflow was published again afterwards.
  • Changes published with Publish changes while the workflow stayed live do not refuse it. The wait resumes on the steps it was queued with, not the new ones.
  • The resume is also refused if a teammate has since taken over the conversation, the AI is paused, or the contact is blocked.
  • One case is exempt: a wait that sits after an answered Ask a Question keeps resuming even if the workflow was stopped, unpublished or republished — but not if it was deleted; see Limits.
  • Only continue during business hours only ever pushes a due time forward, to whichever opening comes next.
  • Only continue between set hours, every day also only pushes forward by itself.
  • But if forward-holding it would carry the send past the channel's own messaging window, that hold is pulled back to the latest moment still inside the window instead.
  • That can land the send earlier the same evening, rather than the next morning.

When it fails

  • The workspace's plan stops including workflows while a wait is pending: the continuation is silently cancelled — it does not run, and nothing about the original run is marked failed after the fact.
  • The workflow is stopped or unpublished while a customer has a wait pending: that customer's queued continuation is dropped. Publishing the workflow again does not bring it back.
  • It resumes against neither the old state nor the new one — unless the wait sits after an answered Ask a Question in the same flow; see Limits.
  • The workflow being deleted is never exempt, even then.
  • A teammate has taken over the conversation, the AI is paused, or the contact is blocked, by the time a scheduled wait comes due: the resume is refused.
  • The one exception is when every remaining step only writes internally — a tag, a field, a note — rather than reaching the customer.
  • That kind of continuation still runs even on a held thread.
  • You read the reason in the workflow's Activity tab: pick the run under Execution log and the step's line names it.

Limits

  • It cannot pause for longer than 90 days in one step.
  • A wait of a day or more usually outlasts the 24-hour window on WhatsApp, so whatever comes after a long wait on that channel should be a template, not a plain message.
  • Stopping or unpublishing a workflow means every customer currently waiting on it will not get their next step, even if you publish it again straight away.
  • Changing a live workflow with Edit and Publish changes does not do that. Customers already waiting finish on the steps they started with; see Test and publish a workflow.
  • One is exempt: a wait that sits after an answered Ask a Question in the same flow.
  • That continuation is bound to the copy of the workflow the customer was shown when asked, so it keeps resuming against that same, now-superseded copy — even after the workflow is stopped or republished.
  • Deleting the workflow is not exempt, even then.
  • The two hold options are mutually exclusive — saving refuses a wait with both set.

Best practices

  • For a follow-up aimed at a customer, hold it to set hours rather than business hours.
  • Set hours apply every day including weekends, so a Saturday-night wait still resumes on Sunday morning instead of waiting until Monday.
  • Reserve business-hours holding for a wait whose next step needs the team, not the customer — a hand-off or a call-back promise.
  • Avoid stopping a workflow that has a long wait actively pending on it if the queued follow-up matters. Change it with Edit and Publish changes instead, which leaves those waits in place.

Use cases

  • A payment reminder waits a day, checks whether the invoice is still open, and only then sends the next nudge.
  • A quote sent late at night waits two hours before following up, held to set hours so the follow-up lands the next morning rather than after midnight.

FAQ and troubleshooting

Can Wait hold until a specific date, like 'March 5th at 6pm'?
Not directly — Wait holds for a duration or until a time of day. For a fixed date, use Date & Time (business hours) with a date range, or start the workflow from **Contact Date Reached** instead.
I stopped my workflow (or stopped it and published it again) and a customer's follow-up never arrived.
A wait queued against a workflow is dropped when that workflow is stopped or unpublished, and publishing it again does not bring the wait back. The one exception is a wait that sits after an answered Ask a Question: that continuation is bound to the copy the customer was shown, so it keeps resuming against it even then. Deleting the workflow drops the wait regardless. To change a workflow that has waits pending, press Edit and then Publish changes instead of stopping it: those customers finish on the steps they started with.

Reading this with an AI assistant? Plain Markdown version.