> For the complete documentation index, see [llms.txt](https://guides.clickatell.com/release-notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.clickatell.com/release-notes/release-notes-archive/2022-release-notes/q4-2022/automated-messaging/chat-desk-node-and-routing-screen-enhancements.md).

# Chat Desk node & Routing screen enhancements

## Release Summary

This release focused on enhancing the [Chat Desk node](https://clickatell.gitbook.io/flow/user-facing-nodes/product-nodes/chat-desk-node) and [Routing ](https://clickatell.gitbook.io/flow/configuration/to-manage-a-route)section of Chat Flow.&#x20;

## Chat Desk node enhancements

We've replace the previous "Touch" node with the "[Chat Desk](https://clickatell.gitbook.io/flow/user-facing-nodes/product-nodes/chat-desk-node)" node.

In the quest to make channel and product linking easier, we've updated the [Chat Desk node](https://clickatell.gitbook.io/flow/user-facing-nodes/product-nodes/chat-desk-node) by removing the manual "copy and paste" fields the flow-builder had to perform.&#x20;

We've replaced it with *Production Integration* and *Sandbox Integration* dropdown menus. The Chat Desk API tokens are automatically pulled into the drop-downs for the flow-builder to select from.

A *Department* dropdown was also added. If Departments are set up in Chat Desk, the flow-builder can now select the department where the user must be directed first when they reach this node.

<figure><img src="/files/VmmErnaGANcuUue7lD8W" alt=""><figcaption><p>The new and improved Chat Desk node</p></figcaption></figure>

## Routing section enhancements

In certain use cases, you might want your end-users to be routed directly into Chat Desk (i.e., "bypassing" a bot). In such cases, you need to select "Chat Desk" from the *Service* dropdown in the [Routing ](https://clickatell.gitbook.io/flow/configuration/to-manage-a-route)section. Similar to the Chat Desk node enhancement above, the *Properties* drop-down will automatically be populated with the available integration(s), so the flow-builder can simply select one instead of having to copy and paste it.

<figure><img src="/files/mU0NFCQBOkCqx4mPCbTI" alt=""><figcaption><p>Select the applicable Chat Desk integration for direct routing to Chat Desk</p></figcaption></figure>

Furthermore, we've ensured a consistent experience for flow-builders when selecting the flow and step that should be triggered for each route. This follows the same process as in the "Logic" section when configuring individual nodes.&#x20;

<figure><img src="/files/d1HKxfNH6tMvHi0kOyvB" alt=""><figcaption><p>Change the route's properties</p></figcaption></figure>

<figure><img src="/files/z4pcBCesYbGSBXQGpVwI" alt=""><figcaption><p>Select the flow and step you want this route to point to</p></figcaption></figure>

We've also updated the [Routing ](https://clickatell.gitbook.io/flow/configuration/to-manage-a-route)section's UI, giving it a fresh new look that is consistent with the rest of the product. The empty state (i.e., if no routes have been set up yet) was updated to give you a clear indication of your next steps.

<figure><img src="/files/BRfGpQgZC6TMJ3rOv1VG" alt=""><figcaption><p>Empty state of the Routing section</p></figcaption></figure>
