Discover everything our e-commerce platform has to offer - from setting up a store, through marketing and integrations, to security, technical support, and design. Find out how to grow your online sales with Web Systems Pro.
Expand your store’s capabilities with ready-made integrations - online payments, wholesalers, shipping, SEO, marketing, CRM, notifications, and more. All designed to help you operate faster, more effectively, and more conveniently.
Searching for support for your online store? Visit our blog, knowledge base, forum, and expert articles. Here you’ll find instructions, e-commerce tips, and answers to frequently asked questions - everything you need to run a successful online store.
We strive to explain in simple terms how our theme templates work - including descriptions of their features and settings. In addition, we regularly update and expand our instructions to ensure they remain clear and helpful at every stage of using the the
Discover everything our e-commerce platform has to offer - from setting up a store, through marketing and integrations, to security, technical support, and design. Find out how to grow your online sales with Web Systems Pro.
Expand your store’s capabilities with ready-made integrations - online payments, wholesalers, shipping, SEO, marketing, CRM, notifications, and more. All designed to help you operate faster, more effectively, and more conveniently.
Searching for support for your online store? Visit our blog, knowledge base, forum, and expert articles. Here you’ll find instructions, e-commerce tips, and answers to frequently asked questions - everything you need to run a successful online store.
We strive to explain in simple terms how our theme templates work - including descriptions of their features and settings. In addition, we regularly update and expand our instructions to ensure they remain clear and helpful at every stage of using the the
A workflow is a business process in which requests are handled in the "Helpdesk" app. The concept of a workflow is based on three components: sources, states, and actions.
Source is the "place" from which a request originates. The app supports four types of sources:
Backend. The "New request" button allows you to manually add a request on behalf of a customer — for example, if the inquiry is made by phone and the reply needs to be sent to the customer via email.
Email. Regular emails arriving at the company's email address. You just need to configure "Helpdesk" to receive news emails from your mailboxes.
Web form. A common way to receive inquiries from website visitors is through a form with fields for entering name, email address, and the request text. There may be multiple such forms.
Personal account. This is a password-protected section of the website created for each customer after their first request, where the entire correspondence history is available, along with a form to submit new requests.
State is the status of a request at a given point during its processing. Examples of states include "New", "In progress", "Closed", etc. In "Helpdesk", you configure the workflow yourself, which means you can create as many different states as needed.
Action is the process of transitioning from one state to another. Examples of actions: "Reply to customer", "Add comment". In most cases, actions are performed in the backend, but you can allow certain actions to be performed from a personal account-for example: "Cancel" (if the customer finds a solution themselves) or "Reopen" (for requests requiring clarification). There are actions that are executed automatically upon specific events-for instance, changing the state upon receiving an additional news email from the customer.
Example of a simple workflow.
Source "Email" → State "New" → Action "Reply" → State "Closed"
The request was sent by email, meaning the source is an email address where the customer's message arrived. When the request reached "Helpdesk", it was assigned the "New" status. After performing the "Reply" action, the request's status changed to "Closed".
Tips for setting up the workflow.
The workflow must include at least one source. Otherwise, customer requests simply won't reach "Support".
The workflow must include at least one state. Actions on a request can only be performed when it is in some state.
To move a request to another state, you must perform an action available in the current state. If none of the actions point to a certain state in the workflow diagram, no request can ever enter that state.
An action may not change the request's state. For example, the "Add comment" action will leave the request in its current state.
You can create any number of states in the workflow. To get requests into these states, you need to add corresponding actions.
In each state, you can define any number of available actions.
A state may have no available actions ("empty"). This means that once a request enters such a state, it cannot change its status to any other.
The same action can be available in different states. For example, the "Reply" action may be available in both the "New" and "Discussion" states.
Workflow diagram.
This is what the default workflow configuration looks like when the "Helpdesk" app is installed for the first time:
Workflow diagram upon first installation of the "Helpdesk" app