How can we help you?

Email Signatures: Company Policy, Personal Signatures and Legal Disclaimer

Overview

Every email an agent sends from Velaro can carry a signature. Administrators decide whether agents write their own, whether the company signature is the default, or whether the company signature is required. Administrators can also add an optional legal disclaimer under the signature.

Nothing changes until you set a policy. With no policy, each agent keeps using their own personal signature, exactly as before, and no disclaimer is added.

The three signature modes

Mode What it means
Personal only Each agent uses their own signature. This is the default when nothing is set.
Company default The company signature is used by default. Agents can still switch to a personal signature.
Locked Agents cannot use personal signatures. Every email carries the company signature.

In Locked mode, agents see the company signature in the composer and cannot edit or replace it. Saved personal signatures stay on file and come back if you change the mode.

Company signature

The company signature is formatted text, up to 4,000 characters. If you leave it empty, Velaro uses the email signature already set in your ticket settings, so existing setups keep working.

Legal disclaimer

The disclaimer is a block of text added under the signature on outgoing email. It is off by default.

  • Turn it on or off with the disclaimer switch.
  • The text is editable, up to 2,000 characters.
  • Velaro suggests starting text that names your company: "All [company] correspondence is confidential. If you are not the intended recipient, notify the sender and delete this message." You can use it as is or change it.
  • Have your own counsel review the wording. Velaro does not provide legal advice.

Team overrides

You can set a different policy for one team, for example a Locked policy for Billing while everyone else stays on Personal only. A team override can change the mode, the signature and the disclaimer. Anything a team override leaves unset follows the company-wide policy.

To remove an override, clear all of its values and save.

The name line above the signature

You can add a line with the sender's name above the signature on every outgoing email. The name line has three settings, and each one flows down from the whole site to a routing group, and then to the agent when you allow it:

  • Name line: No name line (the default), Agent name, Team name, or Agent name and team name.
  • Name to use: Real name (the default), or Display name. If an agent has no display name, their real name is used.
  • Team name shown: The text used for the team name, for example "Customer Support". If you leave it empty, the routing group's own name is used. A group can show its own text, and the site text covers every group that does not.

Nothing changes on your emails until you choose a name line, because the default is no name line.

Every setting shows where it comes from: Agent override, Group override, Inherited from site, or Platform default. This is the same wording used for the call presence settings.

Who can change what

  • Agents can choose their own name line: On by default. When on, each agent can pick their own name line and name from their signature settings, on the web and in the mobile app. It never applies while the signature is Locked.
  • Team admins can change group settings: On by default. When off, only site administrators can edit group signature settings.
  • Apply to existing groups: When you change the site default, choose whether groups that follow the default pick it up, whether every group override is cleared, or whether existing groups keep exactly what they do today and only new groups follow the new default.

Where to find it

Open Compliance, then the Signatures tab. The company signature, the disclaimer and the name line are all on that page, because they are the corporate requirements for outgoing email.

Version history and rollback

Every save is kept as a version with who changed it and when. Open Version history on the Signatures tab and choose Roll back to this version. The restored settings are saved as a new version, so the history is never rewritten. Only site administrators can roll back.

Personal signatures for agents

When the policy allows personal signatures, each agent can keep a small set of saved signatures, give each one a name and pick one when writing an email. Agents manage these from their profile. The composer shows the signature that applies and lets the agent switch when the mode allows it.

Where to set it

An administrator opens the email signature policy in the admin settings and picks a mode, a company signature and the disclaimer. Only administrators can read or change the policy. Agents who are not administrators see the result in their composer.

Ask Moshky, the API, or the command line

Moshky can read and change the policy for you. For example: "Lock everyone to the company signature" or "Turn on the legal disclaimer for the Billing team." Moshky shows the change first and saves it only after you confirm.

The same controls are available in the Velaro MCP server and the command line.

  • MCP tools: signature_policy_get, signature_policy_set, signature_policy_history and signature_policy_rollback.
  • Command line: velaro signature policy get and velaro signature policy set, for example velaro signature policy set --mode locked or velaro signature policy set --team-id 12 --disclaimer true.

Options for set: --mode (locked, company-default, personal-only, or default to follow the company-wide value), --signature, --disclaimer, --disclaimer-text, --name-format (none, name, team, name-and-team), --name-source (real-name, display-name), --team-label, --allow-team-overrides, --allow-agent-overrides, --apply-to and --team-id (0 or left out means company-wide). Options you leave out are not changed.

To review or undo a change: velaro signature policy history lists the saved versions and velaro signature policy rollback <versionId> restores one.

Common questions

An agent says they cannot edit their signature. The policy is probably Locked for their team or the whole company. Change the mode, or ask an administrator.

The disclaimer is not showing. Check that the disclaimer switch is on and that the email is sent from Velaro. Replies sent from outside Velaro do not get it.

Which signature wins when a team override exists? The team override. Settings it leaves unset follow the company-wide policy.

An agent does not see the name line options. The signature is Locked, or Agents can choose their own name line is turned off for the site.

The name line shows the real name but I chose Display name. That agent has no display name set, so the real name is used.

Can I use different disclaimer text per team? Yes. Set the disclaimer text on that team's override.

Related guides

  • Email and ticket settings
  • Moshky guide
  • Command line setup guide
Share: Email

Was this article helpful?