Email marketing you run from Claude and ChatGPT

From a brief to an approved plan: phases, 10-16 emails, reminders for people who did not open or click.

# One-sentence campaign

## When to use
The user says something like "I made a course X for 497, build a 2-month campaign from next Monday".

## Steps
1. If the brief lacks the product, price, link or start date, ask one short question for the missing part. Do not ask about anything else.
2. Call plan_campaign with the brief as given. Keep reminders on (default): not opened after 3 days, not clicked after 2 days.
3. Call preview_plan and show the schedule as a short list: date, subject, reminder. Mention the number of recipients.
4. Apply the user's corrections with update_campaign_plan (fewer emails over holidays, max per week, move or remove an email).
5. When the schedule is accepted, call generate_plan_content to write every email and reminder in the brand tone.
6. Call approve_plan. Tell the user to approve in the dashboard, on their phone or by typing the code they see there. Never guess or ask for the code yourself.

## Rules
- Nothing is sent before approval. Say so once, briefly.
- Summaries in the user's language, short dash, no exclamation marks.
- One A/B subject pair per key email is enough; do not over-test.

Pick a ready recipe (welcome, sale, recurring event, abandoned cart), set the parameters, simulate, activate.

# Path from a recipe

## When to use
The user wants an automation that starts from a tag, a signup, a registration, a purchase or inactivity.

## Steps
1. Call list_recipes and pick the one that matches the request. If two match, show both in one line each and ask which one.
2. Collect the parameters the recipe needs (tag, product, link, signature). Use the brand kit for the signature when the user does not say otherwise.
3. Call create_path_from_recipe with the recipe key and parameters. It creates a draft.
4. Call simulate_path for one example person and show the steps with dates: day 0 welcome, day 2 reminder if not opened, day 7 question.
5. If the user wants changes, use update_path. Keep the recipe's reminders unless told to remove them.
6. Call enable_path. It returns an approval request; the user approves in the dashboard or with the code.

## Rules
- Recipes already contain reminders for people who did not open or click. Do not add duplicates.
- For recurring events use the recurring event recipe; it runs for every registration, so the same person can register for the next date.

Numbers, three sentences, one recommendation. Opens by humans, not machines; the share of results that came from reminders.

# Weekly report

## When to use
The user asks for a summary of the last 7 days or you are running a scheduled weekly check.

## Steps
1. Call weekly_insights. It returns the numbers, three sentences and one recommendation.
2. Call get_stats for the last 7 days and quote human opens (not machine opens), clicks, replies, bounces, revenue.
3. Call compare_campaigns for the campaigns sent that week and name what the best one had in common.
4. Call reminder_impact and state how many clicks, replies and how much revenue came from reminders.
5. Call list_opportunities and list open opportunities with their suggested action.

## Format
- Headline with the one number that changed most.
- Five bullet lines with the numbers.
- One paragraph: what to do this week.
- Everything in the user's language, under 180 words.

## Rules
- Report, do not act. Creating or sending anything is a separate request from the user.
- If a number is missing, say "no data" instead of estimating.

Duplicates, bounces, people who never engaged. A report first, then changes only after confirmation.

# List cleanup

## When to use
After an import, before a large campaign, or when deliverability drops.

## Steps
1. Call merge_report and tell the user how many real people they have and how many duplicates were merged.
2. Call get_deliverability_report and quote bounces, complaints, daily limit and warm-up state. List the items marked as "fix".
3. Call find_contacts with status bounced and status complained. Show the counts, not the addresses.
4. Call preview_segment with the rule "no mail or no open in 90 days" and show how many people are cold.
5. Propose one action per group: tag cold contacts "cooling" and run the reactivation recipe; leave bounced and complained addresses suppressed.
6. Only after the user says yes: tag_contacts for the cold group. Never call unsubscribe_contact unless the user names the person.

## Rules
- Report first, change second. Every change is a separate confirmation.
- Do not delete anything. PingsYou suppresses addresses; it does not remove history.