Service Cloud Reply Templates currently allow agents to save reusable response content, but there is no centralised way to automatically apply a branded email signature when replying to tickets.
Customers with multiple support inboxes, departments, brands, or agents need different signatures depending on the outgoing support email address or the agent sending the reply
Without this functionality, agents must manually add signatures to templates and custom replies, which can lead to inconsistent branding, duplicate signatures, and incorrect sender details.
Proposed Solution
Add a new Signature Management setting in Service Cloud that allows administrators to create and assign preset email signatures
Signatures should support:
- Brand Logo Image Upload (optional)
- Sender name
- Role or position
- Company or brand name
- Phone number (optional)
- Website Link
- Business address
- Social links
- Legal disclaimer
- Rich text formatting and dynamic tags
- Signature Assignment
Allow signatures to be assigned to:
A specific Support Email Address
A specific user or agent
An account-wide default signature
Each configured support email address should include a new field called Default Outgoing Signature.
For example:
support@company.com → Customer Support signature
accounts@company.com → Accounts Team signature
warranty@company.com → Warranty and Returns signature
Expected Behaviour
When an agent replies to a ticket, Service Cloud should automatically apply the correct signature based on the selected outgoing support email address and/or assigned user.
The signature should be appended automatically to:
- Manual ticket replies
- Reply Templates
- Forwarded replies
- Custom messages
Reply Templates should store only the reusable response content. The signature should be dynamically added when the agent inserts the template or sends the reply
This ensures that administrators can update a signature once without needing to edit every Reply Template.
Suggested Signature Priority
- User signature assigned for the selected Support Email Address
- User personal signature
- Default signature assigned to the selected Support Email Address
- Account-wide default signature
- No signature applied (option)
Workflow
- Administrator creates a signature in Settings > Signature Management.
- Administrator assigns the signature to a Support Email Address, user, or both.
- An agent opens a ticket and selects the outgoing support email address.
- The agent writes a custom reply or inserts a Reply Template.
- Service Cloud automatically appends the relevant signature.
- The agent previews and sends the reply.
- The final sent message, including the signature, is stored in ticket history.
Key Requirements
- Signature should update automatically if the agent changes the outgoing support email address.
- Administrators should be able to lock signature content to prevent agent edits.
- Deactivated signatures should not apply to future messages but should remain visible in historical ticket replies.
- Existing Reply Templates should remain unchanged after release.
- Support dynamic tags such as {{agent.name}}, {{agent.role}}, {{support_email.address}}, and {{company.name}}.
- Prevent duplicate signatures where a template already contains signature content.
Value
This feature would improve brand consistency, reduce manual work for agents, support multi-brand and multi-department organisations, and ensure the correct sender details are included in every customer-facing Service Cloud reply.
