Send in Bulk with a CSV using the classic process

Note:

The below article describes the functionality for the "classic" process of the Send in Bulk experience.

The modern version is the focus of current development, and customers are generally recommended to use the modern experience when possible to familiarize themselves with that environment.

Send in Bulk by using a .CSV file to import the recipients and their details

You can use a CSV file to import your recipients' email addresses and merge custom data into fields on the document for each recipient. You can also customize the message in the email sent to each signer requesting that they sign the document.

.CSV stands for Comma-Separated Value and Excel files can be saved in this format.

Note:

This video shows how to set up and use a .CSV file in a Send in Bulk transaction. It also shows how to track the status of all documents sent in the Send in Bulk transaction. 


Setting up your .CSV

Before setting up your .CSV, it's necessary to know the names of the fields in your document. There's a different way to do this depending on how you added fields to the document:

  • If the document was created with Tags (Text or PDF), use the field name you defined in the tag. For example, has the field name of Address1.
  • If you used the Drag and Drop Environment, edit your document and double-click the field. The name of that field is at the top of that properties window.

Once you know the names of the fields on your document, open either the sample found on the Send in Bulk send page, or create an Excel file.

Note:
  • There must be a minimum of two unique email addresses in the CSV file.
  • The sender’s email address cannot be in the CSV.
  • The number of transactions that can be generated using the Send in Bulk feature is limited based on the tier of service:
    • Enterprise and business tier customers can generate up to 300 transactions
    • Acrobat Pro with advanced e‑sign for teams and Adobe Acrobat Sign Professional customers can generate up to 50 transactions
    • Acrobat Pro with advanced e‑sign can generate up to 50 transactions
    • Team trials can generate up to five transactions
    • Enterprise trials can generate up to three transactions
  1. The first row is the field names and information tags. For custom fields you've added, add the field names to the column header.

    The information tags are as follows:

    _es_signer_email (Mandatory) The signer’s email address

    _es_signer_name (Optional) Signer name used in the signature

    _es_signer_fullname (Optional) Signer name appearing in the document

    _es_signer_company (Optional) Signer Company

    _es_signer_title (Optional) Signer Title

    _es_agreement_message (Optional) The message included in the email sent to the signer.

    The other names used (Phone and ZIP code) are the custom fields we've added to the document.

    Information tags in CSV

  2. The next row is filled with the information specific to the signers. Here we set the email addresses, full name, company name, title, custom message, and the other information for our custom fields.

    Signer information filled

  3. Finally, save the file as a .CSV(Comma delimited)(*.csv), to your local system.

    • Customers who use double-byte characters must save the CSV file in CSV UTF-8 (Comma delimited)(*.csv) format
    Saving CSV to your local system


Sending using the .CSV

  1. Once you've created your .CSV, click Send in bulk on the Home page.

    Send Mega Sign from Home page

  2. On the Send in Bulk send page, click the Import Recipients and Merge Fields from File link to use your .CSV for sending.

    Import recipients and merge fields from file

  3. Click Upload.

    Upload

  4. Find and attach the CSV file you want to use.

  5. Configure the other options as desired:

    • Identity verification - Set this to apply a second-factor authentication
    • I need to sign - Check this box if you (the sender) need to counter sign the documents.
    • Agreement Name - The name of the agreement as it appears in the Manage page.
    • Message - The global message that is included in the Please Sign email (if no other message is explicitly imported with the .csv).
    • Language - What language should be used in the email and on-screen instructions.
    • Set an expiration date for this document (Optional) - Defines a number of days that the agreement remains viable before automatically expiring.
    • Set password to open signed PDF (Optional) - Defines a password to be applied to secure the signed document.
    • Preview, position signatures or add form fields - Allows the sender to place fields on the template.

    When done, click Next

    Select options and send

    Note:

    A Send in Bulk agreement left in a Prefill or Draft state will automatically expire 24 hours after the creation time.

Adding automatic document expiration

Automatic document expiration allows for account and group level configuration. Expiration can be defined for a default time limit, with an optional setting to permit the sender to edit the default value.

Document expiration is measured in whole days (24-hour increments) starting when the agreement is created.  For example, if you configure an agreement for expiration in 3 days, the agreement expires exactly 72 hours after the agreement is sent (if not completed).

Each recipient must complete the signature process before the deadline. Any individual agreement not completed before the deadline is automatically expired.

Set expiration date

Note:

The account or group administrator can configure document expiration to ignore the expiration deadline if the remaining recipients are internal (counter-signers).

Dapatkan bantuan lebih cepat dan lebih mudah

Pengguna baru?