# Highly Structured Message

This action will deliver a Message Template to the user. Message templates are created by your [WhatsApp Business selected provider.](/basic-concepts/publishing/channels/whatsapp/configuring-providers.md)

![](/files/-M2E7T_pE0pkx8S4PkYt)

### Settings

The action uses the following settings:

| Setting           | Description                                                               | [Parsed](/actions-and-operations/dynamic-parsing.md) |
| ----------------- | ------------------------------------------------------------------------- | ---------------------------------------------------- |
| Element Namespace | The namespace of the template. This is usually your Facebook Business Id. | :white\_check\_mark:                                 |
| Element Name      | The name of the element you've chosen for your template                   | :white\_check\_mark:                                 |
| Time To Live      | The TTL value for your template                                           | :white\_check\_mark:                                 |
| Language          | The language of the template message                                      | :no\_entry:                                          |
| Parameters        | The parameters that need to be supplied to your template                  | :white\_check\_mark:                                 |

### Remarks

The Highly Structured Message action will deliver a WhatsApp Business template in full accordance to Facebook API. Please also refer to[ Facebook documents](https://developers.facebook.com/docs/whatsapp/api/messages/message-templates/) for specific information on the required fields.

Some WhatsApp Business providers ([Sinch](/basic-concepts/publishing/channels/whatsapp.md), as an example) require a full name specification for all template parameters. If the active provider requires this type of notation you can follow the examples below.

Template:

```
Hello {1} this is {2}
```

Standard Parameters

```
Mary
The Super Bot
```

Named Parameters

```
body[1]text=Mary
body[2]text=The Super Bot
```

In both cases, the resulting template text sent will be

```
Hello Mary this is The Super Bot
```

{% hint style="warning" %}
Instead of using referenced messages, [Twilio ](https://www.twilio.com/docs/whatsapp/tutorial/send-whatsapp-notification-messages-templates#send-a-whatsapp-message-using-a-template)uses a very different approach: Twilio templates are sent as standard text. If the Twilio parser finds the message corresponding to a template, it will be sent as a template. If not, it will be sent as standard text.\
When using Twilio, you're free to use a standard text action even for templates or, alternatively, to specify the full template text in the "Parameters" field of this action.
{% endhint %}

### Trigger

This action has no triggers.

### Variables

This action does not produce any variable.

### Availability

Channel specific availability follows the table below:

| Channel          | Availability    |
| ---------------- | --------------- |
| Facebook         | Not Applicable  |
| WhatsApp         | Fully Available |
| Telegram         | Not Applicable  |
| Web              | Not Applicable  |
| Alexa            | Not Applicable  |
| Google Assistant | Not Applicable  |
| Slack            | Not Applicable  |
| API              | Not Applicable  |

This action can be used only inside interactions and not as child of other actions. This action is available only to [Premium Accounts](/basic-concepts/your-account/the-free-plan.md).


---

# 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://docs10.xenioo.com/actions-and-operations/content/highly-structured-message.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.