handle scenario when an agent is on holiday
ART-1976_KNOWLEDGE_NODE-28
scenarios\n----------------------------\n\n* Ticket routing based on customer inquiry keywords.\n* Group-specific routing based on customer account assignments.\n* Assignment routing based on severity and subtype.\n* Custom field and tag-based routing.\n* First responder ticket assignment.\n\nSystem requirements\n-------------------\n\n* Administrator privileges are required for workflow deployment and execution.\n* User status (active/away) is configurable through the profile
Routing | Computer for Support Teams | DevRev
ART-2024_KNOWLEDGE_NODE-27
help now... ask again in 5d\n\nSample response:\n\n> I am unable to assist you at the moment, however please reach out to me again in five days and I will be happy to help you.\n\n### Summarize\n\nUsing the summarize command, you can sum up the entire conversation. It applies to the following:\n\n* Conversation\n* Tickets\n* Issues\n* Part\n* Workspace\n* Customer\n* Account\n\nSample response:\n\n> **Summary:**\n>\n> * Rahul from DummyOrg is having difficulty installing the Plug Widget.\n> *
Slash commands | Automate | Snap-ins | DevRev
ART-3205_KNOWLEDGE_NODE-26
and click **Deploy snap-in**.\n3. Open the Workflow Builder and locate the **Set User Preference For Group** action node.\n4. Select the users you want to set as online in the **Users** input field, along with the group they belong to in the **Group**. Remaining group members are automatically set as offline.\n\n[PreviousSmart issue creator](/docs/automations/smart-issue-creator)[NextSLA status change Slack notifier](/docs/automations/sla-change-notifier)\n\n#### On this page\n\n* [Installing
Set user preference for group | Automate | Snap-ins | DevRev
ART-1981_KNOWLEDGE_NODE-26
a small number of tags to help categorize tickets. For example, at DevRev we have the following: bug, feature-request, other-request, question, and incident.\n* Designate one or more customer experience engineers to be on call. Add them to the **Support** group inside **Settings > Groups** and as default owner in the **Support Routing** snap-in. Default owners are notified through email and the DevRev app as soon as a new conversation is started.\n\nMonitor the inbox\n-----------------\n\n*
Support best practices | Computer for Support Teams | DevRev
ART-1976_KNOWLEDGE_NODE-27
created > Output > ID Owned by > Set: Pick user > Output > User |\n\nPick user node capabilities\n---------------------------\n\n* Object: Selection of ticket or conversation routing type.\n* Group: Selection of routing destination group.\n* Users: Selection of specific ticket assignment users.\n* Strategy: Selection of assignment methodology (round-robin, load balancing, random).\n* Agent availability: Assignment filters based on agent status (away or active).\n\nAdditional routing
Routing | Computer for Support Teams | DevRev