30 Claude Prompts for ConvertKit

You are a direct response copywriter who writes high converting landing pages for creators. <context> I am building a standalone ConvertKit landing page to give away a free resource and I need the copy blocks laid out for the ConvertKit page builder. </context> <inputs> - Lead magnet title: [LEAD MAGNET TITLE] - Who it is for: [TARGET READER] - Main result they get: [MAIN RESULT] - Three supporting bullet points: [BENEFIT ONE, BENEFIT TWO, BENEFIT THREE] </inputs> <task> Write the full copy for a single opt-in landing page: headline, subheadline, three benefit bullets, a short proof or credibility line, and the form button text. </task> <constraints> Headline under 12 words. No exclamation points. Do not claim results you were not given. Button text must be an action phrase, not just Submit. </constraints> <format> Return labeled sections: Headline, Subheadline, Bullets, Proof Line, Button Text. </format>

You are a conversion copywriter who audits underperforming opt-in pages. <context> My ConvertKit landing page is converting below 20 percent and I suspect the copy is too vague about what the subscriber actually receives. </context> <inputs> - Current headline: [CURRENT HEADLINE] - Current subheadline: [CURRENT SUBHEADLINE] - Current conversion rate: [CURRENT CONVERSION RATE] - What the resource actually contains: [RESOURCE CONTENTS] </inputs> <task> Diagnose why [CURRENT HEADLINE] and [CURRENT SUBHEADLINE] likely underperform, then rewrite both to be specific about [RESOURCE CONTENTS], plus one alternate headline to test against it. </task> <constraints> Explain the diagnosis in three sentences or fewer before the rewrite. Keep both new headlines under 14 words. No vague claims like game changing or ultimate. </constraints> <format> Return Diagnosis, then Rewritten Headline, Rewritten Subheadline, and Alternate Headline for a split test. </format>

You are a launch copywriter who builds pre-launch waitlist pages for online courses. <context> I am pre-selling a course that is not built yet and I want a ConvertKit waitlist page that captures emails and sets expectations about launch timing. </context> <inputs> - Course working title: [COURSE TITLE] - Problem the course solves: [PROBLEM SOLVED] - Expected launch window: [LAUNCH WINDOW] - Early bird incentive for joining the waitlist: [EARLY BIRD INCENTIVE] </inputs> <task> Write a waitlist landing page: headline framed around [PROBLEM SOLVED], a short paragraph explaining what joining the waitlist gets them including [EARLY BIRD INCENTIVE], and form button text. </task> <constraints> Do not promise a firm launch date, use [LAUNCH WINDOW] as a range. Keep total page copy under 120 words. Avoid coming soon as standalone copy, it says nothing. </constraints> <format> Return Headline, Body Paragraph, Button Text, as plain text blocks. </format>

You are a subscription growth copywriter who writes trial offer pages for paid newsletters. <context> I run a paid newsletter with a free trial and I want three headline and subheadline pairs to test on the ConvertKit landing page that converts trial signups. </context> <inputs> - Newsletter topic: [NEWSLETTER TOPIC] - Trial length: [TRIAL LENGTH] - Price after trial: [PRICE AFTER TRIAL] - Core promise of the paid content: [CORE PROMISE] </inputs> <task> Write three distinct headline and subheadline pairs for the same landing page, each approaching [CORE PROMISE] from a different angle, plus a one line note on the psychological angle each uses. </task> <constraints> Mention [TRIAL LENGTH] and [PRICE AFTER TRIAL] clearly in at least one variant so there is no bait and switch. Headlines under 13 words each. </constraints> <format> Return three numbered variants, each with Headline, Subheadline, and Angle Note. </format>

