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

# Customize an Ask Task

Customize Cortex XSOAR 6.15 Ask tasks for analyst communication workflows.

You can customize the message HTML and CSS for a data collection task.

1. Go to Settings → About → Troubleshooting → **Server Configuration**.
2. Add the key **`messages.html.formats.externalAskSubmit`**, and add the following HTML with your customizations as the value.

   ```programlisting
   <html xmlns="http://www.w3.org/1999/xhtml" xmlns:v="urn:schemas-microsoft-com:vml"
       xmlns:o="urn:schemas-microsoft-com:office:office">

       <head>
           <title> {{.title}} </title> <!--[if !mso]><!-- -->
           <meta http-equiv="X-UA-Compatible" content="IE=edge"> <!--<![endif]-->
           <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
           <meta name="viewport" content="width=device-width, initial-scale=1">
           <style type="text/css">
               #outlook a {
                   padding: 0;
                   text-decoration: none !important;
                   color: #4da9ff;
               }

               a {
                   text-decoration: none !important;
                   color: #4da9ff;
               }

               .ReadMsgBody {
                   width: 100%;
               }

               .ExternalClass {
                   width: 100%;
               }

               .ExternalClass * {
                   line-height: 100%;
               }

               body {
                   margin: 0;
                   padding: 0;
                   -webkit-text-size-adjust: 100%;
                   -ms-text-size-adjust: 100%;
               }

               table,
               td {
                   border-collapse: collapse;
                   mso-table-lspace: 0pt;
                   mso-table-rspace: 0pt;
               }

               img {
                   border: 0;
                   height: auto;
                   line-height: 100%;
                   outline: none;
                   text-decoration: none;
                   -ms-interpolation-mode: bicubic;
               }

               p {
                   display: block;
                   margin: 13px 0;
               }
           </style> <!--[if !mso]><!-->
           <style type="text/css">
               @media only screen and (max-width:480px) {
                   @-ms-viewport {
                       width: 320px;
                   }

                   @viewport {
                       width: 320px;
                   }
               }
           </style> <!--<![endif]-->
           <!--[if mso]> <xml> <o:OfficeDocumentSettings> <o:AllowPNG/> <o:PixelsPerInch>96</o:PixelsPerInch> </o:OfficeDocumentSettings> </xml> <![endif]-->
           <!--[if lte mso 11]> <style type="text/css"> .outlook-group-fix { width:100% !important; } </style> <![endif]-->
           <style type="text/css">
               @media only screen and (min-width:480px) {
                   .mj-column-per-100 {
                       width: 100% !important;
                   }
               }
           </style>
           <style type="text/css"> </style>
           <style type="text/css">
               div {
                   margin: 0 auto;
               }

               td {
                   padding: 0;
               }

               p {
                   padding: 0;
                   margin: 0;
               }
           </style>
       </head>

       <body>
           <div
               style="background-color: {{.bodyBackgroundColor}}; color: {{.bodyFontColor}}; width: 100%; height: 100%; font-family: Helvetica, 'Trebuchet MS', Verdana, Geneva, Century Gothic, Arial, sans-serif;">
               <table
                   style="background-color: {{.headerBackgroundColor}}; color: {{.headerFontColor}}; width: 100%; height: 80px; vertical-align: middle;">
                   <tbody>
                       <tr>
                           <td style="width: 70%;">
                               <h2 style="margin: 0 35px; font-weight: 100;">{{.title}}</h2>
                           </td>
                           <td style="width: 30%; text-align: center;"><img
                                   style="margin: 10px 35px 0 0; width: auto; height:35px;" src="{{.logo}}" alt="Logo" />
                           </td>
                       </tr>
                   </tbody>
               </table>
               <h3 style="text-align: center;">{{.subject}}</h3>
               <div style="margin: 20px; background-color: {{.bodyBackgroundColor}}; padding: 20px;">
                   <p style="word-break: break-word;">{{.body}}</p><br />{{.links}}
               </div>
           </div>
       </body>

       </html>
   ```


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-task-fields/communication-tasks/create-an-ask-task/customize-an-ask-task.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 `build a script that syncs our docs to a CMS` 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.
