Category

How to Update Your Organization's Branding in BoldDesk

Updated:

Rebranding in BoldDesk allows you to update your organization’s brand identity, including the brand name, logos, support email addresses, and customer portal URL, while preserving your existing support environment.

Branding changes are limited to customer-facing and configuration-related elements. Existing tickets, conversations, attachments, users, groups, roles, permissions, automations, and historical records remain intact throughout the rebranding process.

Common use cases:

  • Renaming your company or support organization.
  • Launching a new brand or product line.
  • Migrating to a new email domain.
  • Updating your website, customer portal URL, or custom domain.
  • Refreshing logos and visual branding.

This article explains how to plan, implement, and validate branding changes in BoldDesk while minimizing disruption to agents and customers.

Prerequisites

Before starting the rebranding process:

  • Document your current brand name, logos, support email addresses, subdomain, and custom domains.
  • Review automations, workflow rules, SLA policies, webhooks, integrations, notification templates, canned responses, and custom forms for references to the existing brand.
  • Plan support email and domain migrations in advance and perform validation testing before notifying customers.
  • Identify customer-facing assets that may require updates, including Knowledge Base articles, email signatures, portal content, and notification templates.

Update the Brand Name

To rename a brand:

  1. Go to Admin > Brands.
  2. Select the brand to update.
  3. Update the Brand Name.
  4. Click Save.

Update Logos and Branding

To update your brand assets:

  1. Go to Admin > Brands.
  2. Select the required brand.
  3. Update the branding elements as needed.
  4. Save your changes.

You can update:

  • Brand logo
  • Favicon
  • Customer Portal branding
  • Agent Portal branding
  • Email branding elements

After updating branding, review customer-facing content for outdated references, including:

  • Knowledge Base articles
  • Email signatures
  • Notification templates
  • Canned responses

Learn more in How to Customize Agent Portal Settings in BoldDesk.

What Rebranding Changes

Rebranding updates customer-facing branding and configuration settings while preserving your existing support environment and historical data.

What Changes

Depending on the scope of the rebranding, you may update:

  • Brand names
  • Logos and favicons
  • Customer Portal branding
  • Agent Portal branding
  • Support email addresses
  • Customer Portal URLs and custom domains
  • Email branding elements

What Does Not Change

Rebranding does not modify operational data or user access. The following items remain unchanged:

  • Agent, administrator, and end-user accounts
  • Roles, groups, and permission assignments
  • Open, closed, and historical tickets
  • Conversations and attachments
  • Ticket activities and audit logs
  • Workflow configurations and automation history

If administrator email addresses are changing:

  • Update the administrator email addresses.
  • Complete the required verification process.
  • Confirm that administrators can successfully sign in after the change.

Update Support Email Addresses

If the rebranding includes a new email domain, update your support email addresses and verify that email authentication and routing continue to function correctly. Before removing existing support addresses, validate inbound and outbound email processing to minimize disruptions to customer communications.

Section Details
Email Authentication Requirements • SPF
• DKIM
• DMARC
Review After Updating Email Addresses Verify references to the previous email address in:

• Routing rules
• Automations
• Workflows
• Notification templates
Existing Tickets and Email Addresses If the previous support email address remains configured in BoldDesk, existing tickets can continue using that address. If the old address is removed, replies are sent from the currently configured default support email address. To minimize customer confusion, keep previous support email addresses active during the transition whenever possible.
Replying from a Specific Email Address Enable From Email Selection to allow agents to choose the sender address when creating or replying to tickets. Learn more in How to Change the “From” Email Address When Updating or Creating Tickets.

Update the Customer Portal URL or Custom Domain

If your Customer Portal URL or custom domain is changing:

  • Configure the new custom domain.
  • Complete the required DNS configuration.
  • Confirm SSL provisioning is complete.
  • Verify that the portal is accessible before announcing the change.

Recommendations

  • Configure and validate the new domain before communicating it to customers.
  • Verify that DNS records have propagated successfully.
  • Confirm that the portal is accessible from external networks.

During DNS propagation, the Customer Portal and support email services may be temporarily unavailable.

Learn more in:

Review Automations and Integrations

After completing the branding changes, review configurations that may still reference the previous brand name, email address, domain, or portal URL.

Recommended areas to validate include:

  • Automation rules
  • Workflow automations
  • SLA policies
  • Webhooks
  • Third-party integrations
  • Notification templates
  • Canned responses
  • Custom forms
  • Knowledge Base content

Update any remaining references to ensure a consistent customer experience across all communication channels.

Validate Rebranding Changes

After completing the rebranding process, validate the following areas to ensure that all customer-facing and operational functions continue to work as expected.

Validation Area Checks
Access Validation • Verify administrator login access.
• Verify agent login access.
Ticket and Email Validation • Create a test ticket.
• Verify ticket updates and replies.
• Test email-to-ticket functionality.
• Confirm outbound email delivery.
Workflow Validation • Verify workflows execute correctly.
• Test automations and SLA policies.
• Validate webhook integrations.
Branding Validation • Verify logos and branding throughout the portal.
• Review email templates.
• Review Customer Portal pages and Knowledge Base articles for outdated branding references.

Best Practices for Low-Risk Rebranding

  • Update and verify administrator email addresses before making branding changes.
  • Configure and test new support email addresses before retiring old ones.
  • Review automations, integrations, templates, and workflows for outdated references.
  • Communicate updated URLs and support email addresses to customers before and after the transition.
  • Test key workflows before announcing the rebrand.
  • Keep previous support email addresses active during the transition whenever possible.

Frequently Asked Questions

  1. Does rebranding delete or modify existing tickets?
    No. Rebranding updates branding-related settings only. Existing tickets, conversations, attachments, activities, and audit logs remain unchanged.

  2. Will rebranding affect users or permissions?
    No. Agents, administrators, end users, groups, roles, and permission assignments remain unchanged.

  3. Does renaming a brand update historical ticket conversations?
    No. Historical tickets and conversations are not modified when a brand is renamed.

  4. Can the old support email address still be used after changing domains?
    Yes. Older tickets can continue using the previous support email address as long as the address remains configured in BoldDesk.

  5. What should be reviewed after rebranding?
    Review automations, workflows, SLA policies, webhooks, integrations, notification templates, canned responses, and custom forms for references to the previous brand name, email address, or domain.

  6. Can the customer portal be temporarily unavailable during a domain change?
    Yes. Temporary unavailability can occur during DNS propagation and domain configuration steps (including SSL provisioning).

  7. How can customer impact be minimized during the transition?
    Keep previous support email addresses active when possible, test all changes before rollout, and communicate updated URLs and email addresses to customers in advance.

  8. If the old support email address is removed, what happens to replies on older tickets?
    Replies will be sent from the currently configured default support email address.

Related Articles

  1. How to Customize Agent Portal Settings in BoldDesk
  2. How to Change or Rename a BoldDesk Subdomain
  3. How to Change the “From” Email Address When Updating or Creating Tickets
  4. How to Change a Brand’s Customer Portal Custom Domain in BoldDesk
Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Comments (0)
Access denied
Access denied
Access denied
Access denied

No articles or sections found
No articles or sections found