BOTD Chat and Scope

August 24, 2021

Hey WDS Team!

In an effort to improve our department as a whole and empower each of you individually, the build team has decided to start a new tradition. Many of you may remember the monthly emails with tips and tricks, well we are going to bring back a version of that regarding common build or logo questions that arise. If you have any questions or suggestions, please do not hesitate to reach out to your leadership to discuss and keep an eye on your inbox for some awesome resources coming soon!

The Video

The Why

BOTD is your resource for functionality questions. Due to the high demand of BOTD chats, we cannot complete on the fly changes or fixes. These should be submitted in a ticket for the builders to complete within normal SLA time frames.  https://confluence.godaddy.com/display/PWD/BOTD+SCOPE

Be courteous to your peers and keep your chats short and succinct. Holding your chat open in case you may have another question for BOTD holds up the line for everyone else waiting. The quicker the chats the more chats answered.

If you need information from the chat to relay back to a customer you can access your entire chat history here: https://l2chat.godaddy.com/history.php

The How

To avoid waiting in line use these resources first.

After checking your resources if you need help, open a BOTD chat.
When filling out the form, enter your information next to the brackets in the “Additional Information field”, and avoid removing any of the placeholder text.

Please answer ALL chat questions, including:

  • Customer Number
  • A Jira link especially if you are referencing a ticket
  • Ticket Stage. I.E. Consult, Build, Revisions, Post Publish, Care, Etc.
  • Use the correct domain of the site. Provide the temp domain if the site is not published yet, not the permanent domain.
  • Check if plugins are updated every time. For information on plugins please check out this article: http://wdsdesigns.com/help-guide/plugin-basics/.
  • Detailed explanation of the issue or question.
  • Troubleshooting steps taken, including resources used before coming to BOTD