Use Loop

Loop is CopyLoop’s agentic agent for planning, drafting, revising, and working with product context. It can help you reason about the current page or artifact and, where supported, prepare an action for you to review.

What Loop is good for

Use Loop to:

turn a goal and audience into a first draft
improve a subject line, section, call to action, or complete message
compare a draft with the active brand context
identify missing proof, unclear claims, or audience mismatch
prepare a reviewable content or email change
explain what information is still needed before a safe action can proceed

Loop is not a substitute for factual ownership, audience permission, or final send approval.

Where to open Loop

Loop appears on supported pages as a side rail. You can also choose Draft with Loop when creating an email.

The available context depends on where you open it:

On a content or email page, Loop can work with that artifact.
In a pre-creation flow, Loop can help shape a draft before the artifact exists.
On a broader product surface, Loop may use workspace and page context but will not assume an unrelated artifact.

The context summary in the rail tells you what Loop is working with. Check it before asking for a specific revision.

The review model

For changes, Loop follows a reviewable sequence:

You describe the outcome and constraints.
Loop reviews the available context and asks for missing information when needed.
Loop prepares a proposal for a supported action.
You inspect the proposed result.
You apply or dismiss it.
CopyLoop verifies the result and shows where to continue.

A conversation is not authorization to send email. Publishing an email, choosing a production audience, and scheduling or sending a broadcast remain separate product actions.

Write useful instructions

A strong instruction includes:

Outcome: what the reader should think, understand, or do
Audience: who the message is for and what they already know
Evidence: the proof, source, offer, or facts the draft may use
Constraints: length, structure, required language, and claims to avoid
Next action: the intended call to action

For example:

Draft a 150-word onboarding email for trial users who have not created a project. Use the active brand voice, explain the first-project benefit, do not mention discounts, and end with one CTA to create a project. Do not send it.

Conversations and context

Use a new Loop conversation when you change goals, artifacts, or audiences. Continue the existing conversation when a follow-up clearly refers to the same work.

Before relying on a response, check:

the active workspace and brand
the current artifact or page
the audience and campaign context
whether Loop used a source you trust
whether the proposed action is still current

If a proposal becomes stale after the underlying content changes, ask Loop to prepare it again instead of forcing the old proposal through.

Safe operating habits

Ask Loop to identify assumptions when source material is incomplete.
Keep factual numbers, legal claims, pricing, and customer promises tied to a trusted source.
Review the final artifact, not only the conversational response.
Use separate test audiences for delivery checks.
Treat a blocked action as a product safety boundary, not an invitation to rephrase the request until it bypasses review.

Next, follow Draft and revise with Loop or review AI generation and human review.