After playing around with the new “Workflow” feature in a beta environment it’s quite nice. But as it would apply to our business it may fall short. Let me explain.
Our company relies heavily on “Save My Progress and Resume” to do business with customers OUTSIDE our business. We have multiple forms that are designed as field tickets that calculate services rendered, employee time and a whole host of important details. Our employees hop on their iPhone or iPad, fill out a “ticket” and send to the customer via the save my progress option by putting in the customers email address and sends over the completed ticket. It’s then reviewed and signed by the customer or sent back to the employee (via the same method) if there are discrepancies. There are obvious flaws (I will spare you the details) with this process but it has gotten us by for now and hopes that the “Workflow” feature would address these short falls.
Now, I understand that “Workflow” wasn’t necessarily designed to replace “Save My Progress” but I think with a few tweaks it could add greater functionality to processes like ours.
The one thing that could address a ton of issues is to allow Approve or Deny via the EMAIL ITSELF without having to have an account within MachForm. This would allow this feature to be used much more openly and much more efficiently. In our case I wouldn’t want customers with access to our back-end and couldn’t possibly have an account for every person that does business with us. (See some examples below.)
Another way we use MachForm is a Purchase Order system, and “Workflow” makes a ton of sense for this type of application as well. Employees fill out the form and submit it then it goes through a list of management that would in turn approve or deny it. Once again however, this process would be greatly streamlined by allowing the approver to approve or deny simply within the email without being bogged down with web redirects and login processes.
Thanks for hearing me out.
Aaron
