Could we also be added to the beta testing, please?

I'm all for this if it's KBA compliant without the Adobe add-on!

The new signature feature was working great until you took the 1 tab to look at all signature request on one screen for signatures, signed, pending, sent. We would like to have the one screen back in place instead of having to go through each project to see what signatures we are waiting for.

Can you build a paywall behind the e-signatures so that it can't be submitted until full payment is received?

If a signature is attached to a task in a project, can it stay there instead of the E-signature screen in the client's view? I would prefer to send them a list of task that include signature requests, but having to navigate to a different screen to sign is confusing to some clients and causes additional clicking around.

Any update when this will get sorted? The worst part is the timing out... is that still going to be an issue? Any update would be appreciated! :)

I love the new e-signature feature. One enhancement that would greatly improve the user experience would be the ability to move completed or voided signature requests into folders once they have been finalized.

Providing users with the option to organize completed documents into custom folders would help keep the main dashboard and desktop view focused on active, outstanding signature requests. This would reduce clutter, improve efficiency, and make it easier to manage and locate historical documents when needed.

Amanda,

Add Outscore to the beta list. We're a CPA firm running IRS monitoring and representation, so signature volume is 8821/2848/8879 plus engagement letters, and today that means paying for a second tool outside FC. Native e-sign closes that gap. What would make it work for us on day one:

Templates with fields pre-placed for 8821, 2848, 8879 and engagement letters, with client name, address and EIN/SSN pulled from the client profile.

KBA on 8879 (glad to hear that's in).

Multi-signer support (taxpayer + spouse) with signing order. Signed copy lands on the client task and in Client Files, and the task auto-completes when the last signer finishes. Signature requests available inside project templates so recurring work (annual 8821 renewals) sends automatically.

An API endpoint to create a request from a template, so we can trigger it from our own tooling.

Happy to test with real workflows and give structured feedback. Let me know.

Orlando Saez

CEO - Outscore