> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/journey-orchestration/journey-examples.md).

# Journey examples

Journey orchestration uses time- and behavior-based rules to control user flows. These examples show how to configure targeted actions, branches, and message steps based on user behavior.

### Journey examples

Use these end-to-end examples as starting points for your own journey design:

* Action-Based Engagement Journey — Start when a user performs an action, then branch based on later behavior.
* Time-Based Engagement Journey — Deliver recurring, scheduled messages such as weekly highlights or renewal reminders.

For additional context, see the following blog posts:

* [Understanding Customer Journeys](https://netmera.com/understanding-customer-journeys/)
* [Create Personalized and Engaging Customer Journeys with Netmera](https://netmera.com/create-customer-journeys-with-netmera/)
* [Customer Journeys From First Touch To Loyal Advocate](https://netmera.com/omnichannel-customer-journeys/)

These resources provide additional information about journey orchestration principles and strategies.


---

# 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, and the optional `goal` query parameter:

```
GET https://user.netmera.com/netmera-user-guide/omnichannel-engagement/journey-orchestration/journey-examples.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.