Skip to content

Crowd9/giveaway-skills / skills/giveaway-winner-communications

giveaway-winner-communications

Verified

Write messages after a giveaway draw. Use for 'Winner email', 'verify the Winner', 'collect the delivery address', 'shipping update', 'announce the Winner', 'what do I send non-Winners', 'Winner has not replied', 'someone says they should have won', 'ask the Winner for a photo', or 'what do I email Entrants after the giveaway'. Include timing and follow-up.

FileKindSize
SKILL.mdskill md12.4 KB
evals/cases.mdmarkdown6.3 KB
evals/evals.jsonconfig29.4 KB
references/after-the-draw.mdmarkdown12.4 KB
references/evidence-detail.mdmarkdown3.2 KB
references/house-style.mdmarkdown4.7 KB
references/message-templates.mdmarkdown10.1 KB
scripts/style_check.pyexecutablescript40.3 KB

references/after-the-draw.md

View on GitHub
# After the draw

Advice from practice, except the subscription-Action usage table below. The campaign emails that run while entries are open belong to giveaway-promotion-plan, and the opt-in wording on the entry form belongs to giveaway-entry-method-planner. This page picks up at the moment the Winner is announced and the rest of the list is still sitting there.

## Most campaigns ran no email Action (extracted)

The email series on this page needs contact addresses and recorded marketing consent. The majority of campaigns never ran an email Action, but addresses may still come from the entry form. Marketing permission is a separate switch, the subscriber checkbox the setup skill describes, and this cut does not measure it. The share of campaigns
offering an email or newsletter Action rises with size and stays a minority at every size:

<!-- generated:wc_email_band -->
| Campaign size | Offered an email Action | Campaigns | Businesses |
|---|---|---|---|
| 100 to 250 Entrants | 25% | 33,074 | 9,533 |
| 250 to 500 | 31% | 25,681 | 6,496 |
| 500 to 1,000 | 38% | 21,838 | 5,509 |
| 1,000 to 2,500 | 44% | 20,021 | 5,077 |
| 2,500 to 10,000 | 46% | 12,714 | 2,991 |
| 10,000 or more | 41% | 3,171 | 748 |
<!-- /generated -->

So in three campaigns out of four at the small end, and in more than half at every size, the campaign ran no
email Action. That says nothing about addresses collected through the entry form or consent to the series.
The table measures which Actions campaigns offered, never how many addresses exist or who ticked a box.
Check three things before choosing the message channel:

- **Address availability.** Inspect the campaign's contact records. An address can be collected through the User Details form even when no subscription Action is offered. If there is no usable email address, use the available contact channel for the Winner and the public announcement for the audience.
- **Marketing consent.** Check each person's recorded opt-in and its scope. An Email Subscription Action gets consent through a checkbox on the User Details form. Newsletter signup also collects explicit consent. Having an address alone grants no marketing permission. Keep Winner administration separate from promotional messages.
- **Subscription-Action usage.** The table describes which Actions campaigns offered. Offering an Action establishes neither a particular person's consent nor the absence of addresses in campaigns without that Action.

Plan the promotional welcome series only for people with recorded marketing consent. When addresses exist without that consent, keep them out of the promotional series and core marketing list. When no contact address exists, use another available channel for permitted campaign administration.

Source: `analysis/output/benchmarks.json` (`ordinary_benchmark.entry_methods.by_band.share_with_family`).

## Entry welcome and post-draw messages

Common practice, our data doesn't cover this. The series starts at entry. The opening message is the welcome and referral email the promotion plan sends within a day of the sync landing, while the giveaway still runs. The three below follow the draw. Send them only to people whose recorded marketing consent covers the series, from the giveaway stream, on a fixed schedule, and stop.

| Message | When | What it does |
|---|---|---|
| 0. Welcome and referral | Within a day of entry, during the run | Confirms the entry, names the brand, carries the referral link. Written in giveaway-promotion-plan. |
| 1. Result and thank-you | With the public announcement, within a week of the draw | Names the Winner as the terms allow, thanks everyone, honors any thank-you offer promised at entry, or includes one optional offer if none was promised. This is the non-Winner message in `references/message-templates.md`. |
| 2. What the brand is for | A few days after message one | One product or one story, chosen because the Prize pointed at it. A person who entered for a coffee machine came for coffee. |
| 3. One reason to come back | About a week after message two | A single non-shopping next step: a guide or an invitation to the community. No second offer or reminder for the thank-you code. |

After message three the subscriber either joins the core list or drops out under the hygiene rule below. Three messages is the practice, chosen so the sequence finishes before entry interest fades. Adjust the count to what the business has to say.

## The code for non-Winners with marketing consent

Honor any promised offer, including its recipients, value and conditions. If no offer was promised, an optional thank-you code is a practical choice for a store. Send it only where the recorded marketing consent covers it. Mechanics, from practice:

- **One code per person.** Generate unique single-use codes in the store (Shopify Discounts supports single-use codes, and the email tool merges them per address, Klaviyo and Mailchimp both do this). A shared code lands on coupon sites within a day and the discount goes to people who never entered.
- **Expiry of 7 to 14 days.** Long enough to open the email, short enough to act on. Say the date in the subject.
- **Minimum spend or a collection limit** so the code does not turn the cheapest item free. Exclude sale items and gift cards.
- **A tier for referrers.** Entrants who referred a friend get a larger code. The referral entries are in the dataset, so the segment is a filter on the Entrant list.
- **Recipients follow the promise.** Include Winners if the promised offer covered them. For an unpromised non-Winner offer, Winners can be excluded. Send later series messages only where their recorded consent covers them.
- **Track it.** Record redemptions and the resulting order value in the store, then give those outcomes to giveaway-results-review. Name the code for the campaign so the store's reports identify it. Without the code, revenue attribution is a join of Entrant email to orders.
- **Codes during a sale.** A 15% code sent the day the store goes 30% off is dead on arrival. Before Black Friday or a seasonal sale, make the non-Winner offer early access to the sale, or a code that stacks on one item, and say which it is in the email.
- **Keep the offer optional.** A shopping discount is separate from a payment requirement to enter or claim the Prize. Honor a code already promised at entry without rewriting the terms after the draw. For a jurisdiction question, ask the organizer's lawyer: "Does our optional offer and its entry-page wording fit the promotion rules in [country]?"

