Decommissioning a native Zendesk support address involves setting up a notification trigger to inform customers of the change.
Create a trigger with specific conditions and actions to notify customers that the address is being retired. If you're worried about losing traffic, consider enabling wildcard addresses to catch any late-arriving emails. This ensures that emails sent to the old address are not lost, although it limits routing rules through triggers. For more information, visit theoriginal article.
To decommission an external Zendesk support email address, you need to create a new native Zendesk Support address. This ensures that existing ticket responses are not lost. First, create a unique native Zendesk Support address within the same…
Yes, enabling wildcard addresses can help ensure no emails are lost when decommissioning a support email. Wildcard addresses allow your account to accept emails sent to any address at your subdomain, including the decommissioned one. However, this…
Informing customers about a new support email address can be done through triggers and notifications. Create a trigger that automatically responds to emails sent to the old address, informing customers of the new address. You can also set up…
Tags play a crucial role in managing triggers when decommissioning a Zendesk support email. Use tags like 'decommissioned' or 'donotreply' as prohibitive conditions in your triggers. This prevents multiple triggers from firing upon ticket…
To ensure existing tickets are not lost, redirect the forwarding rule from the old support email to the new one. This allows existing tickets to continue being updated, as the ticket will be updated regardless of which support address the response…