Draft and revise with Loop

This guide covers the two most common Loop workflows: creating a new email and revising an existing artifact.

Draft a new email

1. Open Emails and choose New Email.
2. Select Draft with Loop.
3. Confirm the active brand in the prompt or context.
4. Describe the audience, outcome, evidence, constraints, and call to action.
5. Answer any question Loop asks before it prepares the draft.
6. Review the proposal and apply it only when it reflects the requested message.
7. Continue in the email editor to check layout, links, sender settings, and reusable fields.
8. Publish the email only after normal review.

Useful first prompts:

Draft a welcome email for new customers who have completed signup but not invited a teammate.
Use the active brand and the onboarding source document. Keep it under 180 words, include one CTA,
and do not invent product capabilities.

Create a plain-language product update for existing administrators. Explain the change, who is
affected, and what they need to do. Use only the attached release notes for factual claims.

Revise an existing artifact

Open Loop from the content or email page so the artifact appears in its context. Ask for a bounded change before asking for a full rewrite.

Examples:

• “Give me three subject lines that preserve the current promise without adding urgency.”
• “Shorten the second section by 30% and keep the customer quote unchanged.”
• “Rewrite the CTA so the action is concrete and consistent with our terminology.”
• “Review this for claims that are not supported by the active source material.”
• “Make the opening more direct for an audience that already knows the product.”

Focused changes are easier to review and less likely to erase intentional work elsewhere.

Review a proposal

Before applying:

1. Read the entire proposed result.
2. Compare changed facts, numbers, names, links, and offers with the source.
3. Check that required terminology survived.
4. Confirm the proposal applies to the intended artifact and conversation.
5. Apply it, or dismiss it and explain what should change.

Applying a content proposal creates a new version where supported. That gives you a recovery point, but it does not remove the need to inspect the result.

When Loop cannot proceed

Loop may stop or narrow a request when:

• the current instruction is ambiguous or conflicts with an earlier instruction
• required product context or permissions cannot be verified
• a proposal is stale
• a requested action is not supported on that surface
• a mutation would bypass a required review or delivery step

State the outcome and missing information directly. If an email action is unsupported, continue in the normal Emails or Broadcasts workflow rather than asking Loop to claim that it completed it.

Move from draft to delivery

Loop helps create the message. Delivery still requires:

1. a published email asset
2. a verified sender and sending domain
3. an intentional audience
4. send-readiness checks
5. a separate broadcast or automation action

Use Email assets for publishing and reuse, then Plan your first broadcast for delivery.