Recently we launched a Group Send pilot to test and to scale. The pilot met its objectives and the team became largely self-sufficient quickly. Group Send landed clearly as the right tool for human-led, one-to-many outreach alongside JO for automated, multistep outreaches. Early feedback is now shifting from basic usage to scale and governance:
-
Pre-filtered lists: Admins should be able to create approved, pre-filtered base lists that users can then extend/refine.
-
Shared template structure: When sharing personal templates, a folder structure for shared templates would allow scoping to a specific team.
-
Admin visibility: Email/Admin users should have visibility into Group Send templates to more easily promote proven content into JO use cases where appropriate.
-
Extend Group Send Template Availability to Group Send permissioned users at P360. CTA, and Timeline level. Group Send users should be able to access their Personal and Shared Templates from anywhere in the platform. This is not a current capability.
-
Ensure that every email has an Admin Defined privacy statement that can be enforced for all Operational Templates and Non-Operational Templates sent using Email Assist.
None of these are blockers – they’re signals of healthy adoption and teams already thinking in terms of lifecycle and scale.