CMS Support Plan
Documentation on how to request support for issues related to the CMS
During Digital Experience Team Working Hours
Point person: Nathan Dubord
Eastern Timezone (UTC−5)
Working hours: 9am - 6pm Eastern
- The DEX team is spread across North American time zones. Regular working hours span from 6am - 5:30pm Pacific (Convert to local timezone here).
- If you experience any issues related to our CMS that require immediate attention, please post in #digital-experience-team
- Please tag the following people: 2. Lauren Barker 3. Nathan Dubord 4. Megan Filo 5. Laura Duggan
- You can expect a response within minutes.
- All CMS related issues will be an immediate priority.
Outside Of Digital Experience Team Working Hours
Point person: Nathan Dubord
Eastern Timezone (UTC−5)
Working hours: 9am - 6pm Eastern
- The DEX team is spread across North American time zones. Regular working hours span from 6am - 5:30pm Pacific (Convert to local timezone here).
- If your issue occurs +/- 2hrs of our working hours, please text (phone numbers are available in Slack profiles) the following people based on timezone
- Eastern Timezone (UTC−5):
- Central Timezone (UTC−6):
- Pacific Timezone (UTC−8): 2. Lauren Barker
- If the issue occurs outside of our working hours, please refer to our CMS Troubleshooting Playbook.
- GitLab team members who may be able to assist via Slack include:
- Hanif Smith-Watson (UK, UTC +0)
- Gonzalo Servat (Australia, UTC+10)
- Nick Veenhof (Belgium, UTC +1)
- GitLab team members who may be able to assist via Slack include:
- If you have to wait for a Digital Experience team member to come online, you could create an issue using this template that details the problem which will get a headstart: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/new
If there is a critical stop business (on the web) error
Immediately Text
In order (numbers are in Slack profiles):
Call on the phone if no response within 15 minutes
CMS Troubleshooting Playbook
For information on troubleshooting a technical issue, refer to this playbook: CMS Troubleshooting Playbook
Last modified April 11, 2024: Remove preuss from dex coverage plan (
f1efc165
)