> 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.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-task-fields/communication-tasks/create-an-ask-task/ask-task-examples.md).

# Ask Task Examples

Review Cortex XSOAR 6.14 Ask task examples for playbook communication.

These examples show you how to implement some common uses of the Ask task.

**Send Emails to Users**

In this example, the message and survey are sent by email to all users with the Analyst role, and several external users. We didn't include a message body because the message subject is the survey question we want recipients to answer. There are three reply options, **Yes**, **No**, and **Not sure**. In the playbook, we will only add conditions for the Yes and No replies.

![ask-task-example-email.png](https://3548014557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOHlpKeFtqCLUYKuYyccd%2Fuploads%2Fgit-blob-e287e89ef3982ca67c61027063dd2f73a6cdb48f%2F717595b8b5d2ee4de7674ca3becd0e6fc5a54c9f8a81390df0993da44a0c81f5.png?alt=media)

**Send a Survey**

In this example, the message and survey will be sent to recipients every hour for six hours, until a reply is received. The SLA is six hours. If the SLA is breached, the playbook will proceed according to the Yes condition.

![ask-task-example-survey.png](https://3548014557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOHlpKeFtqCLUYKuYyccd%2Fuploads%2Fgit-blob-97631cefba1454be2c2fb3e8e3de9d952b3ba33e%2F568e24e9c1301dbaba0d00daf0c1d2ed55aedae52287d4252f50649c32db2b3c.png?alt=media)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-task-fields/communication-tasks/create-an-ask-task/ask-task-examples.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.