The Disable text input action controls when visitors can type in the chat during a flow. 

 

In this article, you'll learn:

Silent walkthrough. The flow editor shows Disable text input before a decision and Enable text input after it.

 

A chat widget illustration showing disabled text input.

 

 

How Disable text input works

 

Use Disable text input to guide visitors through button choices without accepting typed messages until the flow enables text input again or ends. 

 

In your flow editor, you'll find two actions:

 

Disable text input node 

When the flow reaches this node, visitors cannot type in the chat until text input is enabled again or the flow ends. 

 

The chat widget with reply buttons and no text input.

 

Enable text input node 

When the flow reaches this node after disabling text input, visitors can type again while the flow is running.

 

The chat widget with text input enabled.

 

 

How to Use Disable text input 

 

To use the Disable text input option, head to the flow editor, open the Actions tab, and find the Disable text input action. 

 

The flow editor action palette showing Disable text input and Enable text input.

 

 

Drag Disable text input onto the flow map and connect it after the trigger and before the rest of the flow. 

 

A flow with Disable text input connected after the trigger and before a decision

 

 

💡
You can also add the Disable text input action later in your flow. However, remember that your website visitors will be able to send you a message until the running flow reaches the connected Disable text input action. 

 

 

The possibility to type will be disabled until you enable it again using the Enable text input or until the flow ends.

 

The Enable text input node and its details in the flow editor

 

 

 

Further reading