> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-task-fields/communication-tasks.md).

# Communication Tasks

Communication tasks enable you to send surveys internally and externally to users to collect data for an incident. The collected data can be used for incident analysis, and as input for subsequent playbook tasks. For example, you may want to send a scheduled survey requesting analysts to send specific incident updates, or send a single (standalone) question survey to determine how an issue was handled.

To allow users outside the Cortex XSOAR server network to access the communication task link, you need to [configure access to the communication task through an engine](/xsoar-6-administrator-guide/6.12/onboard-cortex-xsoar/onboarding-in-cortex-xsoar/engines/configure-engines/edit-the-engine-configuration/configure-access-to-communication-tasks-through-an-engine.md).

**Ask Tasks**

The Ask conditional task is a single question survey, the answer to which determines how a playbook proceeds. If you send the survey to multiple users, the first answer received is used, and subsequent responses are disregarded.

Users interact with the survey directly from the message, meaning the question appears in the message and they click an answer from the message.

The survey question and the first response is recorded in the incident's context data. This enables you to use this response as the input for subsequent playbook tasks.

As it is a conditional task, you need to create a condition for each of the answers. For example, if the survey answers include, **`Yes, No, and Maybe`**, there should be a corresponding condition (path) in the playbook for each of these answers.

![communication-task.png](/files/0KE7tSsXCBUXe93LhgBH)

For all Ask tasks, a link is generated for each possible answer the recipient can select. If the survey is sent to more than one user, a unique link is created for each possible answer for each individual recipient. By default, these links are hidden. To make the links available in the context data, add the **`comm.ask.linktocontext.enabled`** [server configuration](/xsoar-6-administrator-guide/6.12/reference-docs/reference/server-configurations/playbook-server-configurations.md) set to **`true`**. The links appear under **Ask.Links** in the context data.

**Data Collection Tasks**

The Data Collection task is a multi-question survey (form) that survey recipients access from a link in the message. The survey resides on an external site that does not require authentication, thereby allowing survey recipients to respond without restriction.

All responses are collected and recorded in the incident's context data, whether you receive responses from a single user or multiple users. This enables you to use the survey questions and answers as input for subsequent playbook tasks.

The following are examples of integrations that can use Data Collection tasks:

* Email (EWS, Mail Sender, etc.)
* Microsoft Teams
* Slack

{% hint style="info" %}

### Note

You can collect responses in custom fields, for example, a Grid field.
{% endhint %}

For all Data Collection tasks, a single link is generated for each recipient of the survey. The links are available in the context data if the **`comm.datacollection.linktocontext.enabled`** server configuration is set to **`true`**. The links appear in the context data under the **Links** section of that survey.


---

# 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://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-task-fields/communication-tasks.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.