How to use the Support site

<< Click to Display Table of Contents >>

Navigation:  Bizagi Modeler > Modeler Services plans > Customer support >

How to use the Support site


Bizagi offers a Support Site to assists the customer´s incidents. Below you will find a guide of how to perform basic tasks like creating new question/incident tickets, as well as the way their follow-up must be done.



Please note that the website is dynamic, and therefore, it is possible that some of the screenshots offered in this document present some changes, all the while maintaining the philosophy and main characteristics of the ticket creation process and interaction with it.


Site Access

Incident report

Incident update

Ticket's FAQ


Bizagi Support Site Access Instructions

The interaction is very simple and self-explanatory. However, here are the site’s most important features.

We recommend that before posting a ticket always use the search option to find information: The search looks for your question or problem in this User Guide, the free Forums and our Knowledge base.

This is the fastest way to provide solutions to your problems and your frequent consultations. There is a dedicated team that is constantly improving documentation with frequent reports and concerns received through the support channels.


Site Access

To enter the Support Site access the Bizagi´s official site at You will find a screen similar to the following:




On the upper frame you will find the Login option, which will allow you to identify yourself as a customer and access our services.


When you access this option, you will find a page similar to the one on the image below, where you will be prompted for your email and password. If you don’t have a registered account yet, you can join to our Bizagi community and get another benefits such as Bizagi Cloud.




If you have forgotten your password, you can use the remind password option, as explained in How can I retrieve my username or password in case I forget them?


Once you have logged in, you will be redirected to the Customer Portal, where you can access the Support site.


Support Site Tools

To report incidents, once you have accessed the Customer portal, you have to access the Support page using any of the following options:


Clicking on the Support menu on top of the window

Clicking on the link Support


You will then find the Support site’s main page, where you will find the different options that we offer to our clients.




Incident Report

The main assistance channel for incidents and questions is our Support site, which you can access through the option Support Tickets.


We recommend that before posting a ticket always use the search option to find information: The search looks for your question or problem in this User Guide, the free Forums and our Knowledge base.

This is the fastest way to provide solutions to your problems and your frequent consultations. There is a dedicated team that is constantly improving documentation with frequent reports and concerns received through the support channels.


There you will find the following options:




It is very important that you report any question or incident through tickets in order to facilitate follow-up and thus receive a better service.


To report a new incident or question, click the New Ticket button. The following information will be requested:


Subject: A brief description of the incident to be used as a quick and summarized reference of the report.


Severity (formerly know as Category): Select one from the following severity levels. The Support team can change it, agreeing with the customer, if the Severity level was not chosen correctly:


oProduction system down
The incident causes complete loss of service in Production. The affected operation is mission critical and fully impacts the business, and the situation is considered an emergency. No workaround available.


oProduction system badly compromised
The incident caused a severe loss of service. No acceptable alternative or "workaround" is available; however, the operation may continue in a restricted mode.
Such problems include situations where you need to restart processes and performance issues are often present (Example: Slow operation  causing a degradation of service but does not make the product unusable.)


oProblem blocks deploy to production or staging
One of the following situations occur:
- The problem is blocking the development or test environment, preventing the project to continue. None of the consultants of the project can move forward.
- The issue affects the deployment of processes to Production or Pre-Production environments.


oProblem delays project delivery if not solved before ---
The problem delays the execution of the project if not resolved before a certain date.


oNon critical production
The incident causes a minor impact on the business and may require alternative or "workaround" to restore functionality, however the product can be used.


oQuestion about Bizagi
Specific questions on product features


Module: Component subject to the report or question.


Product. Select the Bizagi product the report or question is about.


Exact Version. Indicate the exact version that you are using. For example, if you selected the Bizagi product 9.1.x Enterprise .NET, the exact version could be: 9.1.9.


Processor architecture: Indicate if your system architecture is 32 or 64 bits architecture.


Project: Indicate your Project's name


Database. Database motor used. The different Oracle and SQL Server versions supported by Bizagi are among the options.


Send Copy to. When the ticket is created, updated, or closed, notifications are sent. If you wish to have copies of the notifications sent to additional mailboxes, you can do so using this option.


Ticket description. Complete description of the question or problem reported. In order for assistance to be faster and more efficient, we suggest that the description is as explanatory as possible. To this end, we recommend that it contains the following information:


Problem details. Indicate what is the unwanted situation, when it began to occur, and provide antecedents of the problem (if any). If possible, include images and error messages.


