> 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/branding/social-sharing.md). # Sharing Channels Pick the sharing channels your customers use and write the message that travels with them. A referral spreads through the channel your customers already use to talk to friends — usually a private message, not a public post. The buttons you offer, their order, and the words that go with them decide which of those moments turns into a referral. Open your campaign and go to **Sharing channels**. Two tabs: **Channel** picks the buttons, **Message** writes what gets sent. > **Best practice:** Lead with the channel your audience uses privately, then trim the rest. On mobile, put WhatsApp and Native Share at the top; on desktop, email and X usually fit better. Fewer, well-chosen buttons produce more shares than a crowded row. ### Which channel for which customer | Channel | Best for | Notes | | --------------------------------- | ------------------------------------------------ | --------------------------------------------------- | | WhatsApp | One-to-one, mobile-first, international | Lead with it on mobile | | Native Share | Whatever app the customer prefers | Mobile only — hands off to the device's share sheet | | Native Share with message capture | The same, but Bloop records which app they chose | Mobile only | | Custom Email | Considered, personal recommendations | Sends Bloop's own template, which you control | | Mail App | Customers who'd rather write it themselves | Opens the device's default mail client | | Gmail | Desktop Gmail users | Opens a pre-filled Gmail compose window | | X (Twitter) | Public, fast, low-commitment | Tech, media and creator audiences | | Facebook | Broad public reach | Communities and older demographics | **Private channels out-convert public ones.** A WhatsApp message to one friend carries more weight than a post to a thousand strangers. Lead with private, offer public as a secondary option, and confirm the mix with an [A/B test](/referral-program/ab-testing.md). The two email options are not the same thing. **Custom Email** sends through Bloop using a template you edit, so you control the wording and can track it. **Mail App** opens the customer's own mail client with the message pre-filled — more personal, but it leaves your hands the moment they hit send. ### Pick the channels The **Channel** tab gives you separate **Desktop** and **Mobile** lists, plus a pool of **Available channels** underneath. Drag a channel into a list to enable it, drag within a list to reorder — the top channel appears first on your storefront, and it gets most of the clicks. Two rules the editor enforces: a channel can only appear once per list, and the Native Share options are mobile-only. Set the two lists separately. The channels people reach for on a phone are not the ones they reach for at a desk, and copying one list onto the other wastes the difference. ### Write the message The **Message** tab has a card per channel — **X (Twitter)**, **Facebook**, **WhatsApp** and **Email** — each with a live preview of how the share will look. | Card | What you write | | ----------- | ---------------------------------------------------------------------- | | X (Twitter) | Message, link title, link description, and the `@referrer_name` handle | | Facebook | Link title and link description | | WhatsApp | Message | | Email | Message | **Insert variable** drops the pieces Bloop fills in at send time — the store name, the referral link and code, and each side's reward value — so the message stays correct when you change the offer. Each card that produces a link preview also takes an **Image**: Bloop's default, or your own upload in `.jpeg` or `.png`, under 20 MB and 20 megapixels. Facebook renders best at 1200 × 630 px. #### Languages Pick the language at the top of the tab before you type. The message text, link titles and link descriptions are stored per language; the images and the X handle are shared across all of them. Switching language discards unsaved edits without warning, so save before you change the selector. ### What to write * **Write in the customer's voice**, not an ad's. "I love these — here's 15% off" beats "Shop our referral program". * **Name the reward in the first few words.** The recipient decides in one line whether to tap. * **Keep WhatsApp short.** One sentence and the link. * **Let the link preview do the selling** on Facebook and X — that's what the image, title and description are for. ### Common mistakes to avoid * **Offering every channel.** A crowded row turns an easy share into a decision. * **The same list on desktop and mobile.** Set them separately. * **Leading with public channels.** They add reach but convert worse per share. * **Writing one language and assuming the rest.** Check the selector, or turn on automatic translation for the campaign. * **Hard-coding the reward into the message.** Use **Insert variable** so the copy survives your next offer change. ### Next steps * Decide between links and codes in [referral methods](/referral-program/referral-methods.md). * Control how the reward value reads in [reward display](/referral-program/reward-display.md). * Confirm your channel order with [A/B testing](/referral-program/ab-testing.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/branding/social-sharing.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.