diff --git a/docs/personalization/how_it_works.md b/docs/personalization/how_it_works.md
index 25e762acfc..587ede29c0 100644
--- a/docs/personalization/how_it_works.md
+++ b/docs/personalization/how_it_works.md
@@ -9,7 +9,7 @@ The idea behind the Personalization service is built upon four main steps.
 1. A user visits a news service or an online store, navigates through it and leaves some footprints. The most popular footprints are selecting (CLICK) and purchasing products (BUY).
 2. This information is sent to the Personalization client every time these events happen.
 3. The Personalization server accumulates the tracked events, categorizes them and calculates recommendations for every product and every user in the shop.
-4. Recommendations can be fetched from the Personalization service and presented to users during their sessions.
+4. Recommendations can be fetched from the Personalization service and presented to users during their sessions or pushed by the service to a dedicated endpoint, for example, to be forwarded to customers.
 
 ![Overview of how recommendation works](recommendation_overview.png)
 
diff --git a/docs/personalization/integrate_recommendation_service.md b/docs/personalization/integrate_recommendation_service.md
index 34f9b3c71c..f03b0dc928 100644
--- a/docs/personalization/integrate_recommendation_service.md
+++ b/docs/personalization/integrate_recommendation_service.md
@@ -151,6 +151,62 @@ if ($recommendations && isset($recommendations->recommendationResponseList)) {
 curl_close($curl);
 ```
 
+## Send emails with recommendations
+
+By using [email triggers]([[= user_doc =]]/personalization/triggers.md), your organization can send emails to individual visitors, for example, to invite them to return to the website or remind them of items abandoned in a cart.
+
+Email triggers are push messages with recommendations.
+Specific conditions, such as the time that must pass before email start being sent, content types and attributes to be included in a response, or a number of repetitions, are first defined based on an interview between you and Ibexa.
+Email triggers are then processed on the Personalization server and responses are delivered to a dedicated endpoint.
+
+To let your visitors receive emails with recommendations:
+
+1\. With the [User API](api_reference/user_api.md#post-requests), add the `e-mail` attribute (or another identifier) to the user record.
+
+2\. Prepare an endpoint to intercept push messages and pass them on, for example, to your mailing system.
+Out of many options, it could be an Ibexa Connect [webhook](https://doc.ibexa.co/projects/connect/en/latest/tools/webhooks/). 
+The endpoint must meet the following requirements:
+
+   - must support POST requests
+   - must accept JSON objects in a format that resembles the following example:
+
+``` json
+{
+   "customerID":"1234567",
+   "userExternalId":"user@domain.com",
+   "triggerType":"REACTIVATION|ABANDONED_SHOPPING_CART",
+   "triggerName":"TRIGGER_REF_CODE",
+   "triggerOpenedLink":"NEW_EVENT_FOR_TRIGGER_OPENED",
+   "recommendations":[
+      {
+         "itemId":959,
+         "itemType":46,
+         "links":{
+            "clickRecommended":"CLICK_RECOMMENDED_LINK_WITH_TRIGGER_REF_CODE",
+            "rendered":"RENDERED_LINK"
+         },
+         "attributes":{
+            "ses_name":"First product's name",
+			      "ses_image":["img_1", "img_2"]
+         }
+      },
+      {
+         "itemId":123,
+         "itemType":55,
+         "links":{
+            "clickRecommended":"CLICK_RECOMMENDED_LINK_WITH_TRIGGER_REF_CODE",
+            "rendered":"RENDERED_LINK"
+         },
+         "attributes":{
+            "ses_name_for_type_55":"Second product's name"
+         }
+      }
+   ]
+}
+```
+
+3\. Contact `support@ibexa.co` with your organization's requirements to have the email triggers enabled.
+
 ## Advanced integration
 
 You can configure integration at a more advanced level to track more events,