Chapter 13: How to Use AI the Right Way in 2027

Section 1

Build the context once

• Audience and buying situations.
• Product facts and approved claims.
• Brand voice with real examples.
• Current offers and conditions.
• Product and landing-page URLs.
• Approved customer evidence.
• Design references.
• What the output must avoid.

Use authorized data and share only what the task needs. Customer-level personal data is usually unnecessary for a creative brief.

Section 2

Turn an idea into an email brief

Act as an ecommerce email strategist. Use only the supplied brand and product context.

Create a brief for:
Audience: [audience]
Customer situation: [situation]
Product or offer: [verified details]
Goal: [goal]
Destination: [URL]

Return:
1. The main message.
2. Why it is relevant.
3. The primary CTA.
4. Supporting facts.
5. Proposed email structure.
6. Missing information.

Do not invent claims, testimonials, urgency, discounts, or product specifications. Label assumptions.

Section 3

Create and refine the copy

Using this approved brief, write three distinct email approaches.

For each, provide a subject line, preview text, headline, supporting copy, and primary CTA.

Keep the message specific and coherent. Use only verified facts. Explain how the approaches differ. Flag any claim that needs approval.

Brief:
[paste brief]

Brand context:
[paste context]

Choose the approach based on the customer and objective. Combining every generated idea usually makes the message less focused.

Section 4

Create a design and prepare it for Figma

The article calls this “GPT Astra 6” and demonstrates a roughly 5–7 minute design workflow, not a guaranteed completion time or independently verified model availability.

1. Gather the inputs

   Have the brand website URL, product or collection URL, campaign goal, offer (or none), and additional direction ready. The demonstration includes product-description context.

   Source: GPT Astra article (opens in a new tab)

2. Start with the article’s prompt

   Open ChatGPT and paste the email-designer prompt from the article. It asks for actual brand imagery, verified claims, a 640px-wide visual design, clear hierarchy, and separate editable text and artwork—not send-ready email HTML.

   Source: GPT Astra article (opens in a new tab)

3. Generate the design

   Supply your inputs and let it produce the draft. The prompt requests a visual preview, PNG and SVG versions, and an editable Figma handoff; requested deliverables are not proof that every requirement was fulfilled.

   Source: GPT Astra article (opens in a new tab)

4. Import the demonstrated handoff

   Download the generated handoff and locate the Figma importer folder and manifest.json. In Figma, create a frame, then use Plugins → Development → Import plugin from manifest and select that manifest. Locate and run the created importer; the transcript abbreviates this final selection.

   Source: GPT Astra article (opens in a new tab)

5. Edit and review

   The demonstration shows editing native text, replacing or adding images, and tidying details in Figma. The source prompt also asks for visual inspection, font and import limitations, and disclosure of whether the handoff was actually tested in Figma. Verify those for your own output.

   Source: GPT Astra article (opens in a new tab)

Strategy, audience selection, timing, and testing remain separate work. Check the finished email in your sending platform and actual email clients: a Figma layout does not verify email rendering.

Create a mobile-first ecommerce email design using the approved copy and brand references below.

Provide:
- Clear hero, supporting content, optional product section, and footer.
- Readable typography and accessible contrast.
- One primary action.
- Editable text and reusable sections where supported.
- A list of required assets.
- An explanation of the supported export or Figma handoff method.

Do not claim an export succeeded unless it actually did. Do not invent product photography, reviews, or claims.

Approved copy:
[paste copy]

Brand references:
[paste references]

Section 5

Audit performance with connected tools

Workflow framework, not a tested implementation walkthrough: no connected-account audit is demonstrated here.

Where Claude and a Klaviyo MCP connection are available, confirm the supported tools and permissions before using them. Begin with read-only analysis.

A useful audit identifies evidence and limitations rather than presenting every pattern as a cause.

Review the connected account using read-only tools.

Before analysis, state:
- Available data and date coverage.
- Attribution settings if accessible.
- Missing information.

Compare campaigns and flows over comparable periods. Separate observations, hypotheses, and recommendations.

For each finding, include the supporting metric, period, and limitation. Do not modify flows, audiences, campaigns, or account settings. Do not send messages.

Prioritize a short list of useful follow-up investigations. Do not invent unavailable data.

Section 6

Create a useful agent

This agent material is a workflow framework until a tested walkthrough is supplied; the example is a proposed role, not a deployed agent.

An agent needs a narrow job, defined inputs, permitted actions, and a stopping point.

Example: Email brief reviewer

Role

Email brief reviewer.

Input

Brief, approved product facts, and brand guidelines.

Task

Identify unclear messaging, unsupported claims, and missing inputs.

Output

A concise review with suggested corrections.

Boundary

Cannot publish, send, change offers, or modify account settings.

Human decision

Approve the revised brief.

Role: [role]
Objective: [objective]
Inputs: [authorized inputs]
Allowed tools and actions: [permitted tools and actions]
Prohibited actions: [boundaries]
Output format: [format]
When to ask for help: [uncertainty or escalation conditions]
Review owner: [person responsible]
Completion criteria: [stopping point]

Section 7

Review before using