# Channel display types & Chat 2 Pay node enhancement

## Release Summary 

This release focused on further UX enhancements to simplify and support multiple channel display types, variable support for the Chat 2 Pay node, and addressing some bugs.

## Supporting Multiple Display Types for Different Channels <a href="#supporting-multiple-display-types-for-different-channels" id="supporting-multiple-display-types-for-different-channels"></a>

Each rich/interactive channel has different rules and options when displaying messages to the end-user. For example, in WhatsApp's Interactive Messages, you can only configure 1 - 3 options for Reply Buttons, while the equivalent on another future channel may only allow you to configure 2 - 5 options.&#x20;

Therefore, we had to find a way to support all these options (while still supporting the text-only messaging channels like USSD and SMS) and present them to the flow-builder in a simple way, and also in this way future-proof our product for channels further down on the roadmap.&#x20;

On the *Menu* and *Multiple Choice* Nodes, we have introduced a "*Configure Display Type"* modal that enables the flow-builder to configure the way that the options should display to end-users on each of the applicable channels they are going to use.

The modal only displays the channel/s that are activated on your account. For the selected channel, e.g. WhatsApp, the flow-builder can select from different display types. Clicking on "*More info*" provides a description of the selected display type, including an example of how the display type will be presented to the end-user.

<figure><img src="https://2380245535-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl8ao2e7ogQyZBti1BuxA%2Fuploads%2F3lEPcCyHVcVVvVs596Me%2Fimage.png?alt=media&#x26;token=d75330fe-8d51-4a86-8a5a-7ef36872fd4f" alt="" width="563"><figcaption><p>Configure display type on Menu and Multiple Choice nodes.</p></figcaption></figure>

<figure><img src="https://2380245535-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl8ao2e7ogQyZBti1BuxA%2Fuploads%2FL43ghzi6rL9IUOIj0LNL%2Fimage.png?alt=media&#x26;token=136b2f0c-123c-4870-a153-e618b9c40181" alt="" width="563"><figcaption><p>Select the display type for your WhatsApp channel</p></figcaption></figure>

<figure><img src="https://2380245535-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl8ao2e7ogQyZBti1BuxA%2Fuploads%2F6sUMkJSI168mLvSHmmGo%2Fimage.png?alt=media&#x26;token=32919100-b39d-4794-8d9a-36807283dc2f" alt="" width="563"><figcaption><p>Click "More info" to preview a static example of how it will display to the end-user on the WhatsApp channel</p></figcaption></figure>

## Chat 2 Pay Node <a href="#chat-2-pay-node" id="chat-2-pay-node"></a>

A small but significant improvement - the [Chat 2 Pay node ](https://clickatell.gitbook.io/flow/user-facing-nodes/commerce/chat-2-pay)now supports variables on all (applicable) fields. This means that the flow-builder can use session variables within the Chat 2 Pay node and provide the end-user with a richer, more personalized experience while also reducing development time for the flow-builder.