> 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/pattern-of-life-pol.md).

# Pattern of Life (PoL)

Pattern of Life (PoL ) is a **predefined pool of content** used to simulate audiences, mirroring the rhythm of real online activity. 

PoL content is published in the same channels as scripted content from the Master Events List (MEL). The key difference is that PoL content is designed for dynamic publishing by the Facilitator. PoL allows the Facilitator to publish content "on-demand" rather than in sequence as is the case with the MEL.

### Why use PoL?

A combination of scripted injects from the MEL and on-demand message stacks from PoL provide the player with a blended content experience within their Virtual Desktop, which feels realistic and engaging. 

<table><thead><tr><th width="162">Benefit</th><th>Description</th></tr></thead><tbody><tr><td><strong>Efficiency</strong></td><td>Automates persona behaviour, reducing manual effort during the exercise</td></tr><tr><td><strong>Realism</strong></td><td>Personas behave like real individuals. A good example is if you want to stimulate multiple tweets seconds apart from each other</td></tr><tr><td><strong>Engagement</strong></td><td>Adds depth to the exercise by ensuring that players are receiving content from personas that feel real</td></tr></tbody></table>

<figure><img src="/files/4Qo6ACUU3MHkKeDBslqH" alt=""><figcaption></figcaption></figure>

### Terminology

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

<table><thead><tr><th width="150.2667236328125">Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Deck</strong></td><td>The grid where stax are referenced (up to 64 buttons available) which is created by the designer in the Editor and available to the Facilitator in the Facilitator Dashboard</td></tr><tr><td><strong>Button</strong></td><td>The cell in the Deck where the designer has placed a Stack for execution</td></tr><tr><td><strong>Stack/Stax</strong></td><td>The sequence of posts generated by the designer and assigned to a button</td></tr><tr><td><strong>Queues</strong></td><td>The unseen resources that allow Stax to be published. One is required per team (which by default is the Session team - i.e. publishing to everyone). <br>If you edit a deck button and select a Superteam, pressing that button will start one Queue per team (i.e. Conducttr will attempt to publish this stack to all teams in the Superteam)</td></tr><tr><td><strong>Post</strong></td><td>An individual item within a stack e.g. a tweet</td></tr></tbody></table>

## Running

<figure><img src="/files/hXP05iy27YxbEZlXdPpZ" alt=""><figcaption><p>PoL content fires around scripted MEL events during an exercise</p></figcaption></figure>

In the Facilitator Dashboard you can view the deck by clicking the `PoL` tab located at the top of the dashboard. On the deck there are two modes:

1. Play mode
2. Edit mode

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

In this example there are six buttons on the deck in total, but only two are queues as they're set to Session.

### Play mode

The deck will automatically be on *Play mode*. This allows the Facilitator to publish stax, turning them on and off independently. All available stax are low-lighted. When the Facilitator presses a button, it highlights yellow. This signifies that queues are in use.

Each button displays the following information:

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

### Edit mode

*Edit mode* allows the Facilitator to modify some settings for each stax:&#x20;

* **Loop:** Stax will repeat once completed
* **Session:** Decide if everyone in the session will see the content or a specific team/Superteam
* **Number:** Determines where your content will start. E.g. if it's set to 1, the first piece of content in your stack will be sent. Alternatively, if it's set to 3, the third piece of content will be sent

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

#### :zap:Queue limits

Each licence has a Max Queues setting so on the higher licences you'll be able to publish more content at the same time. All users can have at least six queues running at one time.

In the above example, if the stack 'Positive statement reaction' is sent to the Banking Superteam, 3 queues will be used because there are 3 teams under that Superteam.&#x20;

{% content-ref url="/pages/mxCD7XjWhey1frBl7a7P" %}
[Superteams](/feature-documentation/designing-and-running/teams-roles-positions-and-groups/setting-up-your-teams-table/superteams.md)
{% endcontent-ref %}

***

## Designing

### How to

{% stepper %}
{% step %}

#### Navigate to `PoL`&#x20;

Click a deck position— this will create a stack waiting for content. Then click the AI magic icon.

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

{% hint style="warning" %}
Designers can create multiple decks, but only 1 deck can be active at any time.
{% endhint %}
{% endstep %}

{% step %}

#### Use the *AI Stack Assistant*

The *AI Stack Assistant* generates a flow of reactions and chatter across multiple posts.&#x20;

{% hint style="success" %}
The style & strength of the content generated depends on:

* The Faction voice which is described in the Faction Description field
* The exercise context given in the Exercise setup
  {% endhint %}

The Stack Assistant expects you to select:

* Faction
* (Optional) which personas from the faction to use/how many posts to generate
* Channel & beliefs (positive, negative, or mixed)

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

{% hint style="info" %}
The channels available for PoL are:

* Email
* MicroBlog (Twitter/X)
* GoSocial
* Help Desk
  {% endhint %}
  {% endstep %}

{% step %}

#### Generate a preview and then `Generate Stack`

Click `Get preview` to see a sample of content the AI will generate. If you like it, click `Generate Stack`.

If you don't like the sample, change the text in the *Point of view* field or the Faction voice or the description in the Exercise Setup.
{% endstep %}
{% endstepper %}

### :zap:Mixing channels in a stack

It is possible to mix social channels in the same stack but we don't recommend it.

Why? Because when you're running an exercise it's easy to forget that the content is published across multiple channels and you may watch the stack timer expire only to wonder where your content has been published!

{% hint style="danger" %}
Email can't be combined with other channels in the same stack. This is because email isn't a feed in the way that social media is.
{% endhint %}

### How to configure an action inject for PoL

Designers can set up manual PoL from the MEL by creating an action inject.

{% stepper %}
{% step %}

#### Select Action

Create a new inject and in `Inject details`, select *Action*. Then in the *Action* drop-down menu that appears, select `PoL Stax Status`.

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

{% step %}

#### Select Status

In the *Status* drop-down menu, select either `Start` or `Stop` .

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

{% step %}

#### Select Stax

From the *Stax* drop-down menu, select the stack you want to stop or start.

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

Now when this inject fires during the live exercise, the PoL stack 'Celeb Gossip' will start playing automatically.
{% endstep %}
{% endstepper %}


---

# 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/pattern-of-life-pol.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.