When using eSignature feature in Salestrekker to sign documents online, you can embed template tags to documents that you are signing frequently, so they will be recognized when you initiate document signing process. All field will be allocated to correct signing party automatically.

This article is to provide instructions and basic tags that you can simply copy/paste to your document templates to appropriate positions within the document.

Supported field types that can be preset are:

  • Signature - where signers signature will be requested;

  • Date - where the date when signature was entered will be printed;

  • Checkbox - where you can set choices to be ticked by signers;

Setting Up Your Templates

In document you can copy/paste codes shown bellow to according places in documents where you would like them to show.

You choose number of signers when you configure the request by selecting them from the list. Signers will be in order from left to right and it will apply as well if you mix Clients and Users in the request:

Feel free to change font size in order to fit the template tag where you need it. Font size doesn't play a role in the request itself. However it is important to have the tag showing in one line.

Correct:

Wrong:

List of tags for Signature and Dates that can be Copy/Pasted into Document templates

Signer 1

Signature: [sig|req|signer0|Signature|Signature1]

Date: [date|noreq|signer0|SignatureDate|Signatured1]

Signer 2

Signature: [sig|req|signer1|Signature|Signature2]

Date: [date|noreq|signer1|SignatureDate|Signatured2]

Signer 3

Signature: [sig|req|signer2|Signature|Signature3]

Date: [date|noreq|signer2|SignatureDate|Signatured3]

Signer 4

Signature: [sig|req|signer3|Signature|Signature4]

Date: [date|noreq|signer3|SignatureDate|Signatured4]


IMPORTANT TIP: If you plan to send same documents on occasion to be printed and signed manually, would be best to color signature template tags white. Otherwise they will show in printout.

Just select them and apply Font styling to change text color to white. That way tags will be invisible to human eye, but will still be recognized and triggered when you launch eSignature request:

Also, if you don't have the need to customize in depth and require to input signature tags one by one, we support signature merge tables that can be used and that will populate whole section including signature tags to your documents. These merge keys are (just copy and paste this code to the document):

Signatures table - {@dealTablesSignatures}

This will produce complete table with all client names and with their signature tags applied.

Broker Signature table - {@dealTablesOwnerSignatures}

This will produce complete table with brokers name (deal owner's name) on it along with his appropriate signature tags applied.

Using Checkboxes

In addition to Signatures and Dates, Checkboxes can also be included in templates allowing you to prepare which signer will have option to make selections on the documents while signing it.

You would create a checkbox tag by defining it per instruction below and then paste it in word document (most probable within checkbox object), set font size to be between 1-2pt so it doesn't distort your document look and apply white coloring so tag is invisible when document is used outside of eSignature feature.

There are three kinds of supported checkboxes types:

1) When all checkboxes are required to be selected

[$chknum(1-50|group|reqall|signernum(0-9)]

There can only be one group of these checkboxes per doc. For that reason parameter "group" is always fixed and has no numeration. You can have checkboxes spreading on various pages by assigning different $chknum to checkboxes they would all be required to their order. Signer numeration goes from 0-1. Signer0 would be the first Client in a deal. Numeration starts as such due to other components that require defining persons starting at 0. You are free to choose those parameters as it fits your doc - both for $chknum and singernum.

Examples that can be copy/pasted:

[$chk1|group|reqall|signer0]

[$chk2|group|reqall|signer0] - these two will be required for Client 1 (Signer0)

[$chk3|group|reqall|signer1]

[$chk4|group|reqall|signer1] - these would be required for Client 2 (Signer1)

[$chk5|group|reqall|signer2]

[$chk6|group|reqall|signer2] - these would be required for Client 3 (Signer2)

. . .

[$chk50|group|reqall|signer9] - this would be last possible checkbox setup for this gorup as 50 is maximum limit for required checkboxes. In this particular case this 50th checkbox is required for 10th client in the deal (Signer9). This is more theoretical case to show how you can freely setup required checkboxes to their max limit.

2) When only one checkbox within the group of checkboxes is required to be selected

[$chknum(1-10)|groupnum(1-10)|req|signernum(0-9)]


This would be a defined group of checkboxes where client needs to select at least one to proceed further with signing a document.

These need to have defined groups and this is done via group numeration parameter 1-10. Within this group there can be multiple checkboxes ($chk numeration 1-10) that can be assigned to multiple signers (signer numeration 0-9). From those, person signing would need to opt on at least one to continue.

Examples that can be copy/pasted:

[$chk1|group1|req|signer0]

[$chk2|group1|req|signer0]

[$chk3|group1|req|signer0] - In this case Client 1 (signer0) in deal will be presented with 3 checkboxes of which he must select at least one in order to proceed.

[$chk1|group2|req|signer1]

[$chk2|group2|req|signer1]

[$chk3|group2|req|signer1] - in this case this group of checkboxes would require Client 2 (Signer1) to make at least one choice.

[$chk1|group3|req|signer2]

[$chk2|group3|req|signer2]

[$chk3|group3|req|signer2] - these would apply for Client 3 (Signer2)

[$chk1|group4|req|signer3]

[$chk2|group4|req|signer3]

[$chk3|group4|req|signer3] - these would apply for Client 4 (Signer3)

. . .

[$chk10|group10|req|signer9] - This would be theoretically last possible checkbox. 10th checkbox of 10th group for the 10th Client (Signer9).

3) When checkboxes are optional

[$chknum(1-10)|groupnum(1-10)|signernum(0-9)]

In this case checkbox tags will not require selection. Also need to be grouped and within group they would apply $chk id 1-10 for every checkbox in the group. Signer numeration (0-9) would specify which signer would they be assigned to.

Examples that can be copy/pasted:

[$chk1|group1|signer0]

[$chk2|group1|signer0]

[$chk3|group1|signer0] - In this case Client 1 (signer0) will be presented with 3 checkboxes that he can tick on (but it's not required to).

[$chk1|group2|signer1]

[$chk2|group2|signer1]

[$chk3|group2|signer1] - these would apply for Client 2 (Signer1)

[$chk1|group3|signer2]

[$chk2|group3|signer2]

[$chk3|group3|signer2] - these would apply for Client 3 (Signer2)

[$chk1|group4|signer3]

[$chk2|group4|signer3]

[$chk3|group4|signer3] - these would apply for Client 4 (Signer3)

. . .

[$chk10|group10|signer9] - Theoretically last possible - 10th checkbox of 10th group for the 10th Client (Signer9).

Red font in screenshot shows how does the tag look like when inserted into checkbox object in Word, prior being colored white (font size is 1pt):

After new keys are created and inserted right into the checkbox places in document templates and after that when DocuSign editor is launched they are immediately being recognized.

When signature is completed and clients made their selection you will get them showing as such:

Did this answer your question?