Set a snippet as your email signature

Stop retyping (or manually re-inserting) your sign-off on every email. Mark a personal snippet as your signature and it’s inserted automatically at the bottom of the composer whenever you reply by email or start a new email conversation.

Before you start

• Decide what you want your sign-off to say: name, title, closing line — whatever you’d normally type by hand.
• You can create a new signature from the signature row in All Snippets, or use an existing personal snippet if you already have one.
• Signatures come from personal snippets only. If your sign-off currently lives in a Global snippet, copy the content into a personal one first.

Steps

To add a new email signature:

1. Open Settings → Snippets → All Snippets.
2. Find the pinned signature row.
3. Click Add signature.
4. Fill in the signature title and content.
5. Choose the required signature Language.
6. Optional: turn on Hide the signature from the reply box if you want the signature added only when the reply is sent.
7. Click Create.

The pinned row now shows your current signature with a Signature badge.

To change your signature using an existing personal snippet:

1. Open Settings → Snippets.
2. Open the personal snippet you want to use as your signature.
3. Toggle Use as my email signature.
4. Choose the required signature Language.
5. Optional: turn on Hide the signature from the reply box if you want the signature added only when the reply is sent.
6. Save.

Choose the language your sign-off is written in — not your product or interface language preference. If your signature includes a bilingual closing, select the non-English source language. The Create or Save control stays disabled until you choose a language.

That’s it — no separate signature editor. The snippet’s content is the signature, so editing the snippet later updates your signature everywhere it’s used going forward.

Only one snippet can be your signature at a time. Toggling it on for a different snippet automatically turns it off for the previous one.

If your signature has translations, the snippet settings also show a read-only Translations list so you can see which translated versions are available.

Where and when it appears

Signatures are available for email replies and new email conversations. They’re not inserted in chat-based channels — it’s an email-only feature.

How the signature appears depends on the signature setting:

• Visible signature — the signature is inserted at the bottom of the composer as soon as the composer opens for an eligible conversation, ahead of anything you type.
• Hidden signature — the signature is not displayed in the reply box. Instead, the composer shows a Signature added on send hint, and Atender adds the resolved signature when you send the email.

If the signature has a matching translation, Atender uses the resolved translated signature for the conversation. In hidden mode, that translated signature is still added on send without being shown in the editor first.

How it behaves with existing content

The signature is designed to stay out of your way rather than fight with whatever else is happening in the composer.

For visible signatures:

• Empty composer — the signature sits alone, and your cursor is placed above it so you start typing where you’d expect.
• Draft already has text — the signature is appended below your existing content; your cursor position isn’t disturbed.
• A macro inserts a snippet — the macro’s snippet is inserted first, and the signature lands underneath it once the macro’s insert completes.
• An AI suggestion replaces the draft — accepting an AI-suggested reply replaces the whole composer, signature included. The signature is then re-inserted at the bottom automatically, so you’re never left without it.
• You send, and the send fails — if sending errors out and your draft is restored, the signature comes back with it rather than being duplicated.

In every case, only one visible copy of the signature can exist in the draft at a time — replacing or clearing the draft clears the signature along with it, and it’s re-added the next time the composer re-evaluates the draft (for example, right after an AI suggestion lands).

For hidden signatures:

• The signature does not take up space in the composer and does not change your draft text while you’re writing.
• The Signature added on send hint confirms that a signature will be included when the email is sent.
• When you send, Atender adds the resolved signature — including the translated version when one applies — to the outgoing email.
• If sending fails and your draft is restored, the signature remains hidden in the composer and is added again on the next send attempt rather than being duplicated in your draft.

Verify it worked

1. Open an email conversation (or start a new one).
2. If your signature is visible, the composer should show it at the bottom automatically, with no snippet insertion needed on your part.
3. If your signature is hidden, the composer should show the Signature added on send hint instead of displaying the signature text.
4. Type a reply above it — or, for hidden signatures, type your reply normally.
5. Send. On your next reply, the signature should reappear on its own or continue to be added on send, depending on your setting.

If the signature isn’t showing up:

• Confirm the toggle is on for the intended snippet — only one snippet can be active as the signature, and turning it on elsewhere turns it off here.
• Confirm you’re replying by email — the signature doesn’t appear in chat channels.
• Check whether Hide the signature from the reply box is turned on. If it is, look for the Signature added on send hint instead of signature text in the composer.
• If a macro or AI suggestion just ran, give it a moment; visible signatures re-insert after those actions settle rather than appearing instantly.