Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Neil
Beigetreten 13. Mai 2021
·
Letzte Aktivität 04. Sept. 2024
Folge ich
0
Follower
1
Gesamtaktivitäten
123
Stimmen
2
Abonnements
40
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Neil
Neil hat einen Kommentar hinterlassen
That is correct, management of the custom statuses will be handled from within the Admin page.
Kommentar anzeigen · Gepostet 04. März 2024 · Neil
0
Follower
0
Stimmen
0
Kommentare
Neil hat einen Kommentar hinterlassen
I understand where you're coming from. At the moment, this is a limitation on how Organizations can be maneuvered. With this in mind, we highly appreciate if you could share your product feedback here where our Product Managers keep tabs on customer feedbacks.
Kommentar anzeigen · Gepostet 29. Feb. 2024 · Neil
0
Follower
0
Stimmen
0
Kommentare
Neil hat einen Kommentar hinterlassen
Regarding your questions.
Can you confirm adding new support address that is used today as a support email alias won't break anything?
As mentioned here, Zendesk doesn't support the use of aliases, distribution lists, shared mailboxes, Google groups, or any non-standard email clients or services due to added complexities of routing and issues troubleshooting.
We have today 3 different addresses. Is there any harm in deleting those which were not set up in the account?
Aside from the system support address (which cannot be deleted), there should be no harm in deleting any support address as long as it is not used in your workflow
The new support address I would like to use is currently being used by an end user and thus I was not able to create it. If I will change that end user to be an agent - will it allow me to create this new address?
The best course of action is to simply change the email address of the end-user to a different one.
Kommentar anzeigen · Gepostet 29. Feb. 2024 · Neil
0
Follower
0
Stimmen
0
Kommentare
Neil hat einen Kommentar hinterlassen
No documentation regarding how the integration is setup is available yet but initial testing shows that the agent status in Support reflects in Tymeshift automatically.
This applies to both default and custom agent statuses.
Kommentar anzeigen · Gepostet 29. Feb. 2024 · Neil
0
Follower
0
Stimmen
0
Kommentare
Neil hat einen Kommentar hinterlassen
Host mapping won't affect the support address you have set up in your account. This will only change the URL the end-user sees when navigating to your help center.
To change the support address that end-users see on your email reply. The best way would be to add a new support address and set it as your default. If you plan to add an external support address, you would need to follow these steps to allow Zendesk to send emails on behalf of the external support address.
Kommentar anzeigen · Gepostet 18. Feb. 2024 · Neil
0
Follower
1
Stimme
0
Kommentare
Neil hat einen Kommentar hinterlassen
You can map a support address to a ticket using brands. Please see here : https://support.zendesk.com/hc/en-us/articles/4408836507162-Adding-email-support-addresses-for-multiple-brands
Each brand will have it's own support address and you can simply use a ticket to change the brand that is associated to a ticket.
Kommentar anzeigen · Gepostet 18. Feb. 2024 · Neil
0
Follower
0
Stimmen
0
Kommentare
Neil hat einen Kommentar hinterlassen
There's no default option to remove a user from an organization, but you can remove an organization from the user's profile
- Open the user's profile.
- Click the name of the organization you want to remove, then select Remove.
Kommentar anzeigen · Gepostet 18. Feb. 2024 · Neil
0
Follower
0
Stimmen
0
Kommentare
Neil hat einen Kommentar hinterlassen
The condition Ticket: Comment text is available only in the Triggers feature and not in the Automations feature.
Kommentar anzeigen · Gepostet 15. Feb. 2024 · Neil
0
Follower
0
Stimmen
0
Kommentare
Neil hat einen Kommentar hinterlassen
When a sandbox is created it copies the owner and current admins, agents that were upgraded to admins after the sandbox was created will not be added automatically, as mentioned in the article, they will need to be manually added into the sandbox instance.
The sandbox instance does not carry over the SSO you have in your production.
More details about sandbox environment here : https://support.zendesk.com/hc/en-us/articles/6150628316058-About-Zendesk-sandbox-environments
Kommentar anzeigen · Gepostet 13. Feb. 2024 · Neil
0
Follower
0
Stimmen
0
Kommentare
Neil hat einen Kommentar hinterlassen
Activating the agent workspace option has no additional cost if you are already subscribed to Support Team, Professional, Enterprise or any of. the Suite plans.
Kommentar anzeigen · Gepostet 13. Feb. 2024 · Neil
0
Follower
0
Stimmen
0
Kommentare