Revisions – Workflow
Published On: March 29, 2022/Last Updated March 29, 2022
New Build – Revisions Awaiting Builder
Under no circumstances should Builders email or communicate directly with customers.
Please rely on our Website Specialists to communicate with our customers.
- Middle click (Open in a new tab) the second link in the summary tab ending in “- Build Revisions” and the number of revisions
- In the top right corner of the page click on the “Ready” dropdown and choose “In Progress”
- Leave an internal comment indicating you have begun work
- Once you have completed the revisions, click on the “In Progress” dropdown and choose “Send for QA”
- Input your time spent on the ticket.
- Make sure your Site Preview Link includes the whole URL (including the http://). This will be more helpful in the long run to just click on the link instead of copy/pasting it.
- In the Builder Clarifications section of the pop up, delete any existing notes that may be there and then add any notes you may have, and it is good practice to copy and paste the notes to internal comments. Make sure to notate any items that you were unable to address and why.
- Choose one of the options from the Builder Notes dropdown. Make sure to use these, as they are vital to tracking and improving our process.
- Request completed – no notes
- Request Completed – Items need to be done differently than requested
- Request Completed – Items had to be adjusted to look better
- Request could not be completed as requested
- Missing Items
- Click the “Send For QA” button again.
Technical Clarification
Do not send for non technical clarifications. They will not go to anyone and get lost in the Matrix.
Builders are expected to be skilled in technical troubleshooting for our websites, software, plugins, and applications. Do not hesitate to reach out to your team and leadership to find solutions to technical issues first.
- If the ticket needs to go to a Builder 3 for technical troubleshooting, such as Beaver Builder not loading, Click the “In Progress” dropdown and choose “Clarification Needed”
- Select the “Yes” option in the Technical Clarification dropdown. This will send the tickets to our internal Builder 3’s to troubleshoot.
- Using the Panel Template, leave notes in the ticket about the issues you have encountered.
- After you have left your notes, click on the “Clarification Needed” button.
- Once the clarification has been completed on the Builder 3 side, it will come back into our bucket for New Care Tickets.
- Note: It does not auto assign to the last builder. If you see a ticket come in that you requested a clarification for please grab it, as you probably know more about the ticket than a new person picking it up.
- Click the “Ready” dropdown and choose “In Progress”, leave your note indicating your working on the ticket, then once you have completed everything click the dropdown at the top that says “In Progress” and choose “Design Complete – Send for QA” leaving any notes you may have, including a completion note.
Panel Template
Please adjust the title and notes accordingly.
{panel:title=Technical Clarification 1 - Critical Error}
*All tasks completed except:*
*Page:* Home
*Instruction:* Add content from 3 pages on the live site onto the home page
*Issue:* Can't load page and getting a critical error on the home page only
*Steps taken to troubleshoot:*
* troubleshooting step 1 – updated plugins
* troubleshooting step 2 – uploaded .user.ini file
* troubleshooting step 3 – cleared cache from GD cORe dropdown.
{panel}