The Post-Signature Page and Email

Where you set it up

In Contracts › Templates, opening a template: above the sheet you find the Page after signing and Email after signing sections. They are visible to admins and to members with the “Can edit contract templates” permission, like the rest of the editor.

The page: text blocks and one button

A new template starts with a suggested page, written in the template’s language just like the emails: the language shared by the selected markets, otherwise the language you are using the app in. It has a thank-you block (“Thank you {{customer_name}}, your contract for {{service_name}} is signed.”) and, if your plan includes the client chat, a block inviting the client to write to the agency plus the chat button. As long as you leave it alone, the suggestion follows the markets’ language and your plan; once you edit it, it is yours and no longer changes on its own. It is saved as it is, like the sending email.

The page is built out of blocks, in the order the client reads them:

• + Text — as many blocks as you want, up to 2,000 characters each.
• + Chat button — only one. The label is free text, up to 80 characters; the suggested one is “Open the chat with {{agency_name}}”.
• Blocks are reordered with Move up and Move down and taken out with Remove.
• Under the fields sit the variable chips: one click drops them into the text.
• The B button makes the selected text bold (it wraps it in two asterisks, **like this**; a second click removes it). Bold works one line at a time.
• Web addresses written in the text — including the payment links coming from the instructions — become clickable on their own and open in a new tab.
• Preview opens the page as the client will see it, with sample data (“John Smith”).

If you add no blocks at all, the client sees the standard page: the “Contract signed” title and the button to download the PDF. The download button is there either way, even when the page is yours.

When there are no blocks — a template created before the suggested page existed, or one you emptied — under the “No blocks” line you find the Use the suggested page button: it inserts the suggestion in the template’s language, and you then save it like any other change. On existing templates SalesControl never adds anything by itself.

When the chat button appears

The button only shows when both of these are true:

• the agency plan includes the client chat (Enterprise);
• that client’s chat link is active.

Both are re-checked every time the signing link is opened: revoke the chat link and the button disappears at once; regenerate it and the button is back. When they are missing your texts stay and only the button goes: the chat_link variable renders empty, not its own name.

On plans without the chat, the two sections open with a notice telling you so in advance, and a link to upgrade.

The «contract signed» email

This is the email that carries the signed PDF as an attachment. In the Email after signing section you write the Subject and the Text. Here too the B button makes the selection bold, and links in the text arrive clickable.

Both fields arrive pre-filled with the default text, in the template’s language: the language shared by the selected markets, otherwise the language you are using the app in. There is one subtlety worth knowing: if you save leaving the text as it is, SalesControl treats it as if you had written nothing, and the signer receives the default message in their own language. Write your own instead, and yours goes to everybody.

The default text comes in two versions: a plain one (“Thank you …, attached you will find the signed contract for …”) and one that adds the private chat link, the “No password needed” line and the suggestion to open it on a phone and add it to the Home screen. The one proposed follows your plan.

The copy to the signer goes out after the effects of the signature, not before: the chat link is born together with the client, and an email sent a moment earlier could not carry it.

The variables you can use

Page and email share the same list. There is no signing link and no expiry: the contract is already signed.

The sender of the sending email

One step back, in the Sending email section of the same template: the Sender select decides the name the client reads in the “From:” field of the email carrying the signing link.

• Agency name — the historic behaviour.
• Whoever sends the contract — the profile name of the person sending it appears. If a colleague resends it with Send again, the sender becomes theirs: it is always whoever sends it now.

Either way replies still reach whoever sent it: the reply-to address does not change.

The sending email variables are customer_name (first name), customer_full_name (full name), customer_last_name, service_name, agency_name, closer_name, signing_link and link_expiry_date.

Cases where the chat link is not there