> For the complete documentation index, see [llms.txt](https://docs.bloop.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloop.plus/referral-program/emails.md). # Email Notifications Bloop sends 16 referral emails automatically — the invite that asks a customer to share, the reward that thanks them, and reminders that bring a forgotten code back into use. Each is a template you can turn on/off, personalise with variables, and time with a trigger. Configure them under **Branding → Emails**. > **Best practice:** The invite and successful-referral emails matter most — one drives sharing, the other reinforces it. Write them warm and personal, not transactional, and always send yourself a test before going live. For copy ideas, see [referral email templates](https://bloop.plus/blog/referral-email-template/). ### The referral emails Bloop can send | Email | Goes to | When it sends | | ------------------------------------------------------------- | -------- | --------------------------------------------------------- | | Sharing | Referee | A referrer shares by email through the widget | | Invite | Referrer | A customer joins the program | | Gift | Referee | A referee is sent a gift/discount code | | Successful referral (discount / store credit / cash / custom) | Referrer | A referral converts — one template per reward type | | Pending referral | Referrer | A referral is recorded but the reward is under review | | Denied referral | Referrer | A referral didn't qualify | | Not enough referrals | Referrer | Referral succeeds but a referee-count goal isn't met yet | | Referrer / Referee reward expiry | Both | A reward is close to expiring (default: 3 days before) | | Remind referrer / referee | Both | Nudge to use an unredeemed reward (default: 7 days after) | | Cash payout | Referrer | A cash reward has been paid out | | Remind referrer to refer | Referrer | Recurring nudge to keep sharing (default: every 2 weeks) | If you only ever polish two, polish the **invite** and the **successful-referral** email — the invite decides whether a customer ever shares, the successful-referral email decides whether they share *again*. ### What makes a referral email work * **Name the benefit in the subject line.** "Your friend Maya sent you 20% off" beats "You have a new notification." * **Personalise it.** Use the real reward (`{{ReferrerReward}}`), the coupon code, and — on the sharing email — the referrer's own note (`{{Message}}`). * **One action per email.** Share, redeem, or come back — not two asks at once. * **Timing matters.** A thank-you should land the moment a referral converts; reminders work because rewards are forgotten, not refused. ### How triggers work | Trigger | What it means | | ------------ | ----------------------------------------------------------------------------------- | | Immediate | Sends as soon as the event happens (default for most emails) | | Delayed | Sends a set number of days after the event | | Event after | Sends days after a reference event — used for reminders | | Event before | Sends days before a reference event — used for expiry warnings | | Recurring | Sends repeatedly until a stop condition (referral count, send count, or time limit) | Defaults: reward-expiry warnings fire 3 days before, reminders fire 7 days after, and "remind referrer to refer" repeats every 2 weeks until 12 months. ### Enabling and disabling emails Every email can be turned on or off independently. Turning one off doesn't delete your edits, and only affects events going forward. ### Editing an email template Open any email under **Branding → Emails** to edit its **subject**, **body**, **button** (text, colour, link — leave text empty to hide it), and **image** (paid plans). Changes apply to every future send. The button links to your store by default; point it elsewhere, like your referral landing page, using the redirect option. ### Template variables Variables are placeholders like `{{StoreName}}`. Bloop fills them in at send time; an unfilled variable is left as-is rather than shown blank. | Variable | Fills in | | ------------------------------------------------------------------ | ---------------------------------------- | | `{{StoreName}}` | Your store name | | `{{ReferrerName}}` | The referrer's name | | `{{ReferrerReward}}` / `{{RefereeReward}}` | Each side's reward | | `{{ReferralLink}}` / `{{ReferralCode}}` | The referrer's link or code | | `{{CouponCode}}` | The recipient's discount code | | `{{ReferrerMinimumRequirement}}` / `{{RefereeMinimumRequirement}}` | The minimum each side must meet | | `{{ReferrerCodeExpired}}` / `{{RefereeCodeExpired}}` | Time until each code expires | | `{{RemainQuantityOfReferees}}` | How many more friends the referrer needs | | `{{Message}}` | The referrer's personal note | ### The referral hub button Referrer-facing emails carry a button to their [referral hub](/referral-program/referral-hub.md), already signed in — nothing to configure. It's left off referee emails and the reward-earned success emails. If you send through Klaviyo or Mailchimp, use the permanent hub link instead (`BLOOP Hub Portal` / `BLOOPHUB`) — see [Klaviyo](/referral-program/integrations/klaviyo.md) and [Mailchimp](/referral-program/integrations/mailchimp.md). ### Languages Each email has one template per store — no separate language versions. The on-site widget itself supports multiple languages; see [social sharing branding](/referral-program/branding/social-sharing.md). ### Test before you go live Send yourself a test before relying on an email — it uses sample values so you can preview it exactly as a customer would, on both desktop and mobile. ### Common mistakes to avoid * **Writing transactional, not personal.** Warm beats formal — this is a recommendation between friends, not a receipt. * **Two asks in one email.** One email, one button, one action. * **Going live without a test send.** A broken variable or cut-off subject is invisible until a customer sees it. ### Related * [Referral rewards](/referral-program/rewards.md) — set the discount, store credit, or cash these emails announce. * [Social sharing branding](/referral-program/branding/social-sharing.md) — the on-site widget and its languages. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.bloop.plus/referral-program/emails.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.