Subject line A/B variants by Hive Backstage

---
name: subject-line-ab-variants
description: Produce five distinct subject line variants for a show that is not selling, each anchored on a different psychological angle (urgency, social proof, curiosity, value, FOMO) and built from real show context. Trigger whenever an operator says "the [artist] show isn't moving, give me subject lines", "we need to test something different", "the open rate on the last send was flat, try new subjects", "draft A/B variants for this show", or asks for multiple subject line angles for a show that is stuck. Also trigger when the operator explicitly asks for "subject line tests", "variants for the on-sale email", or "five angles for the recap subject". This is the one Backstage skill where producing multiple options is the point of the deliverable. Use it only when the operator is explicitly testing or unstuck a stalled show. Do not use it for first-draft copy delivery (use the relevant email skill for that, which always returns one subject line).
---
# Subject line A/B variants

## What this skill does

This skill produces five subject line variants for an email send that is not performing, with each variant deliberately built on a different psychological angle. The point is to give the operator real options to test, not a buffet of equivalent rewrites of the same idea. If two of the five variants feel interchangeable, the skill has failed.

This is the one Backstage skill where multiple options is the deliverable. Every other email skill in the library returns a single subject line. This one returns five, because the operator's job here is testing and learning, not picking a final copy line.

## When to trigger

Trigger when an operator says a show is not selling, an email's open rate was flat, the last send did not move the needle, or they want to test new subject line angles before the next push. Trigger also on explicit asks for "A/B variants", "subject line tests", or "five angles for [send]".

Do not trigger for first-draft email work. Every email skill in the Backstage library (pre-show-announcement-email, on-sale-day-email, pre-sale-reminder-email, last-call-email, post-show-recap-email, before-you-go-logistics-email, loyalty-tier-email, price-drop-flash-sale-email) returns a single subject line because editorial judgment is part of the deliverable. This skill is the exception, used when the operator is explicitly running a test.

## Required inputs

Ask for these in one message before drafting.

Artist name and show context: date, venue, city. Room size matters because scarcity reads differently for a 200-cap room than a 2,000-cap room.

Where the show is sitting in the sales cycle. Public on-sale just opened. Mid-cycle, three weeks out. Final 48 hours. The right angle depends on where the show is.

What the previous subject line was and what it returned, if known. Open rate, click rate, replies. If the operator does not know the numbers, ask what the subject line said so the variants can deliberately depart from it.

What is actually true about the show. Genuine scarcity (a specific tier remaining, fewer than 50 tickets left), real social proof (sold out last time the artist played, the support is a known local act), a real curiosity hook (a setlist surprise the operator wants to tease, a guest the artist has not confirmed but is rumored). The angles need real anchors. If the operator cannot give them, the skill should ask before drafting fictional ones.

What is off the table. Some venues never use exclamation points. Some never use the artist's first name only. Some have a hard rule on length. If the venue voice profile exists, read it first. If it does not, ask once.

## The five angles

Each variant is built on one angle. The variants are labeled so the operator can map open-rate results back to the angle that won.

Urgency. The reason to act now. Pulls from a real, operator-confirmed scarcity signal. Examples of real anchors: last tier remaining, doors in 48 hours, presale closes tonight. Without a real anchor, the urgency angle becomes hype and the variant should be cut.

Social proof. The reason other people are buying. Anchors: sold out last time at this venue, support is opening for the artist on the rest of the tour, a third party (radio station, blog, festival) covered the announcement. No invented endorsements.

Curiosity. The reason to open without telling the reader what is inside. Anchors: an unusual setlist note, a rumored guest, a one-off thing the artist is doing at this show. The line should make the reader want to know more, not feel tricked when they open.

Value. The reason this show is worth the price of the ticket. Anchors: support lineup is loaded, set length is unusually long, the room is small for an artist this size. No discount-language unless the operator is actually offering a discount.

FOMO. The reason to not be the one who missed it. Different from urgency, which is about time, and from social proof, which is about others buying. FOMO is about regret. Anchors: this is the only stop in the city, the last show of the tour, the artist is touring a record cycle that will not come back.

For each angle, write one variant under 55 characters. Do not stack two angles in one subject. The whole point is isolating which angle moves the room.

## Voice

Read the venue voice profile if one exists. Subject lines are voice-sensitive even though they are short. The variants should all sound like the same venue, just hitting different angles.

Default Backstage operator voice if no profile exists: direct, specific, no hype superlatives. The variants are still the venue speaking, not five different brands.

Hard voice rules:

No em-dashes. Use commas, colons, or periods.

No all caps unless the venue voice profile uses them.

No fabricated specifics. Every anchor comes from the operator's inputs. If the urgency angle does not have a real scarcity anchor, mark the variant as "needs scarcity input" rather than write a fake one.

No emoji unless the venue voice profile uses them in subject lines.

55 character ceiling. Mobile clients truncate past 55.

## Output structure

Always use this exact structure. The operator should be able to scan it in 30 seconds.

```
# Subject line variants: [Artist] at [Venue], [Date]

**Current state:** [One sentence on where the show is in its cycle and what the last subject line did.]

**Previous subject:** [The line the operator gave you, in quotes.]

**1. Urgency**
"[Variant 1]"
Anchor: [the real scarcity signal this variant pulls on]
Best for: [the cycle phase this variant fits, e.g. "final 48 hours"]

**2. Social proof**
"[Variant 2]"
Anchor: [the real social signal]
Best for: [cycle phase]

**3. Curiosity**
"[Variant 3]"
Anchor: [the curiosity hook the operator gave you]
Best for: [cycle phase]

**4. Value**
"[Variant 4]"
Anchor: [the real value signal]
Best for: [cycle phase]

**5. FOMO**
"[Variant 5]"
Anchor: [the regret signal, distinct from time-based urgency]
Best for: [cycle phase]

**Recommended top-line test:** [Two sentences. Which two of the five angles to test against the previous subject if the operator only has bandwidth for one A/B. Editorial judgment is the point.]
```

## Hard rules

Each variant pulls on one angle, not two. If a variant could fit under two headings, rewrite it to commit to one.

If an angle lacks a real anchor, label the variant as "needs input" rather than inventing the anchor. The skill does not produce fictional scarcity or fictional endorsements. The whole library depends on the list trusting what the venue says.

If the operator's previous subject line was already strong on one angle, draft the variant for that angle anyway, but note it in the recommended top-line. The test is more useful when the previous angle is in the mix.

Pick one recommended top-line. This is the only place in the deliverable where editorial judgment lives. Do not return five equally weighted variants and end the brief there. The operator should know which two you would test first.

Keep all five variants in the same voice. The angles change. The venue does not.

## What to deliver

Return the brief in the structure above. Then add two to three sentences naming any anchor that felt thin and the single follow-up input that would make the strongest variant stronger.

Do not walk the operator through every word choice. The variants are labeled with their angle, which is enough.