# Channels

Channels facilitate realistic engagement by simulating real-world information sharing and communication pathways among personas in a simulation. They **are fundamental to delivering the exercise as they serve as the medium through which all interactions and content delivery occur.**

In Conducttr, when publishing an inject, it is essential for the designer to select both the persona and the channel through which the content will be delivered.

<div align="center"><figure><img src="/files/YpGuQYRZXRYB5Fbfs0MS" alt=""><figcaption></figcaption></figure></div>

### Configuration (How to)

{% stepper %}
{% step %}

### Access channel configuration

Navigate to `Configuration` > `Exercise` > `Channels` in the Editor:

<figure><img src="/files/UXDbYi3JAkrdohNZTf8A" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Enable channel

* Click the `Active` toggle switch next to the chosen channel to enable it.
* **Channels like InfoMap and SocialWatch will not auto-enable** as they can't be used in an inject&#x20;
  {% endstep %}

{% step %}

### Customise channel names and icons

Channels have generic default names like MicroBlog and GoSocial. Use the right-hand panel to edit the name and desktop icon to match your exercise or branding needs:

<figure><img src="/files/gGMLuTvBbaokVmxNjxeZ" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure channel settings for persona

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

You can go to the `Persona Library` to enable or disable channels for personas individually or in batch as needed. However, in the Master Events List (MEL), when creating an inject, selecting a channel and adding content which will enable the channel for that persona. If there’s any missing configuration for a persona (e.g., a missing email address when they need to send an email), you’ll be prompted for clarification.

<div align="left"><figure><img src="/files/9WdF1xNMQRonQa01Mkiq" alt=""><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

### Options

<table><thead><tr><th width="188">Option</th><th>Description</th></tr></thead><tbody><tr><td><strong>Channel Type</strong></td><td>Type of channel (e.g., Email, Social Media, SMS)</td></tr><tr><td><strong>Enable/Disable</strong></td><td>Toggles the channel on or off for the exercise</td></tr><tr><td><strong>Settings &#x26; Style</strong></td><td>Access specific configurations and personalise communication parameters</td></tr></tbody></table>

### What the player sees

Participants will experience interactions through active channels as if they are communicating in a real-world setting. Depending on the channel, this might include receiving and sending emails, social media interactions, or text messages reflecting realistic engagement.

### :star: Best practices

* **Consistency is key**: Ensure communication rules across channels are consistent for realism.
* **Customise for clarity**: Use realistic icons and names to enhance the immersion.
* **Test for persona suitability**: Would this persona use this channel?

{% hint style="info" %}
Use the **Channel Assistant** in AXS if you need help deciding which channel is best for the job!
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://helpdocs.conducttr.com/feature-documentation/designing-and-running/channels.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.