Audit an ecommerce welcome email series
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and audit an ecommerce welcome email series.
LLMPrompt
Prompt
Copied 0
Audit my ecommerce welcome email series. Below I'll paste my signup popup (the offer and any question it asks), whether the series stops when someone buys, and every welcome email in order with its subject line, preview text, send delay, buttons, and body copy. If you can, also attach a phone screenshot of each email. Check it against these rules: 1. Email 1 sends right after signup, with no delay. 2. The promised code or offer is in the first lines of email 1, before any brand story. 3. The series has 5 to 7 emails spread over 10 to 14 days. 4. Across the series, it covers why the brand started, the problem the product solves, how it solves it, one specific customer review, and the biggest reason people hesitate (price, fit, quality, or shipping). 5. Each email asks for one action. Several buttons are fine if they all go to the same place. 6. If my popup asks a question, later emails use the answer. If it doesn't, an early email asks what they're shopping for. 7. If the offer expires, the last email gives the exact date and time. 8. The series stops once someone buys. 9. Each subject line makes clear what's inside, and the preview text adds to it instead of repeating it or showing filler like "View in browser." 10. If I attached screenshots, check each email on mobile: the offer and main button show without scrolling, the text is easy to read, and it doesn't rely on one big image. Then give me: 1. Every fix, ranked by how much it likely affects sales. For each one, quote the line from my email that has the problem, say why it matters in one sentence, and give the fix. 2. Rewrites I can paste for the top 3 fixes, in my brand's voice. Don't make up reviews, numbers, or facts about my brand. Use [brackets] for anything I need to fill in. 3. Any rule you couldn't check from what I pasted. My popup: [paste] Does the series stop when someone buys? [yes / no / not sure] My emails: [paste]
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/audit-an-ecommerce-welcome-email-series - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "audit-an-ecommerce-welcome-email-series",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}