CARE Call  FAQ

CARE Call FAQ

This section is an FAQ & Status reference sheet for Website Specialists on-call with a new/existing CARE customer.

jira-logo
Jira CARE Dashboard
more-files
New CARE Request
zoom logo
Zoom
Launcher
search-engine-visibility
Shopper ID
Search
voicemail.1
Email Address Search
customization
Care Training Materials

On-Call FAQ

New CARE Customers

Existing CARE Customers

Note: Self-serve is an option, not a requirement.
If the customer needs help putting in a request we can do it for them or show them how to do it.

CARE Lifecycle Statuses

Statuses: Website Care Request

Open

  • Customer submitted Care request and goes to our Prod Team to create a Temp password and Login for the Builder
  • Prod distributes it to external or internal builders depending on requests.

Ready

  • New to the queue and ready for the Builder to start Care request
  • No clarification is needed or customer provided clarification and is ready to be worked on.

In Progress

  • The request is being actively worked on at the moment by vendor, WSI, or Prod before it moves into the next status.

Clarification

  • This will create a subtask clarification ticket to be completed and addressed by WSI
  • Builder moves it to this status and it will show up “Clarification Needed” queue because the request is not clear and we need clarification from the customer.
  • WSI will assign the clarification subtask ticket to themselves to take over the clarification (it will move to your “Issues in Flight” queue) then WSI will reach out to the customer via email

Waiting for Customer

  • Builder needs clarification on a request, so WSI wrote an email to the customer and we are waiting on their response on the clarification (moves out of “Issues in Flight” queue and goes into “All Customer Clarification Needed Issues”)

Waiting for Support

  • There was a clarification and we emailed the customer for clarification and customer replied on the issue. (it will be shown in “My Issues in Flight” and “New Emails Back from Customer”)

Pending

  • Waiting for something on our end (vendor to start work, etc.)

Ready for QA

  • The request is in the queue for QA to begin QAing the request.
  • Builder puts it to this status
  • (currently Care is not going to this status)

Design QA

  • QA is currently QAing the request.
  • (currently Care is not going to this status)

Needs Edits

  • QA catches issue with the changes and needs a builder to fix the changes that need to be made.
  • Builder watches this bucket and goes through the necessary changes of what needs to be fixed.
  • (currently Care is not going to this status)

Done

  • Goes to the builder, passes QA, and request is complete. Customer gets an email about the completed request and has 5 business days (7 days) to respond before the ticket is closed automatically.

Canceled

  • Customer cancelled the request or we cancelled it without a reply in 5 business days (7 days)
  • Customer doesn’t have access to cancel their tickets, but if they call in and want us to cancel we can move the status to cancel

Closed

  • This ticket will automatically move to this status after 7 days from being “Done” and cannot be reopened

Color Key:

  • Grey - statuses mean they are in a queue ready to be grabbed for work (status category = "To Do")
  • Blue - statuses mean someone is doing work at that moment
  • Green - means it is resolved (status category = "Done")

Statuses: Clarification Subtask

Ready

  • New to the queue and ready for WSI to assign themselves as the “Assignee” on the project to reach out to the customer for clarification

In Progress

  • This clarification request is being actively worked on at the moment.

Waiting for Customer

  • WSI assigned ticket to themselves and reached out via email for clarification.

Done

  • The clarification request was completed and went back to the builder to finish the parent request.

Canceled

  • Clarification request is automatically cancelled without a reply in 5 business days (7 days).
  • Builder will move forward with all the rest of the request and not do this request because there was a clarification needed.

Color Key:

  • Grey - statuses mean they are in a queue ready to be grabbed for work (status category = "To Do")
  • Blue - statuses mean someone is doing work at that moment
  • Green - means it is resolved (status category = "Done")