Ok - this may be cake - but I figure go about checking on this one with the community before I deploy. I figure someone else can benefit from seeing an order of operations to deploy to a message to a group.

My goal | deploy the activation message purely to those within a group in as few steps as possible. Unfortunately, I cannot see a way to target a group from the users tool for doing a “group push”, so I think this exercise will need to be done via the csv upload.

Setting the stage, I have had a series of smaller go lives, and I want to effectively go live with a group that is already part of the user base and assigned a branch.

Here is the order of operations that I can dream up:

1. Develop said group in excel or directly in my instance.
2. Activate the group as manual OR automatic to achieve the desired “moving forward” business.
3. Upload a csv or add metadata parameters to the system to isolate my group automatically going forward.
4. Download the grouping via the download csv function in tools.
   1. If automatic, ground truth against a static list (this is an extra step for sanity) if said list is available - verify it with the customer.
   2. Add said group to the notifications? They are in a branch that currently has their activation notifications enabled (so this may be overkill in my case, but it is an important step with soft golives to ensure that your cohort has these enabled).
5. After verification - upload the csv via the user group with user tools.
6. Under the General Import Options - Check off “Send Notifications”
7. Match fields in importer (consider using only username as the minimal is only critical).
   1. Save a preset - so I dont have to ever do this again.
8. Click IMPORT.
   1. Hold breath.
9. Group is now ready for other messaging deployments (LP or course messaging).

And so? What am I missing?????