HelloSign API - great if you must have e-sign integrated into your App.
June 05, 2018

HelloSign API - great if you must have e-sign integrated into your App.

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with HelloSign

We used the HelloSign API product to have new users sign a User Agreement as part of the user onboarding. Users would sign up for an account, be prompted to confirm their email address, and then would sign an end user agreement via HelloSign's API, helping to streamline that process. Ultimately, legal felt that an explicitly signed agreement was no longer required, so we changed the onboarding to a 'check box' agreement of the terms of the user agreement and removed the HelloSign step form the onboarding process given that it added a step and was driving drop off in the adoption of the product.
  • Integrating the API was pretty easy and straightforward all in all.
  • The flexibility in incorporating HelloSign into the onboarding was great.
  • From a design aesthetic, it looked pretty good.
  • The ability to access all of the signed agreements through their web dashboard at any time was helpful.
  • After the initial sale, we never heard back from our sales rep. Even after canceling our subscription, we didn't hear back.
  • I thought the API pricing was a bit high.
  • During the initial setup, they had to manually review the implementation to ensure that it was compliant. Scheduling that was a bit of a hassle, would have preferred to point them to a demo and let them do it on their own time.
  • If you need users to sign documents from within your app, and want control over the user experience (or just don't want to redirect them off your app) it is a great solution and surely beats having to ask customers to sign and email or sign and fax documents back in. It is even better than having them e-sign after emailing them, and saves resources/time with sales and account management.
  • The downside is that it is an extra step in the onboarding that drives drop off, so if it can be avoided, it will help drive greater usage/adoption, etc.
We chose to use HelloSign due to ease and flexibility of their API as compared to competitive solutions in the market. Cost was a secondary factor, but our primary driver was the control that we had in integrating the e-sign step in our onboarding.
In terms of an API-based e-signature provider, my gut is that they are still the best option out there, but it still provides an extra step in onboarding and is better to remove from the user experience, if possible. Implementation was quite easy, and flexibility to use different templates in different scenarios is valuable, if required.