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 5a89d693a..ca12ca721 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	
@@ -145,3 +145,58 @@ See the <a href="https://drive.google.com/file/d/1uiJQWIi-6U7YZu28OggvXSqZ57FYNu
 </p>
 
 <p><b>Note:</b> 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.</p>
+
+### Steps to add translations
+
+If translations are to be added after creating and using the interactive message in the flow editor, they need to be updated in two places:
+<ul>
+  <li>In the interactive message – to make them visible to end users.</li>
+  <li>In the flow editor – to ensure the flow logic remains intact.</li>
+</ul>
+
+Step 1: Click on the `edit` icon on the interactive message node.
+
+<img width="366" height="406" alt="Screenshot 2025-10-29 at 8 52 11 PM" src="https://github.com/user-attachments/assets/085151bb-4a3b-4f9b-abb4-81d5d48451ef" />
+
+Step 2: The edit page of the interactive message will open. From the top-right corner, click on the language for which you want to add translations. 
+
+<img width="599" height="392" alt="Screenshot 2025-10-29 at 8 53 00 PM" src="https://github.com/user-attachments/assets/5146efa2-a1ff-4ff6-a2bf-27aa8a86b071" />
+
+Enter the translations for the message body and the buttons/list items. Repeat this process for each language you wish to include.
+
+<img width="535" height="335" alt="Screenshot 2025-10-29 at 8 53 21 PM" src="https://github.com/user-attachments/assets/c1399a9d-9dc2-4d59-87bd-e116406ac6d2" />
+
+Step 3: Click on `Save`
+
+Step 4: On the flow editor, navigate to the languages on the top right corner.
+
+<img width="607" height="393" alt="Screenshot 2025-10-29 at 8 54 04 PM" src="https://github.com/user-attachments/assets/38dd4db5-db74-4b76-a9f0-a2198b16c89f" />
+
+Step 5: Select the language you wish to add translations for. The below screenshot shows the `Hindi` language view.
+
+<img width="596" height="381" alt="Screenshot 2025-10-29 at 8 54 34 PM" src="https://github.com/user-attachments/assets/77a8361e-80ce-4336-b17f-3ff7b589718e" />
+
+Note: The values entered under validations such as `has only the phrase`, `has a number`, etc. act as rules to verify whether a user’s response matches the expected input. These are grouped into categories, as shown below. Depending on the design, these categories may or may not be visible to the end user. Learn more about `Wait for Response` [here](https://glific.github.io/docs/docs/Product%20Features/Flows/Flow%20Actions/Wait%20for%20the%20contact%20to%20respond).
+
+<img width="607" height="539" alt="Screenshot 2025-10-29 at 8 55 09 PM" src="https://github.com/user-attachments/assets/e9363434-6d0e-4c4d-b330-909c9b26f009" />
+
+Click on the `Wait for Response` node linked to the interactive message for which you want to add translations. 
+
+In the `Rule Translations` tab and enter the corresponding translations for the button text. In cases where the validation type is set to `has any of the words`, you can add the translated terms as comma-separated values, and continue similarly for other validation types.
+
+<img width="631" height="412" alt="Screenshot 2025-10-30 at 8 44 40 AM" src="https://github.com/user-attachments/assets/1cd2c671-3630-4fea-8489-4af66e4ae7b4" />
+
+
+In the `Category Translation` tab, you can add translated category names as per your design requirements. If no translations are provided here, the system will use the default values when referenced, for example, in the above case, if hindi category translations are not added, when the category name is referenced as `@results.topic_selected.category.` In Hindi, the default category names (which are in english) will be picked.
+
+<img width="638" height="412" alt="Screenshot 2025-10-30 at 8 44 58 AM" src="https://github.com/user-attachments/assets/fe7b3688-4b90-4edc-8909-016a05749e8f" />
+
+Step 5: Click on `Ok`
+
+Step 6: Test the flows in the languages for which the translations were added, to make sure, they have been added correctly and the flow does not break/terminate. 
+
+
+
+
+
+