> For the complete documentation index, see [llms.txt](https://support.growlytics.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.growlytics.in/journeys-and-automation/journey-settings/using-time-slots-in-journey.md). # Using time slots in journey Timing is everything! The right notification, to the right customer, and at the right is the magic equation you should aim for. With Growlytics you can decide the time after which each step of the journey will get activated for the customer. Watch this quick tutorial to see how to set a 'Wait for Event' criteria in a customer journey. {% embed url="" %} Add 'Wait for Time' Criteria {% endembed %} Let us take a look at how to set a ‘Wait for Time’ Criteria while creating a Journey. Add a ‘Wait for Time’ block, link it to the 'Custom Entry Event' block, and ‘Click to edit’. This option helps specify the time period after which, the next steps of the journey get activated for the customer. There are three options to choose from:

Add 'Wait for Time' Block

* **Option 1 'Wait for Some Time' -** This option helps specify the number of minutes, hours, or days after which the next step in the journey gets activated. For example, set a criteria where a customer will receive a 'Thank You' message, two hours after performing a 'Purchase' event.

Wait for Some Time

* **Option 2 'Wait for Day of Week'** - This option allows you to specify the day of the week after which the next step in the journey will get activated between a specific time slot. You can also select multiple days in the week after which the next step in the journey will get activated. Based on the time of the Customer’s entry into the journey, the earliest weekday matched will be considered. For example, the journey has been set to continue after every Monday and Thursday of the week between the same time slot of 10:00 AM to 07:00 PM, but the customer made a purchase on Friday. In this case, he will receive the Thank You message on Monday since it is the closest match.

Wait for Day of the Week,

* **Option 3 'Wait for Day of Month'** - This option enables you to specify the date of the month after which the next step in the journey will get activated. Select the time slot as required. You can also select multiple dates in the month, after which the next step in the journey will get activated. Based on the time of the Customer’s entry into the journey, the earliest date matched will be considered. For example, your customers shouldn't miss out on the Month End Bonanza, but the notification shouldn't go out too early either. In such cases you can use this option to trigger the Month End Bonanza notifications to reach your customer on the 25th of every month between 02:00 PM and 08:00 PM.

Wait for Day of Month

{% hint style="info" %} **Pro tip!** Use this advanced setting option to your advantage. The **‘Wait for Time Slot’** option enables you to select a particular time slot during which your customers will be prompted to go ahead with the next steps in the journey. Click on the drop-down, to select the 'Slot Start Time' and 'Slot End Time'. For example, there is a customer who is twelve hours behind your local time zone and notifications shouldn't reach them at odd hours. Use this option to set a time slot that matches their time zone, with a 'SLowt Start Time' as 08:30 PM and 'Slot End Time' as 09:30 PM. By doing this, any notification that is sent out will get triggered at that particular time slot for that particular customer. Thus ensuring that your customer is not disturbed! {% endhint %}

Wait for Time Slot

Based on the criteria set, the journey steps will get activated for the customer.
Click on ‘Save Changes’ to save your draft and continue building your journey. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://support.growlytics.in/journeys-and-automation/journey-settings/using-time-slots-in-journey.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.