Category

How to Restrict Query Submission Until Required Details Are Provided

Updated:

This guide explains how to prevent a requester (customer/user) from submitting messages or queries in a BoldDesk chat workflow until all required fields are collected. To achieve this, you must use the Manage Inputs block and disable Requester Input and Agent Input during the data‑collection step.

This configuration is commonly used when you must collect mandatory details—such as customer name or email address—before continuing the conversation.

How the Input Restriction Works

When Requester Input and Agent Input are disabled:

  • The requester cannot type or send messages in the chat widget.
  • Agents cannot reply within the Agent Portal for that workflow step.
  • The system ensures that required fields are collected before allowing further conversation.
  • Input options automatically re-enable after the workflow block finishes.

Steps to Disable Requester & Agent Input

Use these steps to configure the workflow:

Open the Conversation Created Block

Click the More Options menu on the Conversation Created block.

Insert a Manage Inputs Action

Select Insert NextActionsManage Inputs.

Disable Input Options

Inside the Manage Inputs block:

  • Disable Requester Input.
  • Disable Agent Input.

    Disable Requester and Agent Input.gif

    Manage Inputs.png

This prevents both the requester and the agent from sending messages during the workflow’s data‑collection phase.

By using the Manage Inputs option, you can conceal the input area. If the value is set to false in the workflow, the sticky button will also be hidden. After the process is finished, you may display the input area once more.

Requester View (Chat Widget)

  • The reply box is hidden or disabled.
  • The user cannot submit queries until required fields are completed.

    Requester Input at Start of Chat.png

Agent View (Agent Portal)

  • The agent’s reply area is disabled during that workflow step.

    Reply Section disabled in Agent Portal.png

The Requester Input, Agent Input, and System messages are activated automatically after the respective workflow concludes.

Example Use Case: Collecting Customer Name & Email Before Conversation Continues

Workflow logic:

  1. System asks for Full Name.
  2. System asks for Email Address.
  3. Requester Input stays disabled until both items are provided.

This ensures consistent data capture and eliminates incomplete ticket submissions.

Frequently Asked Questions

1. Why disable requester input in a chat workflow?
To ensure the requester completes mandatory fields before continuing the conversation.

2. Can I disable only requester input but keep agent input enabled?
Yes. Requester Input and Agent Input are independent checkboxes. You can disable one or both.

3. When do inputs return to normal?
Requester Input, Agent Input, and System messages are activated automatically after the respective workflow concludes.

4. Does Manage Inputs validate email format?
Validation depends on the field type configured in the blocks that collect the data (for example, an Email input type).

5. Can I use Manage Inputs to create multi-step forms?
Yes. This approach is commonly used for onboarding, lead capture, and structured intake workflows.

6. What happens to the sticky button when requester input is disabled?
If Requester Input is set to false, the sticky button is also hidden while the restriction is active.

Related Articles

  1. How to Add a “Contact Us” Form in BoldDesk Chat Workflows
  2. How to Get an Attachment from the User in Chat Workflows
  3. How to Use Navigate to Blocks in Chat Workflows
  4. How to Collect Location Details From the User in Chat Workflows
Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Comments (0)
Access denied
Access denied
Access denied
Access denied

No articles or sections found
No articles or sections found