Skip to content

Conversations

Email campaigns that check consent before they send

Newsletters, appeals, event invitations and updates, sent only to people who agreed to hear about that subject on that channel. Audiences come from the records the organisation already keeps, emails are built from ready-made blocks, and the results show who opened, who clicked and who was left out and why.

Included from the Growth plan.

What it does

  • Audiences

    • Saved views of people as audiences: any filter on people, such as a role, a place or a custom field, saved for everyone.
    • Groups that staff or an automation add people to, such as everyone who signs up on a form.
    • People added or taken out by hand on a single campaign.
    • Consent checked by channel and purpose for every person, every time; anyone without it is left out and listed with the reason.
  • Writing

    • An email builder with text, pictures, buttons, columns, donate buttons with amounts, events, stories, figures and social links.
    • Starting layouts, templates and saved sections to reuse across campaigns, in the organisation’s colours.
    • Each person’s name and details merged in, with a preview as any one of them.
    • A test send to chosen addresses, and checks before sending, such as a missing subject or an audience that reaches nobody.
    • A copy readers can open in a browser, and an unsubscribe and preferences page where they choose what they get.
  • Sending

    • Send now or at a chosen time.
    • Test two subject lines on a share of the audience, and send the one with more opens or clicks to the rest.
    • Text campaigns where a number is connected, with message length and landline checks.
    • Addresses that bounce or complain are not sent to again.
  • Results

    • Delivered, opened, clicked, bounced and unsubscribed, with clicks by link.
    • Each person’s own result, and who was left out and why.
  • Journeys

    • Messages sent over time, such as a welcome series, built as automations and started from ready-made recipes.

In your kind of organisation

Examples with made-up people and projects.

  • A monthly newsletter

    to everyone who agreed to updates by email, built from last month’s layout and scheduled for Tuesday at 10.

  • An appeal

    two subject lines go to a fifth of the supporters each, and after a few hours the one with more clicks goes to everyone else, with donate buttons for three amounts.

  • An event reminder by text

    to volunteers who agreed to hear about events by text, with landlines left out before it goes.

  • A welcome series

    a welcome email when someone joins the newsletter group, and a second a week later.

Control and safety

  • Writing a campaign and sending one are separate permissions.
  • Opt-outs, from an unsubscribe link or recorded by staff, take effect on the next send.
  • Every send, open and click is on the person’s record.

Works with

  • Consent: what each person agreed to, by channel and purpose.
  • People and roles: audiences from roles and filters.
  • Forms: sign-up forms that record what each person agreed to.
  • Automations: journeys, and adding people to a campaign group as a step.
  • Texts: text campaigns from a connected number.
  • Fundraising and Gift Aid: appeals and donate buttons.

Good to know

  • Pictures can come from the Drive, or be uploaded.

Call it what you call it

Organisations rename this to: Newsletters, Mailings, Appeals, Bulletins.

Which plan you need

Included from the Growth plan.

Compare plans

See how Affinux would work for your team

A 30-minute demo, shown with your type of organisation. Or start a free trial and explore with sample data.