Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1

We must complete these tickets quickly and accurately. Over time, we’ll likely shorten the SLAs - but for now, please adhere to the following:

  1. Agent assigned must complete the design (move status to “needs QA) within 4 business hours of the ticket coming in (and set to ‘needs design’).

  2. Ticket must complete the QA process (and revisions - if needed) and move to “Design Complete” stage within 8 business hours of the ticket coming in (and set to ‘needs design’).

  3. Ticket waits for user to reply

    1. If customer/user approves design via comment or does not reply within 72 hours, ticket is moved to “Done” which automatically sends a satisfaction email to requesting user and process is ended!

    2. If customer/user replies requesting changes, ticket is moved to “Needs Revision”

      1. If designer has questions for customer proposal desk designer comments questions in ticket and moves ticket status to “Needs customer feedback”. Once customer has responded designer ticket automatically moves back to Needs Revision status and designer is notified via email/jira notification. Repeat this step until request is fully understood.

      2. Designer completes revisions and moves ticket to “Revision QA” status

        1. If internal revision is needed, QA team member adds internal comment to ticket and moves back to “Needs Revision” and design team member updates

      3. QA team member moves status to “Revision Complete” which automatically notifies customers that their design is complete.

        1. Ticket must be moved to Revision complete within 24 hours of status being set to Needs Revision.

  • No labels