> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/docs/docs_se/guider/journeys/journey-steps/journey-step-wait.md).

# Wait

Journey-steg som pausar kontakten en viss tid före nästa steg.

Steget Wait pausar kontakten en viss tid. När tiden har gått går kontakten vidare till nästa steg.

<div align="left" data-with-frame="true"><img src="https://2555292243-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FicfGEyRadiE4k7sV4O4o%2Fuploads%2Fgit-blob-b359c052a287dd745e80a423a811f315dd33537e%2Fjourney-step-wait-settings.png?alt=media" alt="Dialogen Wait med Delay for inställt på 3 dagar"></div>

## Inställningar

* **Delay for** — ange ett tal och välj en enhet, till exempel dagar.

Klicka på **Apply** för att spara steget.

Ett Wait-steg placeras ofta före ett [If / Else](https://support.emarketeer.com/docs/docs_se/guider/journeys/journey-steps/journey-step-if-else.md)-steg, så att kontakten hinner agera innan villkoret kontrolleras.

{% hint style="info" %}
Lägg alltid till ett väntesteg före ett If / Else-steg, annars utvärderas det omedelbart. Det är särskilt viktigt när du utvärderar interaktioner från ett tidigare steg, till exempel att ett e-postmeddelande öppnats.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.emarketeer.com/docs/docs_se/guider/journeys/journey-steps/journey-step-wait.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
