Brand Supportbench customer messages: reply addresses, templates, surveys and chat transcripts

Consistent customer communication means more than adding a logo. A customer needs to recognize the sender, understand the update, find the requested action and know what happens next. Supportbench provides different controls for reply identities, reusable case content, survey invitations and chat transcripts. This guide helps you choose the right one and build a coherent B2B support experience without assuming one template changes every email.

Choose the editor that owns the message  ·  Design a message around the customer’s next action  ·  Set the reply identity and shared signature  ·  Build reusable replies without accidental case changes  ·  Brand a survey invitation for its actual context  ·  Create a branded chat transcript email  ·  Check the message as a customer would

Choose the editor that owns the message

A case template is not the universal email wrapper for the whole account. Changing a reply signature does not rewrite survey invitations or a widget’s transcript body. Start with a sample of the message the customer actually received and identify the feature that generated it.

Design a message around the customer’s next action

Choose a clear sender name, a short opening, a factual status and one obvious next action. For a complex B2B case, include the affected organization or service only when appropriate for the recipients. Do not copy internal commercial notes, unrelated contacts or a previous customer’s details into a reusable message.

• Explain what is known, what remains under investigation and who owns the next step.
• Use a real next-update commitment only when the team has agreed to meet it. A template should not invent a deadline.
• Keep essential meaning in text. A logo may be blocked by the recipient’s mail client.
• Use descriptive links, short paragraphs and readable contrast. Avoid a large header image that pushes the useful content below the first screen.
• Decide which details agents must review each time: customer name, affected asset, environment, requested evidence and next update time.

Set the reply identity and shared signature

1. With permission to administer the relevant email settings, open Settings → Email configuration → Address / signature. Open the intended record or select New Address.
2. Enter an internal Name that helps agents choose the correct identity. For a new record, enter the real Email address; it is locked after creation.
3. Set Display name to the customer-facing sender name. Review Active and Default active address. A default address must be active.
4. Edit Signature with the shared identity, contact information and restrained branding your organization requires. The signature is appended when agents send from this system address.
5. Save, reopen the record and inspect it. Then send a controlled case reply using that address and check the actual received sender name, address, signature and reply path.

Avoid duplicating the same footer in both the reusable reply content and the shared signature. If an agent-specific signature also applies in your setup, inspect the final message rather than assuming the editors automatically remove duplicates. Domain authentication is a separate administrative step: follow the address and signature reference before relying on custom DKIM.

Build reusable replies without accidental case changes

1. Open Settings → Cases → Templates and select the relevant template or create one for a specific task. Name it by the situation it solves, such as Request integration diagnostic timestamps.
2. Write the customer-facing content in a reusable form. Separate facts that stay the same from details the agent must confirm for each case. Use only variables supported by that template context.
3. Review the template’s configured case options as carefully as its text. A template can carry operational settings; do not configure a priority, customer, asset or routing action merely to add branding.
4. Apply it to an approved training case. Inspect the inserted content, recipients, activity type and any changed case fields before submitting the activity.
5. Test a second case with different customer context. Remove hard-coded details that could expose the first customer or incorrectly categorize the next case.

For complete template behavior and source-case copying, use the response template operations guide, source-case template procedure and case template configuration reference. Copying a richly configured source case deserves its own review; it is not a harmless shortcut for copying a visual footer.

Brand a survey invitation for its actual context

A survey invitation should tell the recipient what experience you are asking about and provide the generated response link. A case-triggered invitation can use supported case context. A scheduled relationship survey has a recipient context and must not pretend to describe a particular closed case.

1. Open the relevant Survey forms record and confirm the selected community and invitation content. The community supplies the applicable logo source.
2. Choose supported variables for the actual delivery route. For example, the scheduled campaign uses {{first_name}}; the case workflow supports {{contact_first_name}}. These are not interchangeable names.
3. Retain the generated {{survey_url}} link and write a short explanation of the survey’s purpose. Do not build a response URL from an example or reuse another recipient’s link.
4. Verify a controlled delivered invitation, including a recipient with incomplete profile details. The editor’s appearance alone does not prove the final variables, links or mailbox rendering.

Use the survey-variable guide for context-specific examples and Survey forms configuration for form settings. A branded invitation does not change who is eligible for a scheduled survey or the campaign’s timing.

Create a branded chat transcript email

1. With Administer chat widgets permission, open Settings → Self-Service → Chat widgets, select the intended widget and open Messages & follow-up. The custom-branding controls require account support for this capability. If they are absent, ask your administrator or Supportbench Support to confirm availability; do not try to bypass the missing option with HTML.
2. Find Transcript email. Review whether it is enabled and the Transcript subject. Confirm that you are editing the widget used on the intended customer site.
3. Enable Use a custom branded email to replace the standard email body. With this option off, the standard email remains in use; turning it off again restores that standard body.
4. In Custom email body, add the introduction, logo or footer you need. Use Insert transcript, or place {{chat_transcript}} exactly once on its own line. Keep the transcript itself available between your introduction and footer.
5. Save the widget settings and run a controlled live-agent chat through that widget. Use an approved test contact with an email address, include at least one live agent reply, and close the conversation. Transcript email must be enabled, the conversation must be non-bot, and a usable configured or default From address must resolve for the close transition to queue the email. Inspect the delivered subject, branding and complete customer-visible transcript. Private messages are excluded.
6. Queueing is not confirmation of delivery: check the actual test inbox. Check another test without loading external images. The introduction and transcript should still make sense. Confirm the recipient and conversation are correct before making the new branding part of your team’s standard procedure.

For the widget’s other messages, availability and routing controls, use the Chat widgets configuration guide.

Check the message as a customer would

If the wrong content appears, identify the message generator first. Check the selected reply address for signature problems, the applied template for reused case text, the survey context for variables, and the actual widget for transcript branding. Keep a sanitized before-and-after example and an owner for each shared message so future product or policy changes reach the right editor.

Continue learning

• Configure outbound addresses and signatures
• Use response templates consistently
• Create repeatable cases from a source-case template
• Configure case and chat templates
• Choose supported survey invitation variables
• Configure chat widgets and transcript messages
• Connect the incoming support mailbox