diff --git a/docs/4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an interactive message.md b/docs/4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an interactive message.md
index 188357431..5a89d693a 100644
--- a/docs/4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an interactive message.md
+++ b/docs/4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an interactive message.md
@@ -1 +1,147 @@
-> Refer : [Interactive Messages](https://glific.github.io/docs/docs/Product%20Features/Interactive%20Messages)
\ No newline at end of file
+># Send a contact an interactive message
+
+
+
+
+ | 4-minute read |
+ Level: Beginner |
+ Last Updated: October 2025 |
+
+
+
+Interactive messages let you send messages that include interactive elements—such as buttons, list menus, or a location request—so your end users (chatbot users) can engage in dynamic conversations.
+This is especially useful for:
+
+
+ - Enhancing the user experience: Buttons or lists reduce typing effort for end users.
+ - Supporting NGOs in data collection: Interactive inputs help gather cleaner, structured data that’s easier to categorize and validate.
+
+
+Note: You must first create an interactive message by following the steps outlined here. Only then can you use it inside the flow editor as part of a chatbot flow.
+This document covers:
+
+
+ - Types of interactive messages
+ - How to create an interactive message
+ - How to use an interactive message in the flow editor
+
+
+
+Types of interactive messages
+
+ -
+ Reply Buttons – Include up to three clickable buttons within a single message.
+
+ 
+
+ Important guidelines:
+
+ - Using emojis: Emojis are allowed on buttons. If you use them, copy the entire button text (including emojis) when configuring Wait for Response. Use the “Phrase” match to validate the full response string. See the Wait for Response documentation.
+ - Character limit: Per Meta guidelines, each button label can be a maximum of 20 characters. For example, “Yes I want to participate” (26 characters) is not allowed.
+ - Markdown restrictions: Markdown characters like
* and _ are not allowed in button labels. Using them will trigger “Character policy violated”.
+
+ 
+
+
+ -
+ List Message – Present up to 10 options in a list within a message.
+
+ Important guidelines:
+
+ - Lists add extra steps for users: (1) open the list, (2) select an option, (3) confirm and send.
+ - Emojis are not allowed in the title field of list options.
+ - Meta limits: up to 24 characters for list titles and 60 characters for descriptions.
+
+ 
+
+
+ -
+ Location Request – Ask the end user to share their location.
+
+ 
+
+
+
+All interactive messages follow this structure: Message body + Interaction method (buttons, list options, or a location request). You cannot send only the interaction options without a message body.
+
+
+
+Steps to create an interactive message
+
+Step 1: Log in to Glific.
+Step 2: From the left menu, click Quick Tools → Interactive msg.
+
+Step 3: Click + Create (top right).
+
+Step 4: On the Add a new Interactive message page, fill in the details below.
+
+
+
+
+ -
+ Type – Choose Reply Buttons, List Message, or Location Request.
+
+ -
+ Reply Buttons
+ 
+
+ - Enter the text for the first button.
+ - Click + to add the second (and third) button.
+ - (Optional) Select an Attachment Type.
+ - (Optional) Provide an Attachment URL. If Allow dynamic media is checked, you can use an expression to fetch the media URL dynamically.
+
+
+ -
+ List Message
+ 
+
+ - Enter the List Header—the text shown on the list button (see the preview).
+ - Enter the Title for List 1 (see how titles and items appear in the preview).
+ - Enter the Title for the first item in List 1.
+ - Enter the Description for the item.
+ - Click Add list item to add more items.
+ - Click Add list to add another list section.
+
+
+ -
+ Location Request
+ 
+
+ - Write the message that will appear with the Send Location button.
+ - To learn how to convert shared coordinates into meaningful place data, see Google Maps API for reverse geolocation.
+
+
+
+
+ - Title – A name for easy search. If you check the box, this title also appears at the top of the message for end users.
+ - Message – The content you want to send, along with the chosen interaction (buttons, list, or location request).
+ - Footer – Optional subtext displayed at the bottom of the message.
+ - Tag – Create or select a tag to make future searching and categorization easier.
+ - Translate – See Using interactive messages in different languages.
+
+
+How to add interactive messages in the flow editor
+
+Step 1: Create a flow.
+Step 2: When adding a new node, select Send the contact an interactive message as the action type.
+Step 3: Use the dropdown to choose the interactive message you created. You can also type its title to filter the list.
+
+Step 4: Click OK.
+See the sample flow.
+
+
+Using interactive messages in different languages
+
+Step 1: Create the interactive message in your default language (see steps above).
+Step 2: After saving, click Translate.
+
+A pop-up appears. Selecting Auto translate the content will translate the message box text into your preconfigured languages.
+
+Step 3: The message content (including list header, list names, list options, and button options) is translated for all specified languages. The language-specific interactive message will automatically appear for contacts whose profile language matches.
+
+Please verify and, if needed, edit the translated fields before saving.
+Step 4: Click SAVE.
+See the sample flow.
+
+
+Note: It’s best to add translations while creating the interactive message. You can also add them later by switching languages in the flow editor and updating category/rule translations. Adding translations during creation—either via auto-translate or manually—automatically populates the corresponding category and rule translation fields.