process onboarding for a ticket
ART-1979_KNOWLEDGE_NODE-42
it's automatically put into the *queued* stage, which indicates that it needs to be picked up by a customer experience engineer.\n\n**In-progress**\n\n* *Work in progress* (WIP)\n\n  Work on the concern reported by the user has begun. When a customer experience engineer starts work on a ticket, the ticket's stage changes to *work in progress*. When they require more information, they may ask the customer for additional detail (such as logs or context), in which case the stage would change to
Tickets | Computer for Support Teams | DevRev
ART-1979_KNOWLEDGE_NODE-41
progress\n\n\n\nOpen\n\n\n\nEscalate\n\n\n\nValidate the fix\n\n\n\nAdditional detail needed\n\n\n\nCustomer responds\n\n\n\nStart\n\n\n\nFeature request accepted\n\n\n\nResolved\n\n\n\nNot valid\n\n\n\nQueued\n\n\n\nWork in progress\n\n\n\nAwaiting product assist\n\n\n\nAwaiting development\n\n\n\nAwating customer response\n\n\n\nIn development\n\n\n\nAccepted\n\n\n\nResolved\n\n\n\nCanceled\n```\n\n**Open**\n\n* *Queued* (Q)\n  The initial stage for all tickets. When a new ticket is created,
Tickets | Computer for Support Teams | DevRev
ART-1981_KNOWLEDGE_NODE-30
conversation of which you are not the owner, let the owner know to respond. It's beneficial to retain the same point of contact for the duration of the conversation unless the owner refers some another user.\n* If the conversation has a customer org that's unidentified or is new, add yourself (the customer experience engineer) as the owner of the ticket. Try to find the appropriate owner for the customer org and update the customer record accordingly.\n* Change the stage of the conversation to
Support best practices | Computer for Support Teams | DevRev
ART-1961_KNOWLEDGE_NODE-36
\xe2\x80\x9cWe have received your request for help with the following:  \n{{Ask AI > Output > Output string}}.   \nA support agent will review the request and respond within your organization's SLA.\xe2\x80\x9d\n\n\n\nAsk AI\n\n\n\nPrompt: \xe2\x80\x9cSummarize the ticket based on   \n{{Ticket Created > Output > Description}},   \n{{Ticket Created > Output > Title}},   \n{{Ticket Created > Output > Applies to Part > Name}}, and
Workflows | Computer by DevRev | DevRev
ART-12391_KNOWLEDGE_NODE-26
with *Conversation created* or *Ticket\n   created*.\n\n   This trigger is whenever a conversation or ticket gets created by your\n   customers from Portal or Plug, or any of your integration which supports\n   conversation syncing, like Slack, WhatsApp, or email. You can find the\n   integrations in our marketplace.\n2. Add the *Talk to agent* step as the next action. Fill all the required values\n   of this step. The values needed to fill here are explained below.\n3. Deploy the
Conversational workflows | Workflows | Computer by DevRev | DevRev