Time and money saving routing software
October 15, 2021

Time and money saving routing software

Alexandra Rood | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Ziflow

We use Ziflow to route projects. It's used across most of the entire organization including account, editorial, digital, copy, art, production, and more. It solves many business problems for us: reducing the number of rounds of routing, ensuring all changes are incorporated correctly, marking up changes, and reviewing files before submission.
  • Tagging comments.
  • Comparing versions.
  • Responding to comments.
  • Ability to adjust default settings.
  • Simpler decision making options.
  • Easier home page navigation.
  • Improved efficiency.
  • Time and money saved.
  • Efficient communication.
It's reduced the effort that we expend to review and approve creative content.
It's improved the content review and approval process. The relevant teams are automatically notified when a project is in their queue and needs to be reviewed. The commenting function is simple, and it's great that the team who's incorporating the change is able to label each comment as "done." I love that we can mark comments as "stet" to make sure it's crystal clear what changes are and aren't being made.

Do you think Ziflow delivers good value for the price?

Not sure

Are you happy with Ziflow's feature set?


Did Ziflow live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Ziflow go as expected?

I wasn't involved with the implementation phase

Would you buy Ziflow again?


They are very similar. Ziflow has additional features that improve the routing experience, like tagging comments, simpler reply chains, user-friendly home page, and more. I love that there's a home page where you can search all the proofs that have been shared with you. I don't have to dig around in my email anymore to find old links.
Ziflow is well suited for documents or projects that need to be looked over by multiple people in multiple departments. It's great for when you have client revisions that need to be made and fact checks/check changes/full reads by editorial. It's great for suggesting specific changes to a product or version. It's less appropriate when team members are discussing high-level changes that require full conversation or a lot of back and forth.