Adding a person to a CRM list is a software event. It does not by itself establish permission to start a customer conversation.
Keep the source of the contact
Retain how the contact joined, what messaging they requested and which business identity they expect to hear from. Bind that information to enrollment.
A tag or import event should not automatically turn an unknown record into a valid outbound recipient. Let the workflow reject missing eligibility.
Check the plan’s direction
Some messaging plans are inbound-first or reply-only. Confirm the exact outbound entitlement before building a list-triggered sequence.
The published Miss Blue automation guide describes approval for outbound-first list or tag flows. Sendblue and Blooio also distinguish initiation rights across their commercial paths.
Bound the new-contact work
Use the current provider and account controls for new conversations. Do not derive throughput from unlimited billing or treat a provider’s recommended rate as a universal Apple rule.
Hold or decline excess work in a visible queue. Scaling the worker count should not silently multiply the number of new contacts reached by the same line.
Give operators a clear stop
A person should be able to pause enrollment and invalidate pending actions when the contact no longer wants follow-ups. Preserve that decision through restarts.
Flow Studio’s simulator includes an explicit permission gate for a list-triggered example. It is a planning illustration, not a consent-management or live-send service.