--- title: "Email Templates" canonical: "https://red-ant-documentation.refined.site/space/RET/284688486/Email%20Templates" format: markdown --- > Macro (toc) ## Overview RetailOS facilitates effective customer communication through two distinct types of outbound emails. These email categories serve to enhance customer engagement and streamline the shopping experience, tailored to individual preferences. This guide will provide an overview of the two types of emails RetailOS supports: ### **1. Transactional Emails** Transactional emails are automatically triggered by specific customer actions or events. They serve to provide essential information and enhance the overall shopping experience. Here are some key examples: #### **E-receipts:** These emails are generated immediately after a customer makes a purchase. They include a detailed summary of the transaction, ensuring customers have a record of their purchase for reference. ![image](media://8b5001fa-02b7-44e0-95db-7e5f318835dc) #### **Consultation Summary Emails:** After a consultation, RetailOS sends out summary emails summarising the products discussed during the consultation. These emails also list any products that the customer chose to purchase based on the recommendations made. ![image](media://06d336ae-1fff-4cbf-80bd-f833d5878035) > ℹ️ More information on Consultations functionality can be found [here](https://redantdigital.atlassian.net/wiki/spaces/RET/pages/34668545). #### **Referral Emails:** A referral email is triggered when a sales associate sends a customer their shopping basket. This email provides a convenient way for customers to review the items in their basket, making it easier to complete their purchases online. ![image](media://2ce31a86-088d-444e-aa76-90adc2e87b98) > ℹ️ More information on Email Basket functionality can be found [here](https://redantdigital.atlassian.net/wiki/spaces/RET/pages/285540381/Basket#Email-Basket). #### **Payment Requests:** If a customer opts to '[Pay-by-link](https://redantdigital.atlassian.net/wiki/spaces/RET/pages/399081496)', RetailOS automatically generates payment request emails. These emails contain payment instructions and links to facilitate the payment process. ![image](media://d05218ac-bc77-4e78-b93a-1679ad5b8351) > ℹ️ More information Pay-by-link functionality can be found [here](https://redantdigital.atlassian.net/wiki/spaces/RET/pages/399081496). #### **Customer Registration:** A welcome email can be triggered after a customer has registered their details. This automated email can be disabled if the retailer has an estblished mechanism in place to trigger these types of communications (e.g. triggered by their CDP or other marketing automation platform). > ℹ️ More information on customer registration can be found [here](https://redantdigital.atlassian.net/wiki/spaces/RET/pages/379650123). ### **2. Personally curated emails sent by the sales associate** The ‘[Messaging](https://redantdigital.atlassian.net/wiki/spaces/RET/pages/33914881)’ app can support the sending and receiving of [emails](https://redantdigital.atlassian.net/wiki/spaces/RET/pages/228032537) to and from customers - this can be used by sales associates to follow up post-purchase / consultation, share products, looks, send invitations to events or simply send a birthday message. Sales Associates can utilise pre-defined, pre-formatted templates to draft replies and attach media to their communications to engage with their customers. > ⚠️ Unlike the transactional emails, customers can choose to opt-out of receiving marketing-based email communications and therefore an unsubscribe link must be included in the templates. More information can be found [here](https://redantdigital.atlassian.net/wiki/spaces/RET/pages/228032537/Email+Messaging#Opt-in-for-Email-communications). ![image](media://f425304c-edb3-4202-ab39-e430592ce233) > ℹ️ The ‘Messaging’ app can also support the sending and receiving of [SMS](https://redantdigital.atlassian.net/wiki/spaces/RET/pages/240222233) and [WhatsApp](https://redantdigital.atlassian.net/wiki/spaces/RET/pages/294158367) messages. --- ### HTML Example Templates Messaging templates can be styled to suit your brand and are relatively simple for us to do if you’re able to provide us with the HTML. Templates can be customised as needed utilising the information available in the variables file. - **Variables:** outlines what pieces of data the template receives from Red Ant and can be used within the template - **Config:** outlines what can be configured for the from/to address and subject line - **Examples of our OOTB templates:** ### Localisation RetailOS is able to send translated email communications based on the customer's [preferred language](https://redantdigital.atlassian.net/wiki/spaces/RET/pages/378503561/Customer+Profile#Preferred-Language) - this applies to transactional and personally curated emails > ℹ️ The language that the template has been translated into can be defined via the `language` column within the Message Templates table. This must be set to a valid [locale ID](https://learn.microsoft.com/en-us/openspecs/office_standards/ms-oe376/6c085406-a698-4e12-9d4d-c3b0ee3dbc4a). > ⚠️ By default, all emails are in English, however, if translated versions are provided by the retailer, these can be set up accordingly. In cases where a customer's preferred language lacks a translated version, the platform automatically reverts to using the English template. The translated messaging templates are grouped by language in the template dropdown within the message composer. ![Screenshot 2024-04-08 at 16.19.50.png](media://e84e3a31-dfbc-4ec4-a692-7f5714392d0b) > 📝 The messaging composer fully supports RTL (right-to-left) languages. When a template in an RTL language—such as Arabic—is selected, the composer will automatically: > 📝 > 📝 - Render the predefined subject line and message body in a right-to-left format. > 📝 - Adjust the text input to conform to RTL writing direction. > 📝 - Display the message preview in RTL, ensuring the sales associate can see exactly how the message will appear to the customer before sending.