> ## Documentation Index
> Fetch the complete documentation index at: https://help.lobyco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Delay block

> Build a journey that waits.

*7 September 2026 · Orchestration*

Customer journeys rarely happen all at once. Until now, anything that had to happen *later* meant a second campaign and a second audience. With the new **Delay** block the wait goes on the canvas itself. Customers stop there for as long as you choose, then carry on in the flow.

## Examples

* Welcome a new customer, give them a game, **wait 7 days**, then invite them to a challenge.
* A customer completes a challenge → **wait a day** → re-engage them while it is still fresh.
* Someone qualifies at 08:00 but you want the next engagement to happen in the evening → **wait until 19:00 today**.

![Building a customer journey with a Delay before the next activity](https://mintcdn.com/lobyco-4c9fb3ad/8XKQyo6M7ttG0QMR/images/release-notes/2026-09-07-delay-block-01.png?fit=max\&auto=format\&n=8XKQyo6M7ttG0QMR\&q=85\&s=bd5a4c6c28f83866d60210a4011162c4)

## How it works

Add **Delay** between the customers coming in and the activity that follows. Then fill in one sentence: at this step, wait for 5 days, then continue at 09:00.

Waits are set in minutes, hours or days, up to 90 days. A wait in days also takes a time of day, so you control when during that day the customer is engaged.

[Read the full guide: Delay block](https://help.lobyco.com/business-documentation/campaigns/orchestration-canvas/block-reference.md#delay)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.