Use this as a starting map, then adapt it to the people, tools, and permissions involved. This site does not connect to a customer system or execute an automation.

The process

1. Choose a source you can use

Start with your own guide, a permitted demonstration, or a source you can accurately summarize and credit. Do not assume access equals reuse rights.

2. Write the reader’s question

Name what the recipient will learn or do. A newsletter needs an editorial purpose, not just a product link.

3. Make a draft

Use the source to draft one practical point and a next action. Keep facts and observations intact. Do not invent results or attribute opinions to someone.

4. Review before sending

Check claims, links, disclosure, audience, mobile readability, and the actual destination of the call to action.

5. Send through an approved process

Use a consented list and the provider’s configured unsubscribe and suppression behavior. Review the response without confusing clicks with purchases.

Before this goes live

Use this local checklist to prepare the workflow. These checks are a starting point, not a full security or compliance assessment.

Checklist saved in this browser only.

Choose tools last

Start with the systems already in use. A new tool needs a specific job and a responsible owner. Confirm supported actions, plan requirements, data handling, and failure behavior before enabling an integration.

Explore tools by the work they support →

Want help mapping your version?

Prepare a brief with the process, the question, and the systems involved. Leave private customer data out.

Get hands-on help