Automation Hero vs. VisualCron

I recommend Automation Hero when you receive a lot of communications (email or fax) with a lot of attachments like documents or picture, for which there is a human operator that has to collect all the information from them and this information are basically always the same (same information, same fields, some pictures...). Automation Hero needs a little training to perform well, and this can be realized only if there is a large number of inputs. Instead, if your company manages few documents or only documents written by a human, I think Automation Hero isn't a good choice because the performance isn't good enough, and you have to dedicate too much time to the training (the value of Automation Hero is the possibility to arrange your activities quickly so if you need a lot of time, the solution is not so convenient). Also, in the classification field, I recommend Automation Hero if you have a lot of emails to manage and if you need the first classification of them before they are managed by humans (so, emails are always read by humans who provide answers, but the first step of the classification may be managed by the machine). In a few words, I think Automation Hero could work for large companies.

Incentivized

VisualCron does accommodate continuous file processing. Like packing and unpacking compressed files, splitting or merging files, sending E-mail's and executing queries on databases. VisualCron in less suitable for performing very complex operations on files like, arithmetic with numbers, dates or amounts. Very complex job scripts become cluttered. Debugging Job scripts is not easy.

Incentivized

• Reading standard documents.
• Identifies key words inside a text and provides automatic replies.
• Emails classification.

Incentivized

• VisualCron can pack and unpack files from many types of packing methods.
• Clear job scripts with complex constructions can be written in VisualCron
• VisualCron provides a clear graphical overview of the situation of all jobs.
• VisualCron clearly indicates when a job has run into an error.

Incentivized

• The user interface could be more detailed (Robin).
• Also documents in txt or html format could be read.
• The help section for clients could be integrated into the platform without switching from one to another.

Incentivized

• VisualCron should more specifically indicate the root cause of an error.
• If copying a file goes wrong, VisualCron reports 'can't copy file'. I expect 'no read permissions from original' or 'no write permissions from destination'.
• VisualCron offers no way to execute a Job script line by line
• In VisualCron, nested loops cannot be created.

Incentivized

Questions and problems can be addressed to VisualCron 's support department via E-mail. I usually get a good answer from them fairly quickly. There is also a VisualCron forum where you can ask questions that will be answered by other VisualCron users.

Incentivized

Automation Hero has a great support service for its customers. They are available to work closely with our team, especially for the first steps/first implementations, and they give us a team who is confident with our local native language. When there is something that goes wrong, they have quick answers for us, so we don't have to wait for the problem solutions.

Incentivized

For simple processes, VisualCron is easier to use and maintain. For complicated processes, Quadient Inspire offers more options. The graphical representations of waiting, running or completed jobs is adequate for both products. The logging of job actions is better in Quadient Inpire as in VisualCron.

Incentivized

• Less IT costs because, with Hero Platforms, flows can be implemented without IT technical skills.
• Better customer services for standard questions (speed reply).
• Solutions are scalable so once you have created one you can reuse them in other departments (so the ROI for the implementation of Automation Hero must be considered for a lot of projects).

Incentivized

• With VisualCron, I need 3 times less time to get file processing right.
• If a VisualCron job goes wrong I need twice as much time to find the problem.
• Visualcron does not run on Linux but on Windows which can make an upgrade and reboot take up to 6 times as long.

Incentivized