WB Listora - Feature Announcement Email Template

Use this template whenever shipping a significant new feature. Fill in the bracketed sections. Send-time recommendation and A/B subject variants included.

---

Subject Line Variants (A/B test one pair per send)

Pair 1 - Benefit-led

• A: {{Feature name}} is now in WB Listora {{version}}
• B: New in WB Listora: {{one-sentence benefit}}

Pair 2 - Curiosity-led (for engaged lists)

• A: We just shipped something you asked for
• B: {{Feature name}} - what it is, why we built it

Recommendation: Pair 1 performs better for cold or disengaged segments. Pair 2 works for highly engaged users who open consistently. Test send time: Tuesday or Wednesday, 9-11am recipient local time.

---

Email Body

Preview text: {{One-sentence description of the feature and its benefit}}

---

Hi {{first_name}},

We just shipped {{feature name}} in WB Listora {{version}}.

What it does:

{{Two to three sentences describing the feature in plain language. Lead with what the user can now do, not what we built. Example: “You can now rate individual aspects of a business separately - Food, Service, Value, Ambiance - instead of just an overall star rating. Each aspect gets its own score. The composite breakdown appears on the listing detail page and in search result facets.”}}

Why we built it:

{{One to two sentences on the context or problem this solves. Keep it honest - don’t overclaim. Example: “The most common support request we got after launch was ‘I want to give five stars for the food but two stars for the service.’ The overall average wasn’t telling visitors what they actually needed to know.”}}

How to use it:

{{Two to four numbered steps or one short paragraph. Link to the relevant docs page if available.}}

1. {{Step 1}}
2. {{Step 2}}
3. {{Step 3}}

See the full documentation →

Who gets this:

{{Which tier. Example: “This feature is included in WB Listora Pro. If you’re on Free and want to upgrade, current pricing is at wbcomdesigns.com.”}}

---

Questions? Reply to this email - we read every one.

The Wbcom Designs Team

---

Checklist Before Sending

• Feature name matches the one used in the changelog and docs
• Version number is correct
• Documentation link is live and tested
• “Who gets this” tier note is accurate (Free / Pro / both)
• Tested render in Gmail, Apple Mail, and Outlook
• Plain-text version prepared alongside HTML
• Unsubscribe link present and functional
• Send-time scheduled for recipient-local business hours

---

Tone Notes

• Write in second person (“you can now…”), not first person (“we added…”)
• Two to three sentences per paragraph maximum
• No “excited to announce” - start with what the user can do
• No marketing language: no “powerful,” no “seamless,” no “game-changing”
• If the feature has a limitation worth knowing, mention it honestly - it builds trust