From b0b641cd70d7d74827170db43948333f03a5cfc4 Mon Sep 17 00:00:00 2001 From: Shell Escalante Date: Fri, 2 Feb 2024 15:05:45 -0800 Subject: [PATCH] Update comms-sign-off.mdx --- .../risk-mitigation/comms-sign-off/comms-sign-off.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/workflow/implementing/risk-mitigation/comms-sign-off/comms-sign-off.mdx b/docs/workflow/implementing/risk-mitigation/comms-sign-off/comms-sign-off.mdx index 14fc1e246..bbedcc896 100644 --- a/docs/workflow/implementing/risk-mitigation/comms-sign-off/comms-sign-off.mdx +++ b/docs/workflow/implementing/risk-mitigation/comms-sign-off/comms-sign-off.mdx @@ -3,6 +3,8 @@ title: Comms Sign-off slug: /comms-sign-off sidebar_position: 4 --- +If your experiment includes ANY message, make sure you had an [in-product message consult](https://mozilla-hub.atlassian.net/wiki/spaces/FIREFOX/pages/208308555/Message+Consult+Creation) and filed an [FXE Jira ticket](https://mozilla-hub.atlassian.net/jira/software/c/projects/FXE/boards/543) that was triaged via the Desktop or Mobile messaging leads (Venetia and Courtney). + +This is to ensure we are using a consistent voice with users - and also to make sure we don’t inadvertently send multiple messages that don’t flow together to the user. -Under construction 🚧