Claude + Omnisend: audit, segment and draft an email-to-SMS campaign

Connect and audit before changing the account

Thanks to Omnisend for sponsoring this video.

Luke uses a demo account and starts with a read-only audit of contacts, consent, campaigns, forms and reports. The audit finds a consent problem; a contact record alone does not establish a suitable campaign audience.

1. Connect Omnisend to Claude through the MCP route shown at 1:45.
2. Ask for a read-only account and form review first.
3. Inspect the source records behind the findings and resolve unclear audience/consent data before building the campaign.

Build a segment you can inspect

The recorded example creates a 2,155-contact segment. That number belongs to the demo account, not an audience size you should reproduce.

1. Define the audience conditions in plain language.
2. Create the segment and inspect representative included and excluded contacts.
3. Compare the resulting audience with the rules before generating the draft.
4. Check the campaign wording, links, sender information and intended recipients.

Review the email → wait → SMS sequence

The later steps create the automation through the same connection. A completed diagram is not a reason to send to real people automatically.

1. Specify the trigger, wait and SMS conditions.
2. Inspect the draft messages and the actual audience selected for each step.
3. Test the sequence with appropriate demo records and your own test destinations.
4. Keep final sending approval separate from the agent’s completion of the setup.

The takeaway

The demonstrated output is a reviewed draft and automation in a demo account. The guide does not authorise sending messages or establish that a particular audience is eligible.