## Keep the giveaway list in its own segment

Common practice, our data doesn't cover this. Use a giveaway segment to select recipients by recorded consent, measure the sends and suppress addresses under the hygiene rule below. Keep Winner claim messages separate from marketing sends according to their purpose and consent.

A segment is an audience filter, as [Mailchimp explains](https://mailchimp.com/resources/manage-your-audience/). It does not isolate sender reputation when sends share a domain and sending infrastructure. [Google tracks domain and IP reputation](https://support.google.com/mail/answer/14668346?hl=en), so a segment alone cannot promise protection for the core list.

Describe infrastructure separation only when the provider documents what it separates. For example, [Postmark separates transactional and broadcast traffic onto distinct IP ranges](https://postmarkapp.com/support/article/1082-what-types-of-messages-are-a-good-fit-for-postmark). A stream or subaccount name alone establishes no such separation. Check the provider's current setup before recommending it.

Move an address to the core list only when the recorded consent covers it and there is stronger engagement evidence: clicks that your email tool identifies as coming from people after filtering automated activity, a reply, a purchase or explicit reconfirmation. An open alone does not establish engagement. Check the provider's current [Mailchimp Apple privacy guidance](https://mailchimp.com/help/apple-privacy-faq/) or equivalent help page for how it filters automated activity.

## Watch the send

Read these in the email provider within a day or two of the Winners email, for the giveaway segment on its own.

- Unsubscribe rate on that send.
- Spam complaint rate on that send.
- Bounce rate and the provider's reported reasons, especially for hard bounces. [Mailchimp describes bounces as delivery failures](https://mailchimp.com/help/soft-vs-hard-bounces/). Inspect the reasons and where the addresses came from before choosing a remedy. A bounce does not establish why someone supplied the address.
- Clicks after your email tool has filtered automated activity, replies, purchases and explicit reconfirmations. Treat open share as uncertain because privacy features can generate opens without a person reading.

If complaints rise on the Winners email, check recorded marketing consent, where the list came from, whether recipients would recognize the sender, and the content and frequency of recent sends. Choose a remedy from those findings. A complaint increase alone does not establish that the entry form was defective. Set the numbers down beside the campaign report so the next giveaway has something to compare with.

## Hygiene before the core list

Use consent, delivery failures and stronger engagement signals to review the segment. Missing opens alone do not show that someone is inactive.

- Sunset rule (planning assumption): review addresses after their first 30 to 60 days. A proxy-open-only address has no proven engagement. A real purchase or reply can show engagement even with no recorded open. If there is no stronger signal, suppress promotional sending or send one plain reconfirmation message where the recorded consent covers it, then suppress those who do not reconfirm. Honor unsubscribes immediately regardless of activity.
- Re-permission copy, plain text, one link: "You entered the [campaign name] giveaway. Would you like to keep hearing from [Brand]? Confirm here: [link]. If not, this is the last marketing message." Subject: "Should we stop emailing you?"
- Hard bounces come off immediately.
- A role-address prefix alone does not decide list admission. Apply recorded consent, delivery status and verified engagement to every address. A consented role address with a purchase or reply can join the core list if it has not unsubscribed or hard-bounced. Check any provider-specific restrictions separately against the provider's current documentation. The disposable-domain review lines from giveaway-random-draw flag known throwaway domains for review at draw time, not customer potential or permission to send marketing.
- Only what survives this joins the core list.

## Record entry consent and marketing consent separately

Entry consent and marketing consent are separate permissions. Record each separately, even when both appear on the same form.

| Consent | Where it is given | What it allows |
|---|---|---|
| Entry consent | The entry form, by entering | Running the promotion: contacting a Winner, verifying eligibility, delivering the Prize, publishing the result as the terms describe |
| Marketing consent | A ticked opt-in box on the entry form, or an opt-in on the thank-you page | Sending the promotional messages covered by the recorded opt-in |

Entering does not subscribe anyone. Anyone without recorded marketing consent stays out of promotional messages. Winner notification, verification and delivery messages follow the campaign terms and use the contact details available. The terms script in giveaway-winner-structure writes this as a marketing-consent clause under its --marketing-consent flag.

Name the countries where Entrants live and ask the reader's own lawyer: "For these countries and this consent wording, is confirmed or double opt-in needed before we send the welcome series?" Give no country as an example of a legal requirement. If the approved process includes confirmation, send it before message one and hold unconfirmed addresses out of the series.

## One question to Entrants

Ask one question with the result email or on the thank-you page. One question, one screen, no login.

Useful shapes:

- Which of these would you rather win next time? (three options taken from the Prize shortlist)
- Where did you hear about the giveaway? (fills the gap left by referrers that arrive as direct traffic)
- Had you bought from us before entering? (yes or no, and the answer sizes how much of the list is new)

Send the answers to whoever plans the next campaign and use them to build a Prize shortlist for giveaway-prize-picker.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall