diff --git a/handbook/digital-experience/README.md b/handbook/digital-experience/README.md
index 8585db832d..1157beecd7 100644
--- a/handbook/digital-experience/README.md
+++ b/handbook/digital-experience/README.md
@@ -251,6 +251,15 @@ Fleet will occasionally release information to the press regarding upcoming init
 5. Schedule 2.5 hrs of async time for the CEO work on edits and a 60m followup postgame (solo) where CEO edits and then settles+sends final release.
 
 
+### Process the help-being-ceo Slack channel
+The Apprentice will perform the following steps to process all communication from the CEO in the [help-being-ceo Slack channel](https://fleetdm.slack.com/archives/C03U703J0G5).
+1. As soon as the message is received in the channel, add the "`:eyes:` (👀)" emoji to the Slack message to signify that you have seen and understood the task or question.
+2. In the "[¶¶¶¶ 🌪️🦿 Roundup (:help-being-ceo)](https://docs.google.com/document/d/1g7iYQ_4vwLHnlVYb9J4MdlBkFNcFfweBB4pVWRwMWpI/edit)" (confidential Google doc), create a new bullet at the bottom of the "Help-being-ceo" section and record the entire message verbatim 
+3. Prefix the bullet with the date and time of the message matching the formatting with what is reflected in Slack (e.g. 2024-05-20 01:41). 
+4. Make your prefix a link by copying the message link from Slack and linking it in the Google doc using the date and time text.
+5. Copy the entire message verbatim from Slack including all images and replies making sure to not lose any context and mimic all formatting that's included in the message. In the Slack channel apply the "`:tracking`" emoji (only available in Slack) to signify that the ask has been processed. 
+6. After each task is completed, apply the "`:white_check_mark:`" (✅) to the slack message and remove it from the [¶¶¶¶ 🌪️🦿 Roundup (:help-being-ceo)](https://docs.google.com/document/d/1g7iYQ_4vwLHnlVYb9J4MdlBkFNcFfweBB4pVWRwMWpI/edit).
+
 ### Archive a document
 Follow these steps to archive any document:
 1. Create a copy of the document prefixed with the date using the format "`YYYY-MM-DD` Backup of `DOCUMENT_NAME`" (e.g. "2024-03-22 Backup of 🪂🗞️ Customer voice").