Skip to main content
Quick Replies provide a sleek, user-friendly way for customers to interact with your automated messages. Instead of manually typing every character, contacts can simply tap an interactive option on their screen to proceed through the conversation. In addition to standard conversational branching, ChatbotX includes an advanced Configure quick replies control panel. This feature equips your flows with a complete safety net: automatically sending follow-up messages when contacts become inactive and triggering intelligent fallback flows when contacts send manual text instead of selecting an available button.

​
The difference between Quick Replies and Regular Buttons

While both Quick Replies and Buttons allow you to trigger actions (such as sending messages, performing actions, or starting other flows), their visual presentation and conversational behavior are fundamentally different: Quick Replies are ideal when you want to guide customers through a linear, one-way funnel. Once a choice is made, previous options disappear to prevent duplicate submissions or out-of-order state transitions.

​
How to create Quick Replies in a Flow

Quick Replies are fully supported and optimized for Facebook Messenger, Instagram, and Webchat.
1

Select a message block

Inside the Flow Builder canvas, click the Send Message node where you want to add quick interactive choices.
2

Add quick reply options

Click the + Quick Reply button located directly underneath the message text editor.Type the label for each button (we recommend keeping button titles within 20 characters to ensure full readability on mobile screens). You can also include emoji icons to make choices more engaging.
3

Connect branch outputs

After adding a Quick Reply, click and drag from the output port on the right side of the button to connect it to the desired destination node (such as another Send Message node, an Action block, or an external Flow).
TikTok character limit with buttons attached: When buttons or Quick Replies are attached to a message on TikTok, TikTok only delivers the first 40 characters of the text message. The remainder of the text is automatically truncated. Always keep opening prompts concise when targeting omnichannel flows that include TikTok.

​
Setting up automated follow-ups for inactive contacts

In customer service and sales conversations, contacts often drop off midway through an inquiry because of external distractions or lack of urgency. The Follow up if contact hasn’t engaged setting allows you to automatically re-engage contacts who received your Quick Replies but did not tap any option within a specified time window.
1

Open the quick reply settings modal

On any Send Message node containing Quick Replies, click the Gear icon (⚙️) located next to the + Quick Reply button. The Configure quick replies modal will appear.
2

Enable follow-up monitoring

Toggle on the switch labeled Follow up if contact hasn’t engaged.
3

Configure the waiting duration (Wait for)

Enter the duration the system should wait before sending the follow-up reminder (for example, 30 and select Minutes, Hours, or Days from the dropdown).
4

Choose the follow-up action

Under If contact hasn’t engaged, follow up with, choose the destination action (for example, routing to an appointment booking node or sending a gentle reminder message).
Configure quick replies modal in ChatbotX Flow Builder

The Configure quick replies modal with automated follow-up and retry settings

Meta 24-hour messaging policy: Messenger and Instagram strictly enforce a 24-hour standard messaging window from the contact’s last inbound message. If your configured wait duration exceeds this 24-hour window, ChatbotX will automatically skip sending the follow-up to remain fully compliant with Meta policies.

​
Setting up fallback retry mechanisms for freeform text replies

Rather than tapping the quick buttons on their screen, some contacts instinctively type freeform text using their keyboard. If the typed text does not match any keyword or flow intent, the bot can become unresponsive or stuck. The Retry if reply isn’t a Quick reply feature eliminates this issue by enforcing a controlled retry loop:
1

Enable retry enforcement

In the Configure quick replies modal, toggle on the switch for Retry if reply isn’t a Quick reply.
2

Compose a retry prompt (Retry message)

Provide a concise instruction guiding the contact to tap an option on the screen rather than typing. For example:
3

Set maximum retry attempts (Number of retries)

Click the Number of retries dropdown to define how many times the bot should prompt the contact before diverting them to a fallback node.
Number of retries dropdown options in quick reply configuration

Available retry limits ranging from immediate fallback to up to 5 retries

The platform supports 6 retry limit thresholds:
  • No retries: Skips retry prompts completely and immediately routes the contact to the fallback step upon receiving any freeform text.
  • 1 time: Sends one retry message before failing over.
  • 2 times: Sends up to two retry messages.
  • 3 times: Sends up to three retry messages (recommended standard for optimal UX).
  • 4 times: Sends up to four retry messages.
  • 5 times: Sends up to five retry messages.

​
Choosing the next step when retry limits are exceeded

When a contact exhausts all allowed retry attempts without tapping a valid button, the system triggers the When number of retries is exceeded branch. You can select from 5 specialized continuation actions:
Choose next step dropdown menu in ChatbotX

Five flexible routing options available for next-step actions

Send Message

Instantly sends a clarifying message to acknowledge the contact’s custom inquiry or provide alternative instructions.

Perform Action

Executes back-end automations: tag the contact as stuck-flow, record a note, or assign the conversation to a human support agent (Assign to Human).

Start External Flow

Launches an independent Flow, such as an escalation path or a dedicated lead recovery sequence.

Start External Node

Jumps directly into a specific node inside an existing Flow without running that flow from the beginning.

Start Another Node

Immediately branches to another node within the current Flow (such as routing directly into an AI Agent node).

​
Visualizing fallback connection ports on the Flow Canvas

Once you enable both follow-up and retry handling in the configuration modal, the Send Message block on your Flow Canvas dynamically generates two dedicated physical output ports directly below your Quick Reply buttons:
Quick Reply fallback ports rendered on the Flow Builder canvas

Canvas visualization showing dedicated No engagement and Retries exceeded output ports

  1. No engagement ● port: Automatically fires when the configured Wait for timer elapses without the contact tapping any button. Drag a connection line from this port to your recovery node (such as a Perform Action node triggering a notification flow).
  2. Retries exceeded ● port: Automatically fires when the contact enters freeform text more times than allowed by Number of retries. Connect this port to an error handler or human escalation node (such as Send Message #4).
  3. Continue ● port: Represents the default onward continuation port of the parent message block.

​
Production-ready templates and best practices

​
Welcome inquiry template with 4 quick replies

  • Opening message prompt:
    “Hi ! Welcome to ChatbotX. 👋 How can we assist you today? Please choose an option below to get started:”
  • 4 Quick Reply buttons:
    1. 🚀 Explore Features
    2. 💳 Pricing & Plans
    3. 🛠️ Technical Support
    4. 👤 Talk to Human Agent

​
Progressive 3-stage retry sequence for freeform replies

If Number of retries is set to 3 times, use progressive messaging to balance friendliness with definitive escalation:
  • Attempt 1 (Gentle reminder):
    “I couldn’t quite catch that! 😊 Please tap one of the quick options above so I can guide you to the right place.”
  • Attempt 2 (Clear clarification):
    “It looks like you typed your reply. To keep things moving quickly, please tap one of the buttons on your screen instead of typing.”
  • Attempt 3 (Final notice before failover on Retries exceeded):
    “Sorry, I can only understand button selections at this step. Since I haven’t received a valid choice, I’m transferring you to our team for direct assistance. Please hold on a moment! ⏳”
Seamless handoff to AI Agents: From the Retries exceeded port, connect directly into an AI Agent node. The AI Agent can analyze the customer’s unstructured text inquiry using natural language understanding and deliver an immediate answer, ensuring zero dropped leads even when users bypass button menus.