> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/feature-documentation/designing-and-running/channels/pop-up-channels/walkie-talkie.md).
# Walkie-talkie
The Walkie-talkie channel is a media pop-up that simulates **radio-style audio communication**.
| Benefit | Feature |
| ---------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| Demands immediate attention, making it ideal for urgent alerts or high-pressure communications |
MP3 file
Use in tactical/emergency scenarios
|
## Running
This is Walkie-talkie looks like to players
No matter what channel the player is in, the Walkie-talkie grabs their attention by taking over the screen. There's no skip option, players must press `Push to Answer` to listen and `Release to End` to finish:
{% hint style="success" %}
The persona's name will appear in the screen of the Walkie-talkie.
{% endhint %}
***
## Designing
### How to (Injects)
Create an inject and choose your persona. You can attach or drag and drop an audio file:
### FAQs Does the Walkie-talkie interrupt other interactions, such as email or chats?
Yes, the Walkie-talkie channel **overrides** other interactions by covering the screen, ensuring players cannot ignore it.
Great for **urgent alerts, time-sensitive commands, or simulating high-pressure radio communications** where immediate attention and response are needed.
What happens if the player doesn't press Push to Answer?
Players must press `Push to Answer` to listen to the message and `Release to End` to close it.
There is **no skip option**, so they need to engage with it before returning to other tasks.
---
# 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://helpdocs.conducttr.com/feature-documentation/designing-and-running/channels/pop-up-channels/walkie-talkie.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.
