This task connects permission-based customer communication to a measurable business journey. This guide focuses on how to group contacts by a meaningful source, need, purchase or engagement signal.
Use the control Selstack provides today
The current Email workspace uses mailing lists, not a dynamic rules-based segment builder. Open Emails → Mailing lists and create a list from a Form, a Stack source or an authorised CSV upload.
Name the audience by its real source
Use a name such as “Website audit enquiries” or “Pricing guide subscribers” so another team member understands why each contact is present. Do not label a broad customer export as a behavioural segment you did not actually calculate.
Review permission before adding contacts
A payment, support request or imported address does not automatically grant permission for every campaign. Keep source and consent evidence outside assumptions about engagement.
Select the mailing list when composing
In Compose Email, choose the intended mailing list and review its count before sending or scheduling. Selstack does not silently recalculate a dynamic segment at send time.
Troubleshoot an unexpected list
Open the mailing list and inspect its source before sending. If it was built from the wrong Form, Stack or CSV, create the correct list instead of relying on an unsupported filter rule.
Example: Choose a Useful Contact Segment
A “downloaded pricing guide” list can receive a relevant follow-up; it should not automatically include every past buyer.
If Choose a Useful Contact Segment is not working
If a segment is unexpectedly large, review its source and rules before sending any campaign.
Confirm the result
- The audience, permission and message purpose agree.
- Personalisation, links, consent and unsubscribe behaviour were tested.
- The follow-up has a clear owner and stop condition.
- Results are measured against leads, orders or replies rather than views alone.
When to ask Selstack for help
Contact official Selstack support when the saved result, status or resolved identity still conflicts with the intended record after one refresh. Include the business, page, time, safe reference and visible message. Do not include passwords, OTPs, recovery codes, full card details, BVN, NIN or unmasked bank documents.