> For the complete documentation index, see [llms.txt](https://knowledge-base-speakers.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base-speakers.letsgetdigital.com/call-to-action.md).
# Call to action
## CTA and session state
When the 'Admin' button is selected, the session tools will be displayed:
### Session state
The session state displays the current state of the session.
Furthermore, a speaker is enabled to select a different sate of the session. For example, when the current state is live, the speaker has the option to switch to waiting room or to stop the session:
### Call to action
In the CTA tab, the planned CTA's are displayed:
#### Manage CTA
Manage the planned CTA by clicking the three dots. The options are:
* Send now
* Edit
* Remove
#### Add CTA
Click the 'Add CTA' button to create a new CTA.
Fill in the fields as applicable. The settings are explained at the top of this page.
## End results
Participants will see the following pop-up if enabled:
CTA can also be accessed from the bar shown at the bottom of their screen:
---
# 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://knowledge-base-speakers.letsgetdigital.com/call-to-action.md?ask=&goal=
```
`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.