Skip to main content

Setting up a sales order template for signature

For administrators: set up a sales order template, such as a letter of authority, so your team can send it to customers to fill in and sign online

Written by Nick Kewney

Set it up in four steps

  1. Ask The Layer to switch it on. Sending sales order documents for signature is a company option. Until it is on, none of the settings below appear.

  2. Open the template. Go to Settings, Output Templates and open the template, for example your letter of authority. Sales Order Compatible must be ticked. If you have just ticked it, save and open the template again.

  3. Tick Can Be Sent For Signature, and under Signer Fields click Add field for each detail the customer types in (see below). Save.

  4. Place the fields and the signature on the page. Edit the template's pages and type the snippets where each value should appear (see below). Then test it with Try it yourself first.

New to sales order templates? Start with Setting up and using sales order documents.


Where each detail comes from

A signed document has three kinds of detail, and each comes from a different place:

  • Details The Layer already holds, such as the customer's name, registration number and addresses. These are filled in when you click Generate, from the usual sales order snippets, for example $$sales_order_customer_name$$. The customer sees them but cannot change them.

  • Details the customer types in, such as their current provider or the numbers to port. These are the Signer Fields you add to the template. Each one appears as a box on the signing page, and lands in the document where you type $$so_field_key$$.

  • The signature. The signing page always asks for the signer's name, job title, email and signature, and for confirmation that they are authorised to sign. Place them with $$so_signblock$$, or one by one with $$so_sign_image$$, $$so_sign_name$$, $$so_sign_position$$, $$so_sign_date$$ and $$so_sign_email$$.


Signer field settings

  • Key: a short name in lower case letters, numbers and underscores, such as numbers_to_port. Place it on the page as $$so_field_numbers_to_port$$.

  • Label: what the customer sees above the box.

  • Group: fields with the same group are shown together under that heading.

  • Type: Single line, Multi line, Email, Phone number, or Phone numbers (list). The phone types only accept UK numbers and tell the customer straight away if one is wrong. A list takes one number or range per line, for example 01632 960000 - 0099.

  • Required, Max length and Help text: optional.


Questions

Where do the boxes on the signing page come from?
From the template's Signer Fields. The name, job title, email, signature and authority boxes are always there; everything else is a Signer Field you added.

Do I need a field for the customer's company name or address?
No. Use the sales order snippets: they are filled in from the order when the document is generated.

The document has two signature boxes. Does the customer sign twice?
No. They sign once and every signature box in the document is filled.

I changed the fields, but the customer still sees the old ones.
A document keeps the fields it was generated with. Generate it again, then send it again.

Send for Signature does not appear on the order.
Signing is not switched on for your company. Ask your representative at The Layer.

Send for Signature says no templates are set up.
No template has Can Be Sent For Signature ticked yet. Follow the steps above.

The template warns me about a field when I save.
It is telling you a $$so_field_...$$ on a page has no matching field, or a field is not placed on any page. A field that is not placed is still asked for, and appears on the signed copy's last page.

Can we use our own email wording?
Yes. Speak to your representative at The Layer.

Can customers be reminded automatically?
Yes. See Reminding customers to sign.

Do not use square brackets [ ] in the template's text: they stop custom fields filling in on that page. Signature and field snippets work on the template's pages, not in its header or footer.

Did this answer your question?