> For the complete documentation index, see [llms.txt](https://docs.mylinkconnect.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mylinkconnect.com/broadcasts/scheduling/basic-settings/on-conversation-state-changed.md).

# On Conversation State Changed

On Conversation State Changed broadcasts are sent to your users after the conversation take over and hand over state changes. This type of broadcast is particularly useful if you wish to get back to the user after the operator hands back to the bot or to execute specific operations after some time the conversation has been assigned.

This broadcast is triggered by any action that alters the conversation state. It is triggered by the [flow action](/actions-and-operations/flow/xenioo.bots.actions.base.requestoperatoraction.md) as well as from [direct conversation commands](/conversations/general.md).

### Trigger Timing

You can choose here after how much time the trigger should invoke the current broadcast. The minimum timing is 1 minute and can go up to several months later.

### Trigger

This field will let you choose the type of action that triggers the broadcast. 

| Trigger            | Description                                                                                                             |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------- |
| Take Over          | The trigger will be fired after the specified amount of time has passed since the conversation was taken over.          |
| Hand Over          | The trigger will be fired after the specified amount of time has passed since the conversation was handed over.         |
| Operator Requested | The trigger will be fired after the specified amount of time has passed since the conversation request flag was raised. |


---

# 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://docs.mylinkconnect.com/broadcasts/scheduling/basic-settings/on-conversation-state-changed.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.