Ricerche recenti
Nessuna ricerca recente

Lucas Case
Data ingresso 16 ott 2021
·
Ultima attività 30 ott 2024
Seguiti
0
Follower
0
Attività totali
63
Voti
33
Abbonamenti
17
PANORAMICA ATTIVITÀ
BADGE
ARTICOLI
POST
COMMENTI NELLA COMMUNITY
COMMENTI AGLI ARTICOLI
PANORAMICA ATTIVITÀ
Ultima attività di Lucas Case
Lucas Case ha commentato,
Stephanie Langlois thanks for your reply, we had another example why this is important. Some agents were exposed to highly undesired content and couldn't be protected from it by simply suspending a user. I understand the WA API doesn't support it, but even being able to block incoming messages on the Zendesk side would be really helpful.
To further endorse/empower the desire for this functionality, I think steps need to be taken to address the Digital Services Act, which states that Digital platforms need (WhatsApp included) User Reporting and Redress Mechanisms: Platforms must provide easy-to-use mechanisms for users to report illegal content and appeal content moderation decisions.
Visualizza commento · Data ultimo post: 20 giu 2024 · Lucas Case
0
Follower
0
Voti
0
Commenti
Lucas Case ha commentato,
Mike DR how about subdomains? We want to allow the main domain, and block/reject a subdomain of the main domain? So allow: main.com and block: (reject:)sub.main.com
Visualizza commento · Data ultimo post: 11 giu 2024 · Lucas Case
0
Follower
0
Voti
0
Commenti
Lucas Case ha commentato,
I'm wondering if it is a problem to allow a head domain and block a subdomain. This has to do with a certain subdomain that is being used for messages from users (hashed), We would like to block these messages (an integration is already in place for this). So for example:
Allowlist: main.com
Blocklist: reject:sub.main.com
Visualizza commento · Data ultima modifica: 11 giu 2024 · Lucas Case
0
Follower
0
Voti
0
Commenti
Lucas Case ha commentato,
This is really strange, this is clearly not an admin (only) function. I understand that overhauling the roles structure/function is not easily done, but for the time being, changing the function Roles>Channels>Manage channels and extensions to also include the bots would be a really helpful improvement and logical (even though more fine-tuning would be desirable)
Visualizza commento · Data ultimo post: 02 mag 2024 · Lucas Case
0
Follower
4
Voti
0
Commenti
Lucas Case ha commentato,
In the Intelligence section the (suggested) macro's recently changed to be collapsed instead of expanded, so you can take in all the information and followup properly without "unnecessary" clicks. The macro's used to be directly visible when opening the ticket or opening the intelligence section (instead of being collapsed and only visible when clicking this tab open).
Is this a temporary change to facilitate some other changes/configurability later on? If not, this isn't a change for the better (even in the meanwhile, remembering the previous state of the suggested macro's to be collapsed or expanded would help speed up the agent).
Visualizza commento · Data ultimo post: 14 mar 2024 · Lucas Case
0
Follower
0
Voti
0
Commenti
Lucas Case ha commentato,
The (suggested) macro's recently changed in the intelligence section, they used to be expanded when opening the ticket or opening the intelligence section (instead of being collapsed and only visible when clicking this tab open).
Is this a temporary change to facilitate some other changes/configurability later on? Otherwise, this isn't a change for the better (even in the meanwhile remembering the previous state of the suggested macro's to be collapsed or expanded would help).
Visualizza commento · Data ultima modifica: 14 mar 2024 · Lucas Case
0
Follower
0
Voti
0
Commenti
Lucas Case ha creato un post,
Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)
We want to use a sandbox with copied over ticket, this is currently not possible a when using Custom Objects (due to the dependencies), no notice or option to proceed copying tickets, the custom objects aren't copied anyway. This affects IT that isn't able to test an app or configuration in a non-production environment
What problem do you see this solving? (1-2 sentences)
This is a crucial Enterprise function that is being blocked, I understand Custom Objects don’t work, but at least give us a workaround.
When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur, and how does this impact your business? (3-4 sentences)
Continuously because there is no way around the issue atm.
Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)
NO
What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)
When creating a sandbox with tickets, give a popup stating that the customer uses Custom Objects, due to architectural limitations, this cannot be included in the sandbox, give the customer the option to proceed and copy ticket without Custom objects (more of an acknowledgement/agreement). Or fix the initial issue
Data ultima modifica: 21 dic 2023 · Lucas Case
1
Follower
3
Voti
2
Commenti
Lucas Case ha commentato,
Visualizza commento · Data ultimo post: 10 nov 2023 · Lucas Case
0
Follower
0
Voti
0
Commenti
Lucas Case ha commentato,
Caroline Kello Am I correct in stating changes to an end user in their language are not captures in the Audit log? Knowing this would really be helpful because the end users language does or can be determining for routing or the offering of dynamic content. The article only states that changes in users are captured (and most changes are) but language doesn't seem to be.
Visualizza commento · Data ultima modifica: 18 ott 2023 · Lucas Case
0
Follower
0
Voti
0
Commenti
Lucas Case ha commentato,
@... I mean a vendor that created a normal ticket via channel that could be email, but also ticket form, chat (doesn't matter, the case is the same) and add that ticket as an email side conversation to another ticket. The reason why this should be an email side conversation is that the vendor is not part of your Zendesk agents (so creating a child ticket has no function, as this is normally being used for a partial responsibility or task fulfillment for another ZD department/agent not an external party).
Not every ticket is being grouped properly into the same conversation, so mostly due to improper handling of email outside Zendesk by customers/vendors. But the main reason is the first one.
Visualizza commento · Data ultimo post: 02 feb 2023 · Lucas Case
0
Follower
1
Voto
0
Commenti