You are a UX focused copywriter who writes confirmation and thank you pages for email opt-ins. <context> My ConvertKit form uses double opt-in and a lot of subscribers never click the confirmation link, so I need a thank you page that clearly tells them to check their inbox. </context> <inputs> - Lead magnet name: [LEAD MAGNET TITLE] - Email provider subscribers likely use: [COMMON EMAIL PROVIDER, e.g. Gmail] - Sender name shown in the confirmation email: [SENDER NAME] - Support contact if the email does not arrive: [SUPPORT CONTACT] </inputs> <task> Write thank you page copy that instructs the subscriber to check their inbox for an email from [SENDER NAME], mentions checking spam if using [COMMON EMAIL PROVIDER], and lists [SUPPORT CONTACT] as a fallback. </task> <constraints> Keep it under 80 words. Use numbered steps, not a wall of text. Do not repeat the word confirm more than twice. </constraints> <format> Return Headline and then a numbered instruction list as the body. </format>

You are a newsletter writer who turns rough notes into a finished weekly broadcast. <context> Every week I jot down a few bullet points about what happened in my business and I need those turned into a readable ConvertKit broadcast without losing my voice. </context> <inputs> - Raw bullet notes: [RAW BULLET NOTES] - Newsletter name: [NEWSLETTER NAME] - Typical sign off: [SIGN OFF PHRASE] - Length target: [WORD COUNT TARGET] </inputs> <task> Turn [RAW BULLET NOTES] into a flowing broadcast email for [NEWSLETTER NAME], keeping the order of topics but adding transitions, ending with [SIGN OFF PHRASE]. </task> <constraints> Stay within [WORD COUNT TARGET] plus or minus 10 percent. Do not invent details not present in the notes. Keep sentences short, this is an email not an essay. </constraints> <format> Return Subject line options, three choices, then the full Body as plain text. </format>

You are a launch copywriter who writes the initial announcement email for a product release. <context> I am launching a new product tomorrow and need the first announcement broadcast that goes to my entire ConvertKit list, separate from the detailed sales sequence that follows. </context> <inputs> - Product name: [PRODUCT NAME] - One sentence description: [PRODUCT DESCRIPTION] - Launch price and any discount window: [PRICE AND DISCOUNT WINDOW] - Link to the sales page: [SALES PAGE LINK] </inputs> <task> Write the day one announcement broadcast for [PRODUCT NAME], explaining what it is, who it is for, [PRICE AND DISCOUNT WINDOW], and directing to [SALES PAGE LINK]. </task> <constraints> Under 200 words. This is an announcement, not the full pitch, so do not try to overcome every objection here. One call to action link only. </constraints> <format> Return Subject line, Preview text, and Body. </format>

You are an editor who writes curated roundup newsletters with short commentary on each link. <context> I collect useful articles and tools throughout the week and want to turn a raw list of links into a ConvertKit roundup broadcast with a sentence of context on each. </context> <inputs> - List of links with rough topic: [LINK LIST WITH TOPICS] - Newsletter theme: [NEWSLETTER THEME] - Number of items to feature: [ITEM COUNT] - Optional personal intro topic: [PERSONAL INTRO TOPIC] </inputs> <task> Write a roundup broadcast with a short personal intro about [PERSONAL INTRO TOPIC], then [ITEM COUNT] items from [LINK LIST WITH TOPICS], each with a one sentence reason to click. </task> <constraints> Each item description under 25 words. Do not summarize the linked content as if you read it in full, describe why it is worth a click instead. No filler transitions between items. </constraints> <format> Return Subject line, then Intro paragraph, then a numbered list of items with title and one sentence description each. </format>

You are a community focused newsletter writer who builds broadcasts around reader feedback. <context> Several subscribers replied to my last ConvertKit broadcast with questions or comments and I want to turn the best of those into a mailbag style broadcast. </context> <inputs> - Reader questions or comments received: [READER QUESTIONS LIST] - Newsletter name: [NEWSLETTER NAME] - Tone preference: [TONE PREFERENCE] - Whether to credit first names: [CREDIT PREFERENCE, yes or no] </inputs> <task> Write a mailbag broadcast that addresses each item in [READER QUESTIONS LIST] with a clear answer, matching [TONE PREFERENCE], and crediting first names only if [CREDIT PREFERENCE] is yes. </task> <constraints> Answer each question directly before adding extra context. Keep each answer under 80 words. Do not include any identifying details beyond a first name. </constraints> <format> Return Subject line, then Question and Answer pairs in order, then a short closing line inviting more replies. </format>

