# Send Button {% embed url="" %} The **Send Buttons** action allows you to send **interactive button options** to users during a chatbot conversation. Instead of typing a reply, users can simply tap one of the available buttons to continue the conversation. This feature helps guide users through structured interactions and reduces incorrect responses. Interactive buttons are commonly used for **menu navigation, support options, product selection, and information requests**. ### **Where Send Buttons Are Used** The **Send Buttons** action is typically used when you want users to choose from predefined options. **Common Use Cases** * Main menu navigation * Customer support routing * Product inquiry options * Service selection * Lead qualification * Guided chatbot conversations Example message shown to users: How can we help you today?\ \ View Details\ Contact Support\ More Info ### **How to Add Send Buttons** Follow these steps to add a **Send Buttons** action to your bot flow: * Open the **Bot Builder** * Click **Add Node** * Go to the **Send** category * Select **Send Buttons** * Configure the message and button options * Click **Create** to save the action The action will then appear as a node in the bot workflow. ### **Send Buttons Configuration** When creating a Send Buttons action, several fields must be configured. #### **Action Name** The **Action Name** helps identify the action within the bot builder.\ This name is visible only inside the workflow. Example: Main Menu Options\ Support Menu\ Product Inquiry Menu #### **Has Media (Optional)** The **Has Media** toggle allows you to attach media content to the button message. If enabled, you can include: * Image * Video * Document If disabled, the message will contain only text and buttons. #### **Header Text** The **Header Text** appears at the top of the message and provides context for the user. Example: How Can We Help You? This field supports up to **60 characters**. #### **Body Text** The **Body Text** contains the main message shown to users. This section explains what the user should do. Example: Welcome!\ \ Please choose one of the options below to continue.\ We're here to help you with the right information quickly. You can also insert **variables** in the message. #### **Footer Text (Optional)** The **Footer Text** appears below the message body and provides additional instructions. Example: Select an option to proceed ### **Adding Button Options** You can add **up to three buttons** in a Send Buttons message. Each button represents a selectable option. Example configuration: Button 1: View Details Button 2: Contact Support Button 3: More Info To add more buttons: * Enter text in **Button 1** * Click **Add New Button** * Add Button 2 or Button 3 A maximum of **three buttons** is allowed. #### **Error Attempt** Users may sometimes reply without clicking a button. The **Error Attempt** setting defines how many incorrect responses are allowed before triggering an alternative action. Example: Error Attempt: 3 If the user enters invalid input three times, the system will follow the configured **Action on Invalid**. #### **Error Message** The **Error Message** appears when a user enters an invalid response. Example: Please select one of the available options to continue. This helps guide the user back to the available button choices. #### **Action on Invalid** This option determines what happens if the user exceeds the allowed number of error attempts. Available options include: **End the Flow** Stops the chatbot flow completely. **Skip the Question** Allows the conversation to continue to the next step. **Fall Back Flow** Redirects the user to another predefined chatbot action. #### **Fallback Flow** If **Fall Back Flow** is selected, you must choose the fallback action. The fallback flow redirects users to another part of the chatbot when invalid responses occur. Examples: * Main menu * Help menu * Customer support flow ### **Store Response in Variable** You can store the user's button selection in a **variable**. This allows the chatbot to use the selected value later in the conversation. Example: Variable Name: selected\_option Stored responses can be used in: * Conditional logic (IF statements) * Personalized messages * Workflow automation #### **Example Interaction** Below is an example of a Send Buttons interaction. Message: How can we help you today? Buttons: View Details\ Contact Support\ More Info If the user selects **Contact Support**, the chatbot can redirect the conversation to a **support assistance flow**. ### **Best Practices** Follow these recommendations when using Send Buttons: \*\*Keep button labels short\ \*\*Buttons should be easy to read and understand. \*\*Use clear action words\ \*\*Examples:\ View Products\ Contact Support\ Learn More \*\*Limit the number of options\ \*\*Using 2-3 buttons improves user decision-making. \*\*Provide clear instructions\ \*\*Explain what users should do in the message body. ### **Summary** The **Send Buttons** action helps create interactive chatbot conversations by allowing users to choose from predefined options. With Send Buttons, you can: * Send interactive button messages * Guide users through structured chatbot flows * Reduce incorrect user responses * Store selections for automation * Redirect users with fallback actions This feature improves both **user experience and chatbot accuracy**. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ownchat.app/bot/send-action/send-button.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.