Steps to reproduce it. Steps that must be followed to reproduce the problem. If you consider that the process or the steps are complex to understand or explain, you can rely on a document with images.


Priority explanation. In case you are reporting high-priority incidents, please indicate the reasons why the reported problem blocks the operation of the solution. Also, in Tests and Development, indicate why it is a topic that is relevant to the project’s success.


Inputs. The inputs most frequently requested by the Support Team are:


oEvent Log. When the reported ticket corresponds to an error appearing on screen, whether it contains the generic production environments message inviting to contact the administrator or the complete message in development, error message details are stored in the event log, which is why it is important for you to attach the event log from the web server when this kind of error occurs. We recommend that you have it in .evtx format.


oDatabase Backup. In order to simplify a ticket’s solution cycle, and when conditions permit it, the database becomes an important input. This is because on the one hand, it enables reproducing the exact conditions of a problem, and on the other, it facilitates the analysis and incident reproduction tasks, since it will be easier for the project to explain the event details and it will facilitate the reproduction of the incident.


You can attach a file in the Ticket description. If you need to attach more than one you can combine them into a single .zip or .rar file.

Once you have completed the incident log, you must click the Send button, which is located at the bottom of the screen. You will immediately receive a message from confirming that the incident has been received.


Phone number: Sometimes it is necessary to perform online sessions to resolve problems. Phone number is very important.




Updates on open incidents must be done exclusively through the site, as this is the regular channel for interaction with the support team.



To avoid inconveniences with the reception of notifications, add the address to your safe address list. This way, you will avoid getting notifications sent by Bizagi Support in your spam folder and not receiving ticket updates.


The mailbox is not monitored, so responses or messages sent to this address will not be answered.


If you experience any inconvenience with logging or interaction with the support site, you can contact the Account Manager assigned to your company or send an e-mail to


It is very important to keep in mind that the support service offered pertains the product and not any implementations done during its use, which is why the incident log must be done in terms of product and not of implementation or business.


Incident Updating

The updating of open incidents must be done exclusively through the site.

Once you have accessed the Support Tickets page, you will find the option to check existing tickets besides the one for opening new tickets.




Filters and Search

There are three filter options in this page:

Status Filter. It allows filtering cases according to their status. These are the options:


oAll Tickets

oOpen and recently closed




To use the filter, you must select one of the options and click the Check button.

Date Filter. When you select this checkbox, the start and end dates are displayed. Once the range is defined, the data will be filtered after pressing the button.


Keyword Filter. With this option you can filter tickets containing words and letters that are useful to find a ticket quickly.


Ticket Updating

Once you have found the ticket you want to update, you must access it by clicking on the subject:




New comments can be sent at any moment during a ticket’s life cycle. These will be received by our support team (except when it has already been closed). You can always attach new files to comments.




Every time our support team generates a new comment for a ticket, a notification will be sent to the registered e-mail address and to the address stipulated in the Send copy to field.




Tickets Frequently Asked Questions

How can I check the support duration of a product version?

As Bizagi evolves and new product versions are released, old ones lose their validity. For this reason, we define a date when said versions lose support. This information is updated in our support site for organizations to plan accordingly. To check this information, you can access through the link highlighted on the image below once you access the ticket enquiry and establishment screen:




How can I change my password?

If you need to change your site access password or modify any other account information, you can use the option Edit my account that appears on top of the site after you have logged in, as you can see in the image below:




Once the option is selected, a screen similar to the one below appears.




Click Edit profile and then, click Change Password button.

Enter the current password and then, fill-in the new password and click Change password.




How can I retrieve my password in case I forget it?

If by any chance you have forgotten your password to access Bizagi Site, you may use the option available on our Sign In screen:




If you select the Forgot your password? option, you will be prompted for the e-mail address associated to your account.




If your email address matches with the one registered, we will send the verification link.




Verify your account using the link sent and then, fill-in the new password and click Change password.




Are any additional tools used aside from the page?

The exclusive channel for ticket interaction is the Support site. However, in order to facilitate assistance for open tickets, we use additional tools such as:


Skype. For communications we use this tool, namely through the Skype account Bizagi support.


GotoMeeting. This is a remote access and conference tool that enables access to our clients’ environments through a browser, as well as allowing them access to our environments to work as a team in the assessment and solution of an incident.


ShareFile. File sharing is usually done through a secure site: Every time you need to send a file to Bizagi Support, the corresponding link will be provided through a post on the ticket.