You are a content repurposing specialist who condenses long articles into email friendly newsletter formats. <context> I published a long blog post and want a ConvertKit broadcast version that gives subscribers the core value directly in the email while still linking to the full piece for those who want more. </context> <inputs> - Blog post topic and key points: [BLOG POST KEY POINTS] - Link to full post: [BLOG POST LINK] - Target broadcast length: [TARGET LENGTH] - Audience familiarity level: [AUDIENCE FAMILIARITY LEVEL] </inputs> <task> Condense [BLOG POST KEY POINTS] into a broadcast of [TARGET LENGTH] that delivers the main takeaway on its own, written for someone at [AUDIENCE FAMILIARITY LEVEL], then invites a click to [BLOG POST LINK] for full detail. </task> <constraints> Do not just tease the post and withhold the value, give a real takeaway in the email itself. One link to the full post, placed naturally, not three repeated links. </constraints> <format> Return Subject line and Body as plain text. </format>

You are a marketing operations consultant who designs tagging systems inside email platforms. <context> I sell more than one product and my ConvertKit account only has a handful of tags right now, so I cannot tell who bought what or who is only interested in one topic. </context> <inputs> - Products or services sold: [PRODUCT LIST] - Lead magnets currently offered: [LEAD MAGNET LIST] - Existing tags, if any: [EXISTING TAGS] - Reporting goal: [REPORTING GOAL, e.g. know which product interest converts best] </inputs> <task> Design a full tagging structure covering purchase tags, interest tags, and source tags for [PRODUCT LIST] and [LEAD MAGNET LIST], reconciling with [EXISTING TAGS] where possible, aimed at [REPORTING GOAL]. </task> <constraints> Use a consistent naming convention, for example a prefix like purchased dash or interest dash. Keep the total tag count reasonable, do not propose more than 25 tags. Explain the naming convention in one line. </constraints> <format> Return Naming Convention Note, then a table style list grouped by Purchase Tags, Interest Tags, Source Tags. </format>

You are a lifecycle marketer who defines audience segments for targeted campaigns. <context> I want to run a win-back campaign in ConvertKit but I am not sure exactly which combination of tags and engagement data should define the cold segment I am targeting. </context> <inputs> - Available engagement data: [ENGAGEMENT DATA AVAILABLE, e.g. last open date, last click date] - Time window considered cold: [COLD WINDOW, e.g. 90 days] - Tags that should be excluded from this segment: [EXCLUDED TAGS, e.g. customers] - Total list size: [TOTAL LIST SIZE] </inputs> <task> Define the exact segment logic for a cold subscriber group using [ENGAGEMENT DATA AVAILABLE] and [COLD WINDOW], excluding anyone with [EXCLUDED TAGS], and estimate what share of [TOTAL LIST SIZE] this likely represents. </task> <constraints> State the logic as explicit rules, not vague description. Note any ConvertKit specific filter limitation you are aware of. Do not guess a precise percentage, describe it as a rough range. </constraints> <format> Return Segment Rules as a numbered list, then Estimated Share as one sentence. </format>

You are an automation architect who connects purchase events to email platform tagging. <context> My checkout tool passes purchase data into ConvertKit through automation rules and I need to specify exactly what tags should apply based on what someone buys, so my automations trigger correctly. </context> <inputs> - Products with prices: [PRODUCT LIST WITH PRICES] - Existing customer tag: [EXISTING CUSTOMER TAG] - Upsell product to flag interest for: [UPSELL PRODUCT] - Refund handling requirement: [REFUND HANDLING REQUIREMENT] </inputs> <task> Specify the tag that should apply for each item in [PRODUCT LIST WITH PRICES], how it relates to [EXISTING CUSTOMER TAG], when to apply an upsell interest tag for [UPSELL PRODUCT], and how [REFUND HANDLING REQUIREMENT] should remove or adjust tags. </task> <constraints> Be explicit about tag add versus tag remove actions. Flag any case where two rules might conflict. Do not assume a specific checkout tool's exact automation syntax, describe the logic in plain terms. </constraints> <format> Return a numbered rule list, each rule stated as When X, Then Y. </format>

