FiliQ: Hello, I was wondering on ETA's of: 1.
- Compliant eSignatures (legally binding)
2.- Custom SMTP
3.- Word Document Support
Nowadays I am using Document Studio Chrome Add-On & Signaturely and I would like to simplify my process to:
1.- Get inputs via Questionscout forms
2.- Generate the PDF to be signed by the client with a Word document (legal agreement)
3.- Send the final document (PDF) to be signed by the client (legally binding eSignature)
I do like the way Signaturely handles the signing process, but if I can achieve everything with less steps (SaaS) I will be glad to do it that way.
Hello Fili, thank you for your question.
In our most recent release, we introduced signatures and audit trails that comply with ESIGN and eIDAS regulations. We are also planning on releasing SMTP this month and word document support this quarter. With these releases, your workflow should be achievable with just Docdown :)
Let me know if you have more questions!
Verified purchaser
Thanks for the reply Paras. I must assume that the {{fields}} will be written down over the Word Document and the eSignature "text box" can be selected (in terms of position) over the same Word Document. Then converted into PDF, right?
Then, that PDF will be able to be sent automatically (with an email address gather from the form) with just the eSignature "text box" to be filled by the user.
Am I right?
Hi Fili,
Yes, that's exactly how it will work with word documents. You can also already implement that workflow in Docdown, but with PDF document upload instead.
Let me know if you have more questions :)
Verified purchaser
Got it,
Can't wait for the word document support to be ready. One last question before I made the purchase:
I must assume that the SMTP functionality you are going to release will have some kind of white labeling in order to respect / present the brand of our companies as senders (not only over the email address, but in terms of logos, predefined colors, buttons, etc... right?
All the best