As part of building our understanding of which e-signing approaches are used across Karbon customers, we’d love to know more about the tools (such as DocuSign, Adobe Sign, Go Proposal, Ignition, etc) you use to collect signatures and approvals and the workflows in which you use e-signing.
Leave me a message below of send message if you’d like to chat.
Answered the survey. I’m excited to see how you approach e-signing.
e-signatures in Karbon would be a game changer for me. I’ve suffered (and made my clients suffer) Onvio for many years - I can't wait for this to come to Karbon so I can keep all of my client requests and signatures in one place.
We use Docusign. Our clients love it, but it’s hard on the staff.
We use DocuSign for tax work and Go Proposal for pricing out work.
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.
@StuartK any idea of what we might see come out of this? We used Xero doc packs before but their change in pricing is causing me to review our options for document signing.
@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.
@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.
We use RightSignature because it is bundled with ShareFile but would love to be able to switch over both our client portal and e-signature solutions to a Karbon based solution. Would be lovely to have everything work cohesively together within Karbon.
Our team uses Ignition for all client engagements and Docu-sign for e-signatures.
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.
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 :)
I believe the ignition<>karbon integration that creates the work item will also create the client record if there is not an exact name match in karbon = ignition EL client name.
We used to have duplicate client records created in karbon with this integration because of inconsistent use of commas ex. ABC Company LLC vs ABC Company, LLC where the comma after company create a new unique client record in Karbon and mapped the ignition templates to karbon work items.
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 five e-signing scenarios:
I would love to have this built into client requests. 😁
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.)