You are a data hygiene consultant who audits messy email platform configurations. <context> My ConvertKit account has accumulated dozens of one-off tags over two years, many unused or duplicated, and I need a plan to consolidate before I trust any of my segment data again. </context> <inputs> - Rough list of current tags: [CURRENT TAG LIST] - Tags known to be actively used in automations: [ACTIVE TAGS] - Risk tolerance for deleting tags: [RISK TOLERANCE, e.g. cautious or aggressive] - Time available for the cleanup: [TIME AVAILABLE] </inputs> <task> Review [CURRENT TAG LIST], flag likely duplicates or one-off tags that are not in [ACTIVE TAGS], and produce a consolidation plan matching [RISK TOLERANCE] that fits within [TIME AVAILABLE]. </task> <constraints> Never recommend deleting a tag listed in [ACTIVE TAGS]. Group suggested merges clearly. Order the plan by highest impact first if [TIME AVAILABLE] is limited. </constraints> <format> Return Tags To Merge, Tags To Delete, Tags To Keep As Is, each as a short list with one line reasoning. </format>

You are a segmentation specialist who turns click behavior into interest based tagging. <context> I have several months of broadcast link click data in ConvertKit and want to convert that history into interest tags I can use for more targeted future sends. </context> <inputs> - Recent broadcast topics and links clicked: [BROADCAST TOPICS AND CLICKS] - Number of interest categories wanted: [CATEGORY COUNT] - Minimum clicks to count as genuine interest: [MINIMUM CLICK THRESHOLD] - Planned use of the tags: [PLANNED USE, e.g. targeted product announcements] </inputs> <task> Group [BROADCAST TOPICS AND CLICKS] into [CATEGORY COUNT] interest categories, propose a tag name for each, and state the click rule using [MINIMUM CLICK THRESHOLD] for when a subscriber earns that tag, tied to [PLANNED USE]. </task> <constraints> Keep category names short and consistent in style. Do not create a category for a single outlier topic. State the click rule as a plain if-then statement. </constraints> <format> Return a list of categories, each with Tag Name, Included Topics, and Tagging Rule. </format>

You are a marketing automation designer who plans visual funnel logic before building it in an email platform. <context> I need to plan out a full ConvertKit visual automation for a lead magnet funnel before I start dragging blocks around, so I do not miss a branch or dead end. </context> <inputs> - Entry trigger: [ENTRY TRIGGER, e.g. subscribes to form X] - Sequence to enter: [SEQUENCE NAME] - Condition to branch on: [BRANCH CONDITION, e.g. clicked pricing link] - End state goal: [END STATE GOAL] </inputs> <task> Map out the full automation as a step by step flow starting from [ENTRY TRIGGER], entering [SEQUENCE NAME], branching on [BRANCH CONDITION], and resolving toward [END STATE GOAL], noting every decision point. </task> <constraints> Every branch must have an explicit outcome, no dangling paths. Use plain step numbers, not diagram syntax. Flag any point where a subscriber could get stuck in a loop. </constraints> <format> Return a numbered step list with branch labels like 3a and 3b where the flow splits. </format>

You are an automation logic specialist who writes conditional rules for email sequences. <context> After my ConvertKit sales sequence ends, I need clear if-else logic for what happens next depending on whether the subscriber purchased, and I keep second guessing the branch conditions myself. </context> <inputs> - Purchase tag applied on conversion: [PURCHASE TAG] - Sequence to enter if they bought: [ONBOARDING SEQUENCE NAME] - Sequence to enter if they did not buy: [NURTURE SEQUENCE NAME] - Wait time before checking the condition: [WAIT TIME] </inputs> <task> Write the exact if-else condition to check for [PURCHASE TAG] after waiting [WAIT TIME], routing to [ONBOARDING SEQUENCE NAME] on yes and [NURTURE SEQUENCE NAME] on no. </task> <constraints> State the condition using has tag versus has not tag language matching ConvertKit's condition options. Note what happens if the tag gets applied mid-wait. Keep it to one condition, not nested conditions. </constraints> <format> Return Condition Statement, Yes Path, No Path, each as one line. </format>

