Help

Until you do, your mail goes out from the platform's address — which works, but says Zavon where your name should be. In the console, Setup → Sending domains:

• Add the domain your address ends in. Pasting a whole address works too.
• Give the two records shown — a DKIM TXT and a Return-Path CNAME — to whoever looks after your DNS. Each value has a copy button.
• When they say it is published, press I have published them. Nothing here claims a domain is ready until our delivery provider can actually see the records, which is the only opinion that counts.
• Then register the address your newsletters come from, and press Send myself a note. Check three things in what arrives: the from-name, where a reply would go, and whether it landed in the inbox rather than in Promotions. If one is wrong it is wrong for everybody on your list — and that note is the only time you find out before they do.

DNS changes can take a few minutes to a few hours to propagate. If verification does not pass at once, wait and press it again; nothing is lost in between.

Setup → Themes holds the colours and type your newsletters wear. Start from one of the presets — every colour in them is already one that can be read — then change what you need. The preview on the right is rendered by the same code that sends, so it is not an impression of the email; it is the email.

A theme belongs to your organisation and can dress several publications. Pick which one a publication wears on its own screen, under Newsletters.

A publication is a recurring mailing — “Worship Weekly”, “The Bulletin”. Each has its own unsubscribe topic, so somebody leaving one stays on the others. An email is one edition of it, built from sections, and each section from blocks.

• Drag a block to reorder it, or use the arrows — both work, and the arrows work from the keyboard. Hover between two blocks to insert one there rather than at the end.
• Text blocks take **bold**, _italic_ and [words](https://…), and the toolbar writes those for you. A blank line starts a new paragraph.
• Each block has its own alignment, spacing and background. Images can be full or half width.
• A section can have a different version per audience segment. A person sees exactly one — their highest-priority match, or the default — never two and never a blend.

The preview follows what you type, and it renders for a real member of the audience you have selected. Send a test to yourself before you send to the list.

A workflow is a series of emails spaced over days, started by something happening — somebody accepting an invitation, say. Delays resolve within a few minutes of their due time rather than on the exact second.

Somebody who unsubscribes part-way through has their run paused, and the console will not resume it. Putting a person back into a workflow they opted out of is the one thing this product will not make easy; they can resubscribe themselves through the link in any earlier message, and the workflow continues on its own.

• “Sent from Zavon rather than us.” The domain is not authenticated yet, or the publication is not pointed at your sender. Both are on the Sending domains screen.
• Verification will not pass. The records are usually right but not yet propagated, or published on the wrong host — a DKIM record added to example.org instead of pm._domainkey.example.org is the common one.
• Fewer opens than expected. Open tracking uses an image, and many mail clients now block or pre-load images. The figures are indicative; they under-count.
• Somebody says they did not get it. Their address may have bounced or been suppressed — a hard bounce or a spam complaint stops mail everywhere, on purpose. Ask them to check spam first.
• Signed out unexpectedly. Sessions are short by design. You will be taken to Accounts and returned to the page you were on.

[SENSITIVE] — tell us the organisation and what you were doing, and we will look at the actual record of it.

See also the Terms — in particular who the sender of a message is — and the Privacy Policy.