Moosend

Build a branded newsletter and reuse a content block.

Build a group that clicked a named email within 30 days but has not purchased; show it updates.

Subscribe a test contact and start a timed welcome sequence.

Identify who clicked, bounced or unsubscribed, rather than only a campaign total.

Unsubscribe a test contact and show they cannot receive the next marketing send.

Show how a customer-owned sending domain is authenticated.

Compare two subject lines with a defined winning measure.

Show different offers within the same campaign based on a contact field.

Wait two days and send different follow-ups to clickers and purchasers.

Let a contact stop one topic while retaining another.

Import an existing list with custom fields and identify duplicate records.

Retrieve campaign results or recipient events through an API.

Insert a relevant product or order detail from a connected store.

Stop a sequence after conversion and define if a contact may re-enter.

Separate the person drafting a campaign from someone allowed to send it.

Review desktop and mobile rendering and send a test before publication.

Export a segment and its relevant engagement records in a usable format.

Generate a subject or email from a brief, then edit it before sending.

Show how historic engagement changes an individual contact's send time.

Create an audience or explain campaign performance through a natural-language prompt.

Enter a journey when a form, purchase or named event occurs.

Route contacts differently according to behaviour and profile data.

Pause a journey for a defined period before the next action.

Send email and another channel within one coordinated journey.

See how many contacts reached each step and where they stopped.

Remove a contact from a sales reminder after purchase.

Set whether and when a contact can repeat the same journey.

Change a contact's eligibility when their behaviour changes.

Increase and decrease a score based on different actions.

Assign a qualified lead and preserve the triggering context.

Trigger an external system and show the event payload.

Test two paths and compare the chosen outcome.

Hold messages outside selected days or time windows.

Block one channel after permission changes while preserving allowed actions.

Show how overlapping journeys avoid excessive messages.

Run a test contact and inspect the sequence of steps taken.

Restrict who can alter or activate a live journey.

Describe a journey and inspect the generated steps before activation.

Demonstrate a predictive recommendation based on engagement or purchase data.

Ask which journey step needs attention and inspect the supporting data.