Skip to main content
Question

Highlights from our "Box Sign Early Adopters" Roundtable last week

  • May 22, 2025
  • 11 replies
  • 47 views
C
Forum|alt.badge.img

I've attached the highlights from the roadmap update and customer discussion below, please reach out if you want access to the recording. 

Fun Facts from Shawn:

12 of 18 attendee companies enabled Box sign across a total of 11k employees

Q2 Roadmap Summary:

Batch send - send a document for signature to multiple recipients at once - just released

Document Preparation Enhancements - Improve ease of use and customizability - GA Q2

Revise Signature Request - improve ease of use with ability to edit recipient information for signature requests in flight - target release this week

Ready sign links - reusable links for self serve e-signatures to share via email or publish on a web site - coming in August

Sign Extensibility - API Support and Additional flexibility to support a wide range of business processes - GA Q3

Enable Sign via User Groups - enables faster deployment and makes managing/administering Box sign easier - GA Q2

Sender Side Advancements - Richer functionality in sender side experience to secure and streamline signature requests - GA Q2

Enhanced Signer Experience and Options - Customizability for enterprises and document recipients to address business process needs - GA Q3

E-sign security and compliance - address a wider array of e-sign use cases - GA

  • 21 CFR Part 11 Compliance - Q4+

 

Customer Discussion Highlights:

  1. Interest in multiple documents

  2. Template tags available via API

  3. Box sign for internal docs

  4. Tab order for signing

  5. CFP Part 11 requirements discussion

  6. Blockers to switching on Box Sign

  7. Customer fields and custom groups

  8. Legal validity of e-signatures

  9. Meta data retention on original file

Please reach out to us directly with any questions.

    11 replies

    C
    Forum|alt.badge.img

    Hi Thomas. I thought I understood "Batch send" to mean it would allow the user to send supporting documents along with a sign request. Am I understanding that wrong? This would be a request I would like to forward to the team.

     

    For example, we would send a sales contract for signature alongside our order/complaint policies as separate PDFs.

    C
    Forum|alt.badge.img

    476309878 Taylor that is our multi-documents feature coming in Q3. Batch send is comparable to DocuSign's Bulk Send where a sender can send the same request as individual request to multiple recipients using a CSV file.


    https://support.box.com/hc/en-us/articles/5534701787283-Batch-send-capability-in-Box-Sign-for-sending-signature-request-in-bulk#:~:text=We%20have%20released%20the%20'batch,everyone%20listed%20in%20the%20spreadsheet.

    C
    Forum|alt.badge.img

    I give classroom style training to my users and have had a question come up repeatedly... When using a text field can I assign more than one signer to that field? As an example if I have a comments field I may want more than one person to enter a comment. I know the answer is no right now, but is it planned for a future release?

    C
    Forum|alt.badge.img

    392778289354 can you describe when a user would need to fill in the same field as someone else for an e-sign case? Also how would you expect this to work? Would the second person be able to edit the first person's text? This seems like it could cause more issues for a legally binding document. For example I sign and put "agree to terms but you must pay $1000 additional" and the second person just removes it.

    C
    Forum|alt.badge.img

    We wanted to move to Box Sign from DocuSign, however, we find that some of the companies we deal with block box.com which means that they would not be able to sign documents. The solution for this would be for Box to use a different domain for receiving signing requests.

    C
    Forum|alt.badge.img

    24568101507 yes this is something we are researching but no timelines.

    C
    Forum|alt.badge.img

    I found a bug: the email that goes out to request an Approval on a document reads "::user:: has requested your signature on a document." Can we change that to read "::user:: has requested your approval on a document"?

    C
    Forum|alt.badge.img

    Thanks 363484193367 ! cc 1911681342885 

    C
    Forum|alt.badge.img

    363484193367 that is the default email you can customize based on your individual needs.
    BOX1_Lj9ZFqlTcorDcaS7A5PB_Q.pngBOX1_ePvam_Te7Dn8tr0viy-gtQ.png

    C
    Forum|alt.badge.img

    Hi Thomas, we've recently started using the revise request feature. Great improvement. However, changing the signing order as stated on this link (https://support.box.com/hc/en-us/articles/7754052860307-Changing-a-sent-signature-request) is not possible. Could the statement possibly be corrected? This is the statement:

    If a specific recipient has not signed, you can:

    • Change this recipient's email address, name, signing order, role, and authentication method.
    C
    Forum|alt.badge.img

    thanks reviewing cc 365963157627

    Terms of ServiceAccessibility statement