> For the complete documentation index, see [llms.txt](https://manuals.dialox.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manuals.dialox.ai/store/skills/timeplans/how-to-add-a-flow-for-lunch-breaks.md).

# How to add a flow for lunch breaks

The opening hours settings of your bot don't allow for specific exceptions or additional timeplans. For this the [Timeplan skill](/store/skills/timeplans.md) can be very helpful.  The Timeplan skill allows you to set a specific tag for specific time plans. This way you could configure specific logic for a certain time plan. 

In case of lunch time you need to add a Timeplan that looks like this:

<figure><img src="/files/7y4aDOfRtKYOvCW7w5Zt" alt=""><figcaption></figcaption></figure>

Now you can change your Flow to branch specifically on the tag `timeplan:lunch` the same way we implemented the out of office logic.

Add a link (1) from a [Branch node](/studio/flows/nodes/control-flow-branch.md) to a [Say node](/studio/flows/nodes/say.md) (2) that explains it is lunch time. This Say node will then link to the Note flow using the [Go to flow node](/studio/flows/nodes/control-flow-go-to-flow.md) (3).

<figure><img src="/files/Jc3BJTXHKxggYYO4wF2u" alt=""><figcaption></figcaption></figure>

Click on the link to the Say node and change the Link details on the right hand side:

<figure><img src="/files/QE2rILQRNv6dxgPTuFVe" alt=""><figcaption></figcaption></figure>

Select the Timeplan tag and provide a label for explanatory purposes.

<figure><img src="/files/PLw8EJ1wSxQVrt3uOfjq" alt=""><figcaption></figcaption></figure>

And now you have a flow that handles lunch breaks too!

<figure><img src="/files/QTXBWL7LqyhhxvARlsbC" alt=""><figcaption></figcaption></figure>


---

# 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://manuals.dialox.ai/store/skills/timeplans/how-to-add-a-flow-for-lunch-breaks.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.