<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=4052188&amp;fmt=gif">

 

Big Jobs Are Easy With MassMailerTM

Send documents out in bulk with SIGNiX's MassMailer feature

The new MassMailer™ feature from SIGNiX enables human resources departments, compliance personnel and other groups to easily generate and send out documents to be signed to a large number of individuals with a few simple clicks. Think of all of the time you spend now not only sending out annual privacy policy notices or reports, but think of all the work it takes to get those notices back signed and to clearly identify who has signed what. MassMailer simplifies that process dramatically, saving time, money and personnel. At the same time, you’ll also improve your employees’ and customers’ experience, making it simple for them to review and sign the documents wherever they are. 

How Does It Work?

First, upload a list of the recipients to SIGNiX. Then follow simple steps to add documents and then drag-and-drop signatures, initials and other fields right onto the documents for these recipients to fill out and sign. Once you hit Send, these individuals will receive emails letting them know where to view the document and will then walk them through the process to get the document signed.

How Do I Sign Up for MassMailer?

Contact SIGNiX (fill out the form to the right side of the page) for more information about how to purchase SIGNiX digital signatures or add MassMailer to your current license.

Once I've Signed Up for MassMailer, How Do I Get Started?

  1. Create a MassMailer-compliant CSV file. [link to anchor below]
  2. Log into your Document Center and create a new transaction.
  3. Dismiss the Add Party dialog by clicking the white X in the upper right corner of the dialog box.
  4. Choose the Mass Mailer button, and click Start.
  5. At the Import screen, tap Browse to locate the CSV file mentioned in Step 1 and click open.
  6. SIGNiX will verify if the CSV is formatted correctly and provide you with specific information if it is not. Follow the prompts to upload a new CSV if necessary.
  7. If there are no issues with the CSV, the screen will update to reflect all of the transactions. You can review these, if necessary.
  8. Continue by clicking on the Add Documents tab and upload one or more PDFs for each of the recipients to review, fill and sign, just like you would in a typical transaction. When you’re finished uploading, click the Add Signatures tab.
  9. The tool palette will show you ‘placeholder’ users depending on how many users your transactions include.
  10. Drag-and-drop signature, initial and other fields for each placeholder user just like you would in a typical transaction. When you’re finished, tap the Send tab.
  11. At the Send tab, you can customize the email message that gets sent to each participant alongside the link to their documents. You can also save the transaction as a template to be re-used by selecting the Save As icon in the upper right hand corner. Otherwise, when you’re ready, click Send All to start the Mass Mailer process. A confirmation dialog will appear to ask if you’re sure. Click Yes. 

How Do I Create the MassMailer CSV Import File?

SIGNiX MassMailer uses a simple, easy-to-create CSV (comma-separated value) file to prepare the list of recipients, their email addresses, and authentication information. CSV files can be created in common spreadsheet or text programs, and can also be generated by many CRM and other systems.


Click here to download a sample CSV file that you can customize for testing.


The MassMailer CSV must follow a specific format to be interpreted correctly by SIGNiX. It must have the following headers, in this order:

TransactionName, firstname, middlename, lastname, emailid, servicetype, ssn, dob, mobileno, questions, answers

Each line that follows this will generate individual transactions to be sent out by SIGNiX.

The information required by these headers follows here:

  • “TransactionName” – REQUIRED - A unique Transaction Name must be provided which includes a differentiator for each transaction (preferably Name). If a non-specific transaction name is provided (ie. “Compliance” rather than “Compliance for John Smith”) – there will be difficulty in locating the transaction in the Document Center when the transaction is underway or completed.
  • “firstname” – REQUIRED – First name of the reviewer / signer.
  • “middlename” – OPTIONAL – Middle name/initial of the reviewer / signer.  
  • “lastname” – REQUIRED – Last name of the reviewer / signer.
  • “emailid” – REQUIRED – Email address of the reviewer / signer.
  • “servicetype” – REQUIRED – This value indicates how the signer will be authenticated (identity verified) before they are allowed to review and sign documents. Submitters typically choose one service type for all of the parties on the list, however, different services may be chosen for different parties on the list. Note that charges may apply for certain authentication services. The submitter must provide the appropriate information required by that authentication service type as described below.
    • “SelectOneClick” – NO DATA REQUIRED – User is authenticated via email address and signs with a single click, followed by a confirmation step. If question(s) and answer(s) are also provided, then these will be presented to the user for response (signer must know the answer).
    • “select” – SSN, DOB REQUIRED –The SSN is validated against the user’s name and the DOB is checked for 18+. If question(s) and answer(s) are also provided, then these will be presented to the user for response. A fee is charged per attempt.
    • “SelectID” – SSN & DOB REQUIRED – User is authenticated through third-party knowledge-based authentication (KBA) via multiple choice questions based on 30 years of public database information. A fee is charged per attempt.
    • “SharedSecret” – MOBILE NUMBER REQUIRED – A text message is sent to a user’s mobile phone containing a unique passcode. This passcode must be entered correctly before the user can continue to review and sign documents. A fee is charged per attempt.
    • “ssn” – REQUIRED for select and SelectID service types ONLY – User’s Social Security Number. Format: xxxxxxxxx (9 digits, no spaces or hyphens)
    • “dob” – REQUIRED for select and SelectID service types ONLY – User’s date of birth. Format: mm/dd/yyyy.
    • “mobileno” – REQUIRED for SharedSecret service type – User’s mobile phone number. Format: xxxxxxxxxx (9 digits, no spaces or hyphens)
    • “questions” – OPTIONAL for select service type – Questions that will be posed to user. Multiple questions can be entered, but must be separated by semicolons. For example: What color is the sky?; What are the first four numbers of your account number?; What’s your first name?
    • “answers” ” – OPTIONAL for select service type – Known answers to questions posed to user. User must accurately provide these answers for authentication to succeed. Note that matching capitalization is not required.   Multiple answers can be entered, but must be in the same order as the questions and separated by semicolons. Do NOT add a space after the semicolon. For example:

Blue;1234;Tom - CORRECT

Blue; 1234; Tom - INCORRECT

 

NEW - AUGUST 2014 - Carbon Copy feature added to MassMailer

Need a way to send all of the signed documents to a single point after they've been signed? You can now add a 'carbon copy' email address (or addresses) to the CSV. When each transaction is complete, a copy of the completed documents will be delivered as an email attachment to this email address.

We even recommend that high volume users of MassMailer set up a unique email box for receiving these documents to better manage the flow. There are many tools available for Outlook, for example, that can package these attachments conveniently.

In order to set up CC for a particular transaction, simply add an email address after the last comma-spearated value. No header is required. More than one email address can be used, simply separate them with a semicolon.

 

NOTE: Do not enter data in columns /sections that are not required per the service type as this will flag the user for an error when imported. The error will be highlighted for the submitter to fix and a new CSV will need to be re-imported.

Here’s a sample view of what a CSV should look like:

CSV preview resized 600