My previous post entitled Embracing Change attempted to shed some light on the types of responses we receive from our users whenever we release new features within the application. I concluded the post by asking our users to grow with us and to give the changes in Merus a chance.

The office here at Merus has undergone changes of its own. Everyone on the Merus team has now been eating our own dog food for about 60 days now. This means we have been consistently using MerusCase to track all of our clients, emails, and support requests. Everything we do, every interaction, and every breath is logged in the "dog food firm".

We've had to internally counsel a few of our team members to embrace the dog food change. On Friday, October 18th, we released version 3.1 of MerusCase. With this release, there were two main changes: the introduction of our new feature - Workflow - and some edits to the Parties interface.

The responses the support team has faced on previous releases has always been hard for me to fully understand. I personally love Merus (who wouldn't love an application that tells you it loves you on a daily basis, right?). I have faith in the product to make my workload lighter and more productive. This has rung true with the office's implementation of the "dog food firm" and especially with the new Workflow feature. By setting up workflows in the "dog food firm" the redundancy of typing "follow up with client" as a task for the support team has been rendered obsolete. The support team has automated almost every possible task and event creation whenever we link a message to a case and has effectively saved me time and energy while giving me the peace of mind knowing I'm not forgetting something or failing to reply to an email. (I'm sure this peace of mind is also translated to my supervisor knowing that myself and the rest of support is completing all of our tasks).

Additionally, Workflow is easy to setup and use. It took only a few minutes to set up multiple workflows in Merus. If you can create an event or a task in Merus, then you can create a workflow. Workflow is setup to trigger whenever a new activity is created with a specified activity tag. For instance, you can create a workflow to be triggered each time you set a statute in a case.Workflow allows you to enter tasks, subtasks, and/or events hours, days, weeks, or months after the case activity for Set Statute in this example is created.

Have any users setup their own workflow? Please let us know how the feature has worked for you or if you have any questions or concerns regarding the new feature. Instructions to setup workflow can be found in our help article entitled How to Add a New Workflow.