Support Portal allows each agent to define a personal message signature — a structured sign-off appended to outbound messages. Unlike email-only signature systems, message signatures in Support Portal apply across all connected inboxes, providing consistent agent identification regardless of the communication channel.
Operational objective
Message signatures serve two primary functions:
- Agent identification — Each outbound message includes the agent's name, role, and relevant contact information, reinforcing professional communication standards across all channels.
- Operational consistency — A standardized signature format across the team ensures that all customer-facing communication meets organizational presentation requirements without relying on agents to manually compose sign-offs.
Signatures are configured per agent and managed through personal settings. There is no workspace-level override — each agent maintains their own signature content.
Configuring a message signature
Navigate to the profile icon at the bottom-left of the dashboard, then select Personal Settings.
Scroll to the Personal message signature section. The rich text editor supports the following formatting capabilities:
| Capability | Details |
|---|---|
| Text formatting | Bold, italic, underline, and other standard formatting options |
| Links | Embed clickable URLs for team pages, scheduling tools, or contact forms |
| Inline images | Upload a logo or headshot (subject to channel limitations — see below) |
Compose the signature content, then select Save message signature to apply.
Recommended signature structure
For regulated environments and enterprise deployments, consider including:
| Element | Example |
|---|---|
| Full name | Alex Moreira |
| Role / department | Senior Support Engineer — Network Operations |
| Direct contact | +31 20 555 0142 |
| Organization | Altores B.V. |
Keep signatures concise. Excessively long signatures consume message space and reduce readability, particularly on messaging channels where screen real estate is limited.
Signature behavior during conversations
Once configured, the signature is enabled by default. It appends automatically to every outbound message in the reply editor. Agents retain full control over the signature on a per-message basis.
Sending with signature
When the signature is active, it appears below the message composition area. No additional action is required — the signature is included automatically when the agent sends the message.
Editing the signature before sending
The signature content in the reply editor is fully editable on a per-message basis. An agent can remove a phone number, adjust a line, or clear the signature entirely for a specific message without affecting the saved template. Subsequent messages revert to the saved signature.
Disabling the signature
To suppress the signature for the current session, select the signature toggle in the message editor toolbar. When disabled, outbound messages are sent without the appended signature until the agent re-enables it.
Channel limitations
Message signatures render differently depending on the channel's API capabilities. The following distinction applies:
| Channel type | Signature rendering |
|---|---|
| Email inboxes | Full signature including formatted text and inline images |
| Website live chat | Full signature including formatted text and inline images |
| API inboxes | Full signature including formatted text and inline images |
| All other channels (SMS, WhatsApp, Telegram, etc.) | Text content only — inline images are stripped by the channel provider |
When designing signatures for a multi-channel deployment, ensure the text-only version remains informative and well-structured. Avoid signatures that rely solely on an image or logo, as these will render as empty on text-only channels.
Related capabilities
- For reusable message templates beyond signatures, see Canned Responses.
- To automate agent assignment based on inbox or conversation properties, see Automation.