Wednesday, December 16, 2009

Flowlett Product Features

For those who asked for this, the slides that describe Flowlett's features at a high level are below.

Flowlett Use Cases in Sales

Based on user request, we've compiled some sample use cases below. Enjoy.

Tuesday, December 1, 2009

New Features: Embeddable Form, Collaboration Workflow


Hope you all had a great Thanksgiving holiday!

We're thrilled to announce the general availability of two new (and powerful) features.

Embeddable form:
While creating a form, you can now specify whether it can be embedded. If this option is selected, the form can be embedded on ANY web site or application.


This opens up a number of possibilities. For example, you can build a Contact Us form. Or you can build a form to accept an application (like we did) or accept proposals etc.

You can specify what message should be shown on the web page when the form is submitted and who the contents of the form should be mailed to, when submitted.

But the killer feature really is - you can specify who the completed form should be routed to, in what order and what the recipients should do (review? approve?) to that completed form.

To embed the form into a website or web application, simply copy the iframe code of the form.


Regardless of how the web page or application is set up, the Flowlett form data is transmitted securely via https/SSL.


Collaboration Workflow:
Our second powerful feature is the Collaboration Workflow.


The Collaboration Workflow allows you to collaborate on proposals or projects before you're ready to route them for formal approvals.

This may look similar to many other collaboration tools out there, but the killer feature here is you can collaborate with deadlines (and thereby get to decisions faster).

For those used to our regular workflow, the Collaboration Workflow is different in that:
1. Recipients cannot approve or e-sign.
2. Recipients can comment and upload files (creatives, documents, videos etc.)
3. The Collaboration Workflow doesn't automatically end. The initiator or the Account Admin needs to Archive the workflow to end it.

Try both of these out... and as always, keep sending us feedback. We still read ALL emails :)