# Introduction to Ask Actions {% embed url="" %} ### **How Ask Actions Work** Ask Actions prompt users with a question and wait for their response. Once the user provides the requested information, the chatbot: * Validates the input (if validation is enabled) * Stores the response in a variable * Continues to the next action in the workflow Example interaction: Bot: What is your email address?\ User: The chatbot stores the email address and uses it in later steps. ### **Accessing Ask Actions** To add an Ask Action in the bot builder: * Open **Bot Builder** * Click **Add Node** * Select the **Ask** tab * Choose the required Ask Action * Configure the question and settings * Click **Create** The Ask Action will then appear as a node in the bot workflow. #### **Types of Ask Actions** OwnChat provides several Ask Actions to collect different types of user input. **Ask Text** Collects a **free-text response** from the user. Common uses: * Customer name * Feedback or comments * Custom responses **Ask Number** Collects a **numeric input** from the user and validates it as a number. Common uses: * Quantity of items * Age * Order numbers **Ask Phone Number** Collects a **valid phone number** from the user. Common uses: * Customer contact information * OTP verification * Support communication **Ask Email** Collects a **valid email address** and validates the format. Common uses: * Lead generation * Newsletter signups * Account registration **Ask Date** Allows users to select or enter a **specific date**. Common uses: * Appointment booking * Delivery scheduling * Event registration **Ask URL** Collects a **website URL** from the user. Common uses: * Portfolio links * Website submissions * Social media links **Ask Location** Captures the user's **geographical location**. Users can provide location by: * Sharing their live location * Entering their address manually Common uses: * Delivery services * Location-based services **Ask File** Allows users to **upload files** during the conversation. Supported file types may include: * Images * Documents * Attachments Common uses: * Document verification * Resume submissions * Image uploads **Ask Order** Allows users to **select products or services** within the chatbot. Common uses: * Product orders * Food delivery * Service bookings **Ask Address** Collects a **complete address from the user**. The user can provide details such as: * Street address * City * State * Postal code Common uses: * Delivery addresses * Service location details * Customer profile information **Ask Flow** The **Ask Flow** action allows the chatbot to **trigger another question-based flow** and collect structured information within that flow. This is useful when a conversation requires multiple related inputs grouped into a separate flow. Common uses: * Multi-step forms * Lead qualification processes * Complex data collection workflows ### **Address List** The **Address List** option allows users to **select from previously saved addresses** or predefined address options. This improves the user experience by allowing quick selection instead of manually entering address details each time. Common uses: * Repeat deliveries * Saved customer addresses * Quick address selection ### **Common Configuration Fields** Most Ask Actions include the following settings. **Action Name** The internal name used to identify the action in the workflow. **Message** The question shown to the user. **Error Attempt** Defines how many invalid responses are allowed before triggering the next action. **Error Message** Displayed when the user enters an invalid response. **Action on Invalid** Determines the system behavior if the user exceeds the allowed attempts. Options include: * End the flow * Skip the question * Trigger fallback flow ### **Store Response in Variable** Stores the user's response so it can be used later in the workflow. #### **Example Ask Flow** Example chatbot interaction: Bot: What is your phone number?\ User: 9876543210\ \ Bot: What is your email address?\ User: \ \ Bot: Please share your delivery address.\ User: 25 Park Street, New York The chatbot collects all responses and stores them for further processing. ### **Best Practices** Follow these recommendations when designing Ask Action flows. **Ask clear questions** Make sure the user clearly understands what information is required. **Use the correct input type** Choose the appropriate Ask Action to ensure proper validation. **Store responses properly** Save responses in variables for later use. **Limit the number of questions** Too many questions in a row may reduce user engagement. **Use fallback flows** Fallback flows help guide users when invalid responses occur. ### **Summary** **Ask Actions** allow chatbots to collect user input and build interactive conversations. With Ask Actions, you can: * Collect different types of customer data * Validate user input automatically * Store responses in variables * Use collected data for automation and personalization * Build structured and interactive chatbot workflows Ask Actions are a key component for creating **dynamic chatbot conversations and automated business processes**. --- # 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/ask-action/introduction-to-ask-actions.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.