Purpose
To establish a standardized process for launching Intern campaigns, ensuring clarity on script submission, seed test approval, change management, and default actions in absence of timely feedback.
Training Videos:
https://mbroadcast.sharepoint.com/:f:/r/sites/MessageBroadcast/Support/Training-Tier%201/Duke%20Energy/Duke%20-%20Internal%20INTERN%20campaign%20process%20training?csf=1&web=1&e=tygswL
KB Link: How to perform: Intern Campaign - White Glove – Entergy
Scope
This SOP applies to all Intern campaign launches managed by Convey in collaboration with Duke, where campaign scripts are submitted via Zendesk tickets.
Roles & Responsibilities
-
Convey Team:
- Perform seed test based on submitted script.
- Share test messages with Duke for approval.
-
Proceed with campaign execution based on approval status.
-
Duke Team:
- Review and approve seed test messages promptly.
- Ensure approvals are provided within the same day to avoid delays.
Step 1: Script Submission & Seed Test Approval
Duke team will provide updated and final Intern Campaign Script as part of the case in a separate attachment. To eliminate any errors during copy/paste, we prefer to receive the message in a UTF-8 format text message.
- Convey team will consider the latest update as the final script.
-
Convey will perform a seed test 24 hours prior to the scheduled campaign launch.
- The seed test message will be shared with Duke for review and approval.
- Duke must provide approval on the same day to avoid delays in the live campaign launch.
Step 2:
Change Management
- Once Duke has approved the seed test, no further changes to the script will be accepted for that campaign launch.
Step 3: Default Action in Absence of Approval
-
If Duke does not provide feedback or approval within the same day of receiving the seed test:
- Convey will proceed with the campaign using the script provided in the original Zendesk ticket.
- This ensures campaign timelines are not delayed.
Comments
0 comments
Please sign in to leave a comment.