You are a systems minded email operations manager who plans safe changes to live automations. <context> I need to rename and restructure a core ConvertKit sequence but it is referenced inside three different automations, and I am worried about breaking live subscriber flows. </context> <inputs> - Sequence being changed: [SEQUENCE NAME] - Automations that reference it: [REFERENCING AUTOMATIONS LIST] - Nature of the change: [CHANGE DESCRIPTION, e.g. splitting into two sequences] - Subscribers currently mid-sequence: [MID SEQUENCE COUNT] </inputs> <task> Produce a safe rollout plan for [CHANGE DESCRIPTION] to [SEQUENCE NAME], covering how to handle [REFERENCING AUTOMATIONS LIST] and the [MID SEQUENCE COUNT] subscribers already inside it. </task> <constraints> Order steps so nothing is disconnected before its replacement exists. Call out any step that risks subscribers receiving duplicate or missing emails. Keep the plan to no more than eight steps. </constraints> <format> Return a numbered rollout plan, each step with a one line risk note where relevant. </format>

You are a revenue recovery specialist who designs abandoned checkout email logic. <context> My checkout tool can push an abandoned cart event into ConvertKit and I want a clean automation plan for recovering those carts without annoying people who simply changed their mind. </context> <inputs> - Trigger event name from checkout tool: [ABANDONED CART EVENT] - Product involved: [PRODUCT NAME] - Number of recovery emails wanted: [RECOVERY EMAIL COUNT] - Exit condition if they complete purchase: [PURCHASE TAG OR EVENT] </inputs> <task> Design the automation flow triggered by [ABANDONED CART EVENT] for [PRODUCT NAME], sending [RECOVERY EMAIL COUNT] spaced recovery emails, with an immediate exit if [PURCHASE TAG OR EVENT] fires. </task> <constraints> Specify the wait time before each recovery email. State the exit condition check must happen before every send, not just once at the start. Do not recommend more than three recovery emails. </constraints> <format> Return a numbered flow list including trigger, each email's wait time, and the exit condition placement. </format>

You are a launch operations manager who prevents automation conflicts during high volume send periods. <context> I am about to run a large broadcast campaign and I am worried it will collide with existing ConvertKit automations still running for some subscribers, causing duplicate or contradictory emails. </context> <inputs> - Active automations currently running: [ACTIVE AUTOMATIONS LIST] - Segment the broadcast will target: [BROADCAST SEGMENT] - Campaign duration: [CAMPAIGN DURATION] - Emails per day limit you want to respect: [DAILY EMAIL LIMIT] </inputs> <task> Build a pre-send audit checklist that checks [ACTIVE AUTOMATIONS LIST] for overlap with [BROADCAST SEGMENT], and flags where total volume could exceed [DAILY EMAIL LIMIT] during [CAMPAIGN DURATION]. </task> <constraints> Each checklist item must be something concretely checkable, not vague advice like review your automations. Order items from highest risk of subscriber annoyance to lowest. </constraints> <format> Return a checklist as numbered items, each with a short reason it matters. </format>

You are a re-engagement specialist who writes win-back campaigns for email lists. <context> A large chunk of my ConvertKit list has not opened anything in months and I need a short win-back sequence before I consider removing them, since it is hurting my deliverability. </context> <inputs> - Newsletter name: [NEWSLETTER NAME] - Time since last open: [TIME SINCE LAST OPEN] - What originally attracted them to sign up: [ORIGINAL SIGNUP REASON] - Consequence if they do not respond: [CONSEQUENCE, e.g. removed from list] </inputs> <task> Write a two email win-back sequence for [NEWSLETTER NAME] subscribers who have not opened in [TIME SINCE LAST OPEN], referencing [ORIGINAL SIGNUP REASON], with the second email stating [CONSEQUENCE] clearly but respectfully. </task> <constraints> Do not use manipulative subject lines like are you still there with no substance behind it. Each email under 100 words. State the consequence plainly, do not hide it in fine print. </constraints> <format> Return Email 1 and Email 2, each with Subject and Body. </format>

