How do you use e-signing/e-signatures?

Agree with @max!

We use Docusign. Our clients love it, but it’s hard on the staff.

We use Ignition for everything related to client agreements, but for all other documents, we use RightSignature.  It’s bundled with our Citrix ShareFile subscription, but the nice part is that you can initiate the e-sign on any document stored in ShareFile, and once it’s signed, it automatically saves back to the same location.

Hi @Jared Cordner - e-signing is definitely one of the most popular requests we have and it’s definitely up there on our list of features to build - but the popularity means that it means slightly different things to different people.
Right now I don’t have a timeframe to share though I’ll certainly update the thread with any details as it becomes clearer.

Hi @Kyle Beltle - it’s something we’re actively looking at at the moment - but a fairly broad and complex topic. Please do send me a note or share any specific needs you have around e-signing.

@StuartK - Our goal is to make tax engagement letters easier for our clients. Right now we send them an email from Karbon & then an email from RightSignature. If we could either put a link in the Karbon task to go to a third party site to sign (currently I don’t believe RightSignature supports this), or use Karbon to facilitate the Esignature, that would be ideal.

We use ignition for engagement letters and cpaperless safesendreturns for tax assembly/efile + their safesendsignature product (included) for odds and ends esign needs.

We do not need esign in karbon.

@Kyle Beltle Yes, you can paste a link to the engagement letter in a client task. We currently manage our engagements outside of Karbon. We send the EL directly from Ignition. We have Karbon and PI connected. We use Zapier to search Karbon for the client once the EL is executed, if it is a new client then Zapier creates the new client in Karbon. 

Our services are a 1-1 with our templates, and they are synced in Ignition. When a client signs the EL that integration between PI and Karbon creates the work items in Karbon based on the services that the client engaged for. We have a user setup in Karbon (work assignee for ignition) for the assignment of all work from PI that we never activated via the email link, so we aren’t paying for this user. But it helps us to separate what work is new from the existing work. The work is created based on the start and end date of the EL. 

I’m happy to answer any other questions you have about the Karbon/PI integration :)

@lbernstein This is the Zap we have “Create Karbon organization contacts for new accepted proposals in Ignition”. We turned this Zap on in early 2022 and since then I believe that the Integration between PI and Karbon has been updated. The zap essentially searches Karbon to see if it is an existing client, and it will update the contact, or add a new contact. I didn’t explain that well above, because you are right. Karbon and PI do sync together. We too found that we have to be very careful in the naming convention in both software's or you will get duplicates.

The other Zap I have is connecting our calendly to PI. “Create client in Ignition when invitee created in Calendly”. When a client schedules a discovery call the Zap creates the client in Ignition. If the client doesn’t move forward it is part of our process to remove them from Ignition, but this helps in reducing errors in naming clients. 

We have been using PandaDoc this year. This allows us to send out documents for e-signing via e-mail when that makes the most sense (i.e., sending out an engagement letter to kick off an annual corporate engagement).

It also allows us to generate a link to the document that we can embed in a client request within Karbon. For example, I have a client request template that has one task for the client to watch the Loom video overview of their financials and taxes, another task to review several attached draft documents, and a third task to click into the Pandadoc link and sign their documents.

I’m not sure it always makes sense for a customer to receive an e-signature request through a karbon client request, so PandaDoc’s platform was an appealing addition to our toolkit. (They also met a number of our other criteria, including the ability to add SMS verification for sensitive documents. It was hard to find an option that had MFA security options AND the option to send an e-signature out via URL rather than e-mail.)

I use Cognito forms for Engagement letter, Questionnaire, ACH debit for monthly clients, new client contact form, transfer form, & authorization to share info. We use Go proposal for new monthly clients, Safesend for 8879 signatures. Cognito uses links so we send the Eng letter & Questionnaire link in a client task along with the doc upload as our organizers (sent Jan 15th). 

@Stephen Roos As far as my (very limited) Karbon knowledge go, there is not way through Karbon to get E-signature on documents directly.

We also use Adobe's solution, as I already have paid Adobe subscription, but I recently started to use the build in E-Sign request out of Dropbox, as I found Adobe's solution to have sometimes don't work as well.

There might be very way with integrations to send client a client request through Karbon with link to doc to sign, but not sure if this is possible or difficult to setup for each instance where e-sign is required.