> 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 Configure the emails that hand over links, confirm rewards and rescue forgotten codes. Most of your referral programme's contact with customers happens by email — the welcome that hands over a link, the thank-you that confirms a reward, the reminder that rescues a forgotten code. Bloop sends these automatically, and each one is a template you can rewrite, style, time and switch off. Open your campaign and go to **Email notifications**. Emails belong to the campaign, so a second campaign gets its own set. > **Best practice:** If you only ever polish two, polish the **welcome** email and the **successful reward** email. The welcome decides whether a customer ever shares; the successful reward decides whether they share again. Send yourself a test of both before you go live. ### The emails Bloop sends The page splits into **Referrer** and **Referee** tabs. #### To the referrer | Email | When it sends | | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | Welcome to referral program | They join — carries their referral link and what they'll earn | | Successful rewards | A referral converts. One template per reward type: discount, credit, cash, custom, free product | | Pending rewards | A reward is earned but waiting on review | | Decline rewards | A referral didn't qualify | | Not enough referees to receive reward | A referral succeeded but a referee-count minimum isn't met yet | | Referral progress | Each successful referral while [tier rewards](/referral-program/tier-rewards.md) are on — which tier they're at and what's next | | Reward expiry reminder | Before their unused discount code expires | | Reward reminder | Their discount code is still unused | | Cash payout notification | You marked their [cash payout](/referral-program/management/orders.md#pay-out-cash-rewards) as paid | | Remind referrer to refer | A recurring nudge to referrers who haven't referred anyone yet | #### To the referee | Email | When it sends | | ------------------------------- | ------------------------------------------------ | | Email invitation from referrers | A referrer invites them by email | | Discount claim | They enter their email — carries the coupon code | | Reward expiry reminder | Before their unused code expires | | Reward reminder | Their code is still unused | The **email invitation** is the only one written partly by your customer: it carries their own note. Keep your template's framing light around it — the personal line is what makes it work. ### Edit a template Open any email to get the editor and a live preview beside it. | Field | What it controls | | ------------------- | ---------------------------------------------------------------------------------- | | Subject | The subject line. Variables work here too | | Content | The body | | Banner image | `.jpeg` or `.png`, under 20 MB and 20 MP, best at 1200 × 704 px — or **No Image** | | Button content | The button's text, font, and hover colour. Leave the text empty to hide the button | | Hub redirect button | Where the button sends them | **Reset to default** puts a template back to Bloop's copy if an edit goes wrong. The preview shows the **From** address alongside the subject. If it's not the address you want customers to see, change it in [email sender settings](/account-and-settings/email-sender.md). Editing the **Referral progress** email, you can set which tier the preview highlights — the template branches on tier position, so check the one your referrers will actually be at. #### Where the button goes By default the button takes referrers to their [referral hub](/referral-program/referral-hub.md), already signed in — the single best destination, because everything they might want next is on it. If you'd rather point somewhere specific, fill in a path such as `/about-us` and the button redirects there instead. Use it when an email has a job the hub can't do — a product launch, a survey — and leave it alone otherwise. ### Time the send Each email carries its own schedule: | Option | Used for | | -------------------------------- | ------------------------------------------------ | | Send immediately post-enrollment | The default for anything that reacts to an event | | Send *N* days post-enrollment | Delayed welcomes and onboarding nudges | | Send *N* days before expiry | Expiry warnings | | Send *N* days after event | Reminders on an unused reward | | Recurring, every *N* weeks | The "remind referrer to refer" nudge | A recurring email needs a stopping rule, and you pick which: stop once the referrer has a number of successful referrals, stop after a number of emails, or just let the twelve-month limit end it. Every recurring email stops after **12 months** from the contact's enrolment regardless. Set a stopping rule you'd be comfortable receiving yourself. A reminder that keeps arriving after someone has clearly opted out in spirit costs more goodwill than the referral is worth. ### Turn emails on and off Every email has its own switch. Turning one off keeps your edits and only affects sends from that point on. Be careful turning off the pending and declined emails: they're the ones that explain a reward that didn't arrive. Without them, a referrer's only signal is silence, and silence generates support tickets. ### Template variables Variables are placeholders like `{{StoreName}}` that Bloop fills at send time. **Insert variable** in the editor lists the ones valid for the template you're editing — they differ by email, since a referee's template has no referrer reward to show. | Variable | Fills in | | ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- | | `{{StoreName}}` | Your store name | | `{{ReferrerName}}` | The referrer's name | | `{{ReferrerReward}}` / `{{RefereeReward}}` | Each side's reward — rendered through your [reward display](/referral-program/reward-display.md) text | | `{{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 on an invitation | An unfilled variable is left as written rather than rendered blank — which is why a typo in a variable name shows up in a customer's inbox as `{{ReferralLnk}}`. Insert them from the menu rather than typing them. ### Send a test **Send test email** delivers the template to any address you name. Use the address of a **real referrer** — Bloop fills the variables from their actual data, so you see the email a customer would get rather than placeholder text. Check it on a phone as well as a desktop. Most referral emails are read on one. ### Sending through Klaviyo or Mailchimp If you send lifecycle email through a platform you already own, Bloop can hand the events over instead of sending its own — see [Klaviyo](/referral-program/integrations/klaviyo.md) and [Mailchimp](/referral-program/integrations/mailchimp.md). Those flows carry a permanent hub link as a profile property (`BLOOP Hub Portal` in Klaviyo, `BLOOPHUB` in Mailchimp), so an email sent days later still signs the referrer in. ### Remove the watermark Bloop's emails carry a **Powered by BLOOP Referrals & Affiliates** line. **Request to remove** on the Email notifications page starts the process with support. ### Languages Each email has one template per campaign — there are no per-language versions here. If you sell in several languages, that's a reason to run a campaign per language rather than translating inside one. ### Common mistakes to avoid * **Writing transactional, not personal.** 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 a cut-off subject is invisible until a customer sees it. * **Turning off the pending and declined emails.** Silence about a missing reward becomes a support ticket. * **Typing variables by hand.** Use Insert variable — a misspelled one ships as literal text. ### Next steps * Set the rewards these emails announce in [Referrer and referee rewards](/referral-program/rewards.md). * Control how the reward value reads in [reward display](/referral-program/reward-display.md). * Give referrers somewhere to land in the [referral hub](/referral-program/referral-hub.md). --- # 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.