Skip to content

Settings and activity

5 results found

  1. 10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Timothy Hall supported this idea  · 
    An error occurred while saving the comment
    Timothy Hall commented  · 

    If no one has signed the document, simply putting the document back into draft and resending works just fine. However, if a subsequent signer has deleted the email it would be nice to send to them directly.

    Another work-around is to post a public comment, which if was available from the API could server as a proxy to the resend. A quick API call to post a public comment would allow for a simple "Please Review" message that would go out to all parties.

  2. 13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hi,

    Thank you so much for reaching out – this is a great suggestion and we have had other customers asking about this feature as well. While we’re looking into the possibility of developing it, it isn’t on our product roadmap for the next few months. Please feel free to upvote or leave your comment to let us know how and why this functionality is important for you. Thank you!

    An error occurred while saving the comment
    Timothy Hall commented  · 

    Very important feature for the embedded use case. There is no way to understand the current status of the document outside of an arbitrary state which gives no insight into the recipient actions or attempts.

    Timothy Hall supported this idea  · 
  3. 10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Timothy Hall supported this idea  · 
  4. 20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Timothy Hall commented  · 

    This is crucial for client engagement and for the embedded api case is completely missing. The decline reason could be provided in a webhook, the document details endpoint or even a new endpoint entirely.

    Timothy Hall supported this idea  · 
  5. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Timothy Hall commented  · 

    For the embedded use case, since the user cannot be created with an email outside of the organization's domain, there is no way to have the reply be to the user that created and sent the document. This means that all replies from a client perspective are completely lost, breaking the chain of communication.

    Timothy Hall supported this idea  ·