Customer can't type: buttons and the Turn off typing step

Last updated: 13 October 2026 · 4 min read

In the mobile app (App SDK), the flow decides when the customer can type. You can hide the text box or keep it while buttons wait, and close typing completely when you need to. The web chat does not have these settings.

Steps

  1. 1

    “Customer can't type” on buttons

    Select a “Menu”, a “Language” or a “Message” step with buttons. The right panel has a “Customer can't type” switch, on by default:

    • On: the customer picks one of the buttons, and the text box is hidden.
    • Off: the text box stays under the buttons. The customer can pick a button or type an answer. Typing a button's name counts as picking it.

    The card says “Customer can't type” or “Typing allowed”.

  2. 2

    The “Turn off typing” step

    In “+ Step” › Action, choose “Turn off typing”. After this step the customer can't write in this conversation. The lock stays after the flow is over: if the conversation is resolved, the customer can only start a new one. Use it, for example, when you show an order's status and end the conversation.

  3. 3

    When the text box comes back

    The text box opens again:

    • when the flow reaches a “Question” step;
    • when buttons that allow typing appear;
    • when the conversation is handed to an agent or the AI agent;
    • when an agent writes in the conversation.

    When another flow is started, the lock goes with it.

  4. 4

    SDK version

    These settings work in the app with SDK 1.0.4 and newer. Version 1.0.3 and older do not see them: the text box is hidden while buttons wait and comes back when the flow is over. Flows that do not use these settings work as before. More on versions: “Mobile SDK: versions and what is new”.