You are a deliverability consultant who communicates list hygiene changes to subscribers. <context> I am about to remove a large batch of inactive subscribers from ConvertKit to protect my sender reputation, and I want to give the still-interested ones a final clear chance to stay before it happens. </context> <inputs> - Inactivity threshold: [INACTIVITY THRESHOLD] - Date the removal will happen: [REMOVAL DATE] - Action required to stay subscribed: [ACTION TO STAY] - Newsletter value proposition: [VALUE PROPOSITION] </inputs> <task> Write a final notice email explaining that subscribers inactive past [INACTIVITY THRESHOLD] will be removed on [REMOVAL DATE] unless they take [ACTION TO STAY], reminding them of [VALUE PROPOSITION]. </task> <constraints> Be direct about the date and consequence in the first two sentences, do not bury it. Keep total length under 120 words. No passive aggressive tone toward inactive subscribers. </constraints> <format> Return Subject line and Body. </format>

You are an email deliverability expert who diagnoses sender reputation problems. <context> My ConvertKit sending reputation dropped after a recent broadcast and I saw a spike in spam complaints, and I need to understand what to change before my next send. </context> <inputs> - Recent complaint rate: [COMPLAINT RATE] - What the flagged broadcast contained: [BROADCAST CONTENT SUMMARY] - Sending frequency over the last month: [SENDING FREQUENCY] - List growth source in that period: [LIST GROWTH SOURCE] </inputs> <task> Diagnose likely causes of the spike in [COMPLAINT RATE] given [BROADCAST CONTENT SUMMARY], [SENDING FREQUENCY], and [LIST GROWTH SOURCE], then give a concrete recovery plan for the next 30 days of sending. </task> <constraints> Do not recommend simply sending less as the only fix, address the likely root cause directly. Keep the plan actionable, no generic advice like monitor your metrics without specifics. </constraints> <format> Return Likely Causes as a short list, then Recovery Plan as a numbered 30 day outline. </format>

You are an email operations advisor who writes standing policies for list maintenance. <context> I want a written sunset policy so I stop manually deciding when to remove inactive ConvertKit subscribers and instead follow a consistent rule going forward. </context> <inputs> - Definition of inactive: [INACTIVITY DEFINITION] - Number of win-back attempts before removal: [WIN BACK ATTEMPTS] - Exceptions to the policy: [POLICY EXCEPTIONS, e.g. recent customers] - Review frequency for the policy itself: [REVIEW FREQUENCY] </inputs> <task> Write a short internal sunset policy document defining [INACTIVITY DEFINITION], the [WIN BACK ATTEMPTS] process before removal, [POLICY EXCEPTIONS], and how often to revisit the policy at [REVIEW FREQUENCY]. </task> <constraints> Write it as an internal reference document, not subscriber facing copy. Keep it under 250 words. Make every rule specific enough that someone else could execute it without asking questions. </constraints> <format> Return a document with headers: Definition, Process, Exceptions, Review Schedule. </format>

You are an email marketing analyst who explains engagement metrics to non-technical stakeholders. <context> I manage ConvertKit for a client or team and need to explain what our current open and click engagement numbers actually mean in plain terms, without email jargon. </context> <inputs> - Current open rate: [OPEN RATE] - Current click rate: [CLICK RATE] - Industry benchmark if known: [BENCHMARK, or say unknown] - Recent change worth noting: [RECENT CHANGE, e.g. rate dropped after a list import] </inputs> <task> Explain what [OPEN RATE] and [CLICK RATE] mean in practical terms, compare against [BENCHMARK] if provided, and address [RECENT CHANGE] in language a non-email-marketer would understand. </task> <constraints> Avoid jargon like deliverability without explaining it in plain words first. Keep the explanation under 180 words. Do not overstate confidence if [BENCHMARK] is unknown. </constraints> <format> Return a short written summary suitable for pasting into a client update email or internal report. </format>