<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Workflow/Automations &#8211; SupportCandy</title>
	<atom:link href="https://supportcandy.net/docs-category/workflow/feed/" rel="self" type="application/rss+xml" />
	<link>https://supportcandy.net</link>
	<description>The most reliable customer support plugin and ticket system for WordPress</description>
	<lastBuildDate>Fri, 24 Jan 2025 09:24:38 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://supportcandy.net/wp-content/uploads/2022/07/cropped-logo-32x32.png</url>
	<title>Workflow/Automations &#8211; SupportCandy</title>
	<link>https://supportcandy.net</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>General</title>
		<link>https://supportcandy.net/docs/general/</link>
		
		<dc:creator><![CDATA[Milind Ighe]]></dc:creator>
		<pubDate>Mon, 10 Jul 2023 11:38:22 +0000</pubDate>
				<guid isPermaLink="false">https://supportcandy.net/?post_type=docs&#038;p=328277</guid>

					<description><![CDATA[The Workflow feature in SupportCandy helps you automate and simplify ticket management. Workflows are sets of rules and actions that are performed automatically or manually to make your support process faster and more efficient. Types of Workflow Automatic Workflow This type runs automatically based on triggers and conditions you set. How It Works: Choose a [&#8230;]]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="328277" class="elementor elementor-328277" data-elementor-post-type="docs">
				<div class="elementor-element elementor-element-52177f0b e-flex e-con-boxed e-con e-parent" data-id="52177f0b" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-50878003 elementor-widget elementor-widget-text-editor" data-id="50878003" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									
<p>The <strong>Workflow</strong> feature in SupportCandy helps you automate and simplify ticket management. Workflows are sets of rules and actions that are performed automatically or manually to make your support process faster and more efficient.</p>
<h3>Types of Workflow</h3>
<ol>
<li>
<p><strong>Automatic Workflow</strong></p>
<ul>
<li>
<p>This type runs automatically based on triggers and conditions you set.</p>
</li>
<li>
<p><strong>How It Works:</strong></p>
<ol>
<li>Choose a <strong>Trigger</strong>: A trigger is an event that starts the workflow. For example, when a ticket is created, a reply is added, the status changes, or a custom field is updated.</li>
<li>Set a <strong>Condition</strong>: Define when the workflow should run by adding rules. For example, &#8220;Category equals &#8216;Technical Support'&#8221;.</li>
<li>Add <strong>Actions</strong>: Decide what the workflow will do, such as adding a reply, changing the ticket status, assigning it to an agent, or updating a ticket property.</li>
</ol>
</li>
<li>
<p>Once everything is set up, the workflow will automatically perform the actions whenever the conditions are met.</p>
</li>
</ul>
</li>
<li>
<p><strong>Manual Workflow</strong></p>
<ul>
<li>
<p>This type is triggered manually by a user with permission.</p>
</li>
<li>
<p><strong>How It Works:</strong></p>
<ol>
<li>Set <strong>Conditions</strong>: Define the rules for the workflow, such as &#8220;Priority equals &#8216;High'&#8221; or &#8220;Category is &#8216;Billing'&#8221;.</li>
<li>Add <strong>Actions</strong>: Decide what the workflow should do, such as assigning the ticket or changing its status.</li>
<li>Save the workflow.</li>
</ol>
</li>
<li>
<p>Users with permission will see a <strong>Workflow Widget</strong> on the ticket page.</p>
</li>
<li>
<p>If the conditions are met, users can click to trigger the workflow, and the set actions will be performed.</p>
</li>
</ul>
</li>
</ol>

<h5 class="wp-block-heading">Widget</h5>

<p>You can enable or disable the widget from <strong>Support → Settings →</strong> <strong>Ticket Widgets</strong> <strong>→</strong> <strong>Workflow<br /><br /></strong>This widget will be visible only if you have any manual workflows.</p>
								</div>
				</div>
				<div class="elementor-element elementor-element-4c5602d elementor-widget elementor-widget-image" data-id="4c5602d" data-element_type="widget" data-e-type="widget" data-widget_type="image.default">
				<div class="elementor-widget-container">
												<figure class="wp-caption">
											<a href="https://supportcandy.net/wp-content/uploads/2023/07/SupportCandy-Workflow-widget-on-ticket-page.png" data-elementor-open-lightbox="yes" data-elementor-lightbox-title="SupportCandy Workflow widget on ticket page" data-e-action-hash="#elementor-action%3Aaction%3Dlightbox%26settings%3DeyJpZCI6MzQyOTYwLCJ1cmwiOiJodHRwczpcL1wvc3VwcG9ydGNhbmR5Lm5ldFwvd3AtY29udGVudFwvdXBsb2Fkc1wvMjAyM1wvMDdcL1N1cHBvcnRDYW5keS1Xb3JrZmxvdy13aWRnZXQtb24tdGlja2V0LXBhZ2UucG5nIn0%3D">
							<img fetchpriority="high" decoding="async" width="800" height="341" src="https://supportcandy.net/wp-content/uploads/2023/07/SupportCandy-Workflow-widget-on-ticket-page-1024x436.png" class="attachment-large size-large wp-image-342960" alt="" srcset="https://supportcandy.net/wp-content/uploads/2023/07/SupportCandy-Workflow-widget-on-ticket-page-1024x436.png 1024w, https://supportcandy.net/wp-content/uploads/2023/07/SupportCandy-Workflow-widget-on-ticket-page-300x128.png 300w, https://supportcandy.net/wp-content/uploads/2023/07/SupportCandy-Workflow-widget-on-ticket-page-540x230.png 540w, https://supportcandy.net/wp-content/uploads/2023/07/SupportCandy-Workflow-widget-on-ticket-page-768x327.png 768w, https://supportcandy.net/wp-content/uploads/2023/07/SupportCandy-Workflow-widget-on-ticket-page-1536x654.png 1536w, https://supportcandy.net/wp-content/uploads/2023/07/SupportCandy-Workflow-widget-on-ticket-page-360x153.png 360w, https://supportcandy.net/wp-content/uploads/2023/07/SupportCandy-Workflow-widget-on-ticket-page.png 1593w" sizes="(max-width: 800px) 100vw, 800px" />								</a>
											<figcaption class="widget-image-caption wp-caption-text"></figcaption>
										</figure>
									</div>
				</div>
				<div class="elementor-element elementor-element-5238fb8 elementor-widget elementor-widget-text-editor" data-id="5238fb8" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<h5 class="wp-block-heading">Trigger Workflow Permission</h5>
<p><!-- /wp:heading --><!-- wp:paragraph --></p>
<p>You can grant or restrict the permission to trigger the workflow from <strong>Support → Support Agents →</strong> <strong>Agent Role</strong> <strong>→ Edit →</strong> <strong>Trigger Workflow</strong></p>								</div>
				</div>
					</div>
				</div>
				</div>
		]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Manual Workflow</title>
		<link>https://supportcandy.net/docs/manual-workflow/</link>
		
		<dc:creator><![CDATA[Milind Ighe]]></dc:creator>
		<pubDate>Mon, 10 Jul 2023 11:43:49 +0000</pubDate>
				<guid isPermaLink="false">https://supportcandy.net/?post_type=docs&#038;p=328285</guid>

					<description><![CDATA[The Manual Workflow feature in SupportCandy allows agents to execute predefined workflows manually. This feature provides flexibility to evaluate ticket conditions and perform specific actions, ensuring efficient ticket management. How Manual Workflow Works DefinitionA manual workflow is a set of rules (conditions) and actions defined by the user. Users can manually trigger workflows using the [&#8230;]]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="328285" class="elementor elementor-328285" data-elementor-post-type="docs">
				<div class="elementor-element elementor-element-2a5c95ba e-flex e-con-boxed e-con e-parent" data-id="2a5c95ba" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-2e0d2dce elementor-widget elementor-widget-text-editor" data-id="2e0d2dce" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p>The <strong>Manual Workflow</strong> feature in SupportCandy allows agents to execute predefined workflows manually. This feature provides flexibility to evaluate ticket conditions and perform specific actions, ensuring efficient ticket management.</p>
<h3>How Manual Workflow Works</h3>
<ol>
<li>
<p><strong>Definition</strong><br />A manual workflow is a set of rules (conditions) and actions defined by the user.</p>
<ul>
<li>Users can manually trigger workflows using the <strong>Workflow Widget</strong> on the individual ticket page.</li>
<li>When triggered, the workflow evaluates the ticket based on the defined conditions.</li>
<li>If the conditions are satisfied, the specified actions are executed.</li>
</ul>
</li>
<li>
<p><strong>Triggering a Workflow</strong></p>
<ul>
<li>Manual workflows are triggered directly by the user through the Workflow Widget.</li>
<li>The widget lists all available workflows for the ticket.</li>
<li>Users can select and trigger the workflow.</li>
<li>The system checks the conditions, and if they match, the actions are performed.</li>
</ul>
</li>
</ol>
<h3>Key Components of Manual Workflow</h3>
<h4>1. <strong>Conditions</strong></h4>
<p>Conditions are the criteria that the ticket must meet for the workflow to proceed. You can set conditions using various ticket properties and custom fields. Examples include:</p>
<ul>
<li><strong>Ticket Fields</strong>: Status, category, priority, subject, etc.</li>
<li><strong>Custom Fields</strong>: AgentOnly fields, customer fields, or other ticket-specific custom fields.</li>
<li><strong>Operators</strong>:
<ul>
<li><strong>Equal to</strong>: Matches the exact value.</li>
<li><strong>Matches</strong>: Partial match.</li>
<li><strong>Has word</strong>: Checks for specific words in text fields.</li>
</ul>
</li>
</ul>
<h4>2. <strong>Actions</strong></h4>
<p>Actions are the tasks performed when the workflow is executed, and the conditions are met. You can set multiple actions in a single workflow. Available actions include:</p>
<ul>
<li><strong>Add Reply</strong>: Adds a public reply to the ticket.</li>
<li><strong>Add Private Note</strong>: Adds an internal note visible only to agents.</li>
<li><strong>Change Subject</strong>: Updates the ticket subject.</li>
<li><strong>Change Status</strong>: Changes the ticket status (e.g., Open, In Progress, Closed).</li>
<li><strong>Change Category</strong>: Updates the ticket category (e.g., Sales, Technical Support).</li>
<li><strong>Change Priority</strong>: Modifies the ticket&#8217;s priority (e.g., Low, Medium, High).</li>
<li><strong>Change Assignee</strong>: Reassigns the ticket to a specific agent or team.</li>
<li><strong>Change Additional Recipient</strong>: Updates the list of additional recipients for the ticket.</li>
<li><strong>Change Ticket Fields</strong>: Modifies specific ticket fields.</li>
<li><strong>Change AgentOnly Fields</strong>: Adjusts fields visible only to agents.</li>
<li><strong>Change Customer Fields</strong>: Updates fields related to the customer.</li>
</ul>
<h3>Example of Manual Workflow</h3>
<p><strong>Scenario</strong>: A ticket needs to be escalated to a senior support team when marked &#8220;High Priority.&#8221;</p>
<ul>
<li><strong>Condition</strong>: Priority is equal to &#8220;High.&#8221;</li>
<li><strong>Actions</strong>:
<ol>
<li>Assign the ticket to the &#8220;Senior Support Team.&#8221;</li>
<li>Change the ticket status to &#8220;In Progress.&#8221;</li>
<li>Add a private note for internal communication.</li>
</ol>
</li>
</ul>
<h3>Steps to Configure Manual Workflow</h3>
<ol>
<li>Go to <strong>Support &gt; Workflows &gt; Add Workflow.</strong></li>
<li>Enter the workflow name and description.</li>
<li>Set conditions based on ticket properties or custom fields.</li>
<li>Define the actions to perform if conditions are met.</li>
<li>Save the workflow.</li>
<li>Users with permission can now see the workflow in the <strong>Workflow Widget</strong> on the ticket page.</li>
</ol>
<h3>Summary</h3>
<p>Manual workflows in SupportCandy are user-triggered processes designed to automate repetitive tasks and ensure tickets are managed efficiently.</p>
<ul>
<li><strong>Workflow Widget</strong>: Allows users to manually trigger workflows directly from the ticket page.</li>
<li><strong>Conditions</strong>: Define rules to evaluate tickets based on fields or properties.</li>
<li><strong>Actions</strong>: Perform tasks such as updating fields, adding replies, or reassigning tickets.</li>
</ul>
<p>By using manual workflows, agents can streamline their ticket handling and ensure consistent, accurate, and timely responses.</p>								</div>
				</div>
					</div>
				</div>
				</div>
		]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Automatic Workflow</title>
		<link>https://supportcandy.net/docs/automatic-workflow/</link>
		
		<dc:creator><![CDATA[Milind Ighe]]></dc:creator>
		<pubDate>Mon, 10 Jul 2023 11:43:08 +0000</pubDate>
				<guid isPermaLink="false">https://supportcandy.net/?post_type=docs&#038;p=328282</guid>

					<description><![CDATA[Support&#160;→&#160;Settings&#160;→&#160;Workflow The Automatic Workflow feature in SupportCandy allows you to automate repetitive tasks and ensure consistent ticket management. By setting triggers, conditions, and actions, workflows automatically execute predefined tasks whenever a specific event occurs in the ticketing system. How Automatic Workflow Works TriggerThe workflow begins with a trigger, which is an event in the ticket [&#8230;]]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="328282" class="elementor elementor-328282" data-elementor-post-type="docs">
				<div class="elementor-element elementor-element-49078b8c e-flex e-con-boxed e-con e-parent" data-id="49078b8c" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-a95c258 elementor-widget elementor-widget-text-editor" data-id="a95c258" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p><strong>Support</strong>&nbsp;<strong>→</strong>&nbsp;<strong>Settings</strong>&nbsp;<strong>→</strong>&nbsp;<strong>Workflow</strong></p>
<p>The <strong>Automatic Workflow</strong> feature in SupportCandy allows you to automate repetitive tasks and ensure consistent ticket management. By setting triggers, conditions, and actions, workflows automatically execute predefined tasks whenever a specific event occurs in the ticketing system.</p>
<h6>How Automatic Workflow Works</h6>
<ol>
<li>
<p><strong>Trigger</strong><br>The workflow begins with a trigger, which is an event in the ticket lifecycle.</p>
<ul>
<li>When the trigger occurs, the workflow evaluates the ticket based on the defined conditions.</li>
<li>If the conditions are met, the specified actions are executed automatically.</li>
</ul>
</li>
<li>
<p><strong>Conditions</strong><br>Conditions define the rules or criteria that the ticket must satisfy for the workflow to proceed.</p>
</li>
<li>
<p><strong>Actions</strong><br>Actions are the tasks that are performed if the conditions are satisfied.</p>
</li>
</ol>
<h6>Triggers</h6>
<p>A trigger is the event that initiates the workflow. You must select a trigger for your workflow. Available triggers include:</p>
<ul>
<li><strong>Create New Ticket</strong>: Triggered when a new ticket is created.</li>
<li><strong>Ticket Reply</strong>: Triggered when a reply is added to a ticket.</li>
<li><strong>Submit Private Note</strong>: Triggered when a private note is added.</li>
<li><strong>Change Ticket Subject</strong>: Triggered when the ticket subject is updated.</li>
<li><strong>Change Ticket Category</strong>: Triggered when the category of a ticket changes.</li>
<li><strong>Change Ticket Priority</strong>: Triggered when the ticket priority is modified.</li>
<li><strong>Change Ticket Status</strong>: Triggered when the ticket status is updated.</li>
<li><strong>Change Assignee</strong>: Triggered when the ticket is reassigned or unassigned.</li>
<li><strong>Change Ticket Fields</strong>: Triggered when any ticket field is updated.</li>
<li><strong>Change AgentOnly Fields</strong>: Triggered when an AgentOnly field is modified.</li>
<li><strong>Feedback Added</strong>: Triggered when feedback is provided for a ticket.</li>
</ul>
<h6>&nbsp;</h6>
<h6>Conditions</h6>
<p>Conditions are the rules used to evaluate tickets.</p>
<ul>
<li>You can define conditions based on:
<ul>
<li>Ticket fields: Status, category, subject, priority, etc.</li>
<li>Custom fields: AgentOnly fields, customer fields, or other ticket-specific custom fields.</li>
</ul>
</li>
<li><strong>Operators</strong> available:
<ul>
<li><strong>Equal to</strong>: Matches an exact value.</li>
<li><strong>Matches</strong>: Looks for a one or more values in the given values.</li>
<li><strong>Has word</strong>: Checks for specific words in a field.
</li>
</ul>
</li>
</ul>
<p><b>Example:</b></p>
<ul>
<li><strong>Condition</strong>: If the ticket status is “Open” and priority is “High.”</li>
<li><strong>Outcome</strong>: The workflow proceeds only if both conditions are met.</li>
</ul>
<h6><br></h6>
<h6>Actions</h6>
<p>Actions are the tasks executed when the conditions are satisfied. You can define multiple actions for a single workflow.</p>
<p>Available actions include:</p>
<ul>
<li><strong>Add Reply</strong>: Automatically adds a reply to the ticket.</li>
<li><strong>Add Private Note</strong>: Adds an internal note for agents.</li>
<li><strong>Change Subject</strong>: Updates the ticket subject.</li>
<li><strong>Change Status</strong>: Changes the ticket status (e.g., to &#8220;In Progress&#8221; or &#8220;Closed&#8221;).</li>
<li><strong>Change Category</strong>: Modifies the ticket category.</li>
<li><strong>Change Priority</strong>: Updates the ticket&#8217;s priority (e.g., Low, Medium, High).</li>
<li><strong>Change Assignee</strong>: Change the assigned agents, add new assignee or&nbsp; remove all assignee.</li>
<li><strong>Change Additional Recipient</strong>: Replace the additional recepients or remove all.</li>
<li><strong>Change Ticket Fields</strong>: Updates specific ticket fields.</li>
<li><strong>Change AgentOnly Fields</strong>: Modifies fields visible only to agents.</li>
<li><strong>Change Customer Fields</strong>: Updates customer fields.</li>
</ul>
<div><br></div>
<h6>Examples of Automatic Workflows</h6>
<p><b>Example 1: Auto-Assign High Priority Tickets</b></p>
<ul>
<li><strong>Trigger</strong>: Create New Ticket.</li>
<li><strong>Condition</strong>: Priority is “High.”</li>
<li><strong>Actions</strong>:
</li>
<ol>
<li>Assign the ticket to the “Senior Support Team.”</li>
<li>Change the ticket status to “In Progress.”</li>
<li>Add a private note: “This ticket requires immediate attention.”</li>
</ol>
</ul>
<div><br></div>
<p><b>Example 2: Auto-Close Resolved Tickets</b></p>
<ul>
<li><strong>Trigger</strong>: Out of SLA</li>
<li><strong>Condition</strong>: Status is “Resolved”&nbsp;</li>
<li><strong>Actions</strong>:
<ol>
<li>Add a reply: “This ticket has been closed due to inactivity. Please contact us if the issue persists.”</li>
<li>Change status to “Closed.”</li>
</ol>
</li>
</ul>
<h6><br></h6>
<h6>Steps to Configure Automatic Workflow</h6>
<ol>
<li>Navigate to <strong>Support → Settings → Workflow → Automatic</strong></li>
<li>Enter the workflow name and description.</li>
<li>Select a <strong>Trigger</strong> to define when the workflow starts.</li>
<li>Add <strong>Conditions</strong> to evaluate tickets based on your rules.</li>
<li>Define the <strong>Actions</strong> to perform if the conditions are met.</li>
<li>Save the workflow.</li>
</ol>
<h6><br></h6>
<h6>Summary</h6>
<p>The Automatic Workflow feature in SupportCandy simplifies ticket management by automating repetitive tasks.</p>
<ul>
<li><strong>Triggers</strong> initiate the workflow based on ticket events.</li>
<li><strong>Conditions</strong> evaluate whether the ticket meets the workflow rules.</li>
<li><strong>Actions</strong> perform tasks like updating ticket properties, adding replies, or reassigning tickets.</li>
</ul>
<p>By leveraging automatic workflows, you can ensure tickets are handled efficiently and consistently, reducing manual effort and improving customer support.</p>
<p><!-- /wp:list --></p>								</div>
				</div>
					</div>
				</div>
				</div>
		]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
