Triggers - Action: Add Internal Note as a trigger action

46 Commentaires

  • Erin Boyle
    Actions pour les commentaires Permalien

    Hi Satia,

    It sounds like you're mainly trying to assist agents with next steps, is that correct? Just want to make sure I understand your use case. We don't have any plans to add the ability to add comments via triggers, but we are interested in exploring the problem space of additional, automated guidance for agents.

    Best,
    Erin

    3
  • Jamie Danjoint
    Actions pour les commentaires Permalien

    This has been stated by others, but getting in on this vote:

    • We add a private comment to the ticket if there is information about the user or Organisation that the agent should be aware of. We were finding it too easy to miss those notes and detail fields unless it’s within the body of the comment. Seeing the information within the private comment means the agents never miss the info.

    Life in Software Support is insanely busy and you're going a million miles an hour. Relying on an Agent to go to the Organization tab to view important details about a client or rely on seeing the slew of tags that get added to the case just isn't feasible.

    We store very important information on the org tab (ex: who has permission to request and approve configuration changes to their applications) that is easily overlooked. Please, please, please think outside the box on how we can get this accomplished. 

    THANK YOU!

    3
  • Corey Gould
    Actions pour les commentaires Permalien

    I would also love to be able to do this for a few reasons. 

    1. I have an automation that looks for "On Hold" tickets that have not been updated in 48hrs and changes the status to "Open". The intent here is to force a review/followup from my team members with the appropriate party so we if any resolution has been made. I would like the automation to add a private note to the effect of "This ticket was automatically reopened due to..." so the agent can quickly identify the reason without having to click through to events and then need to understand how events work. I want to keep it as simple and inline as possible. 

    2. I have a trigger that will change (via URL target) the Reply From address, so that I can force one support address per group. However, this interferes with the "Notify Requester of Received Request Trigger" sometimes along with other issues that have been brought up on the forums related to this. I would really like to be able to just assign a specific support address to each group natively so that, no matter what, replies send from a "Support" group come from support@, Technical Service from tech@, etc. regardless of what address the customer actually send to. 

    3. Similarly to item 1, I have an trigger that looks for replies/updates to side conversations and reopens the ticket, again to force a review of it. (Because the system notifications are inadequate and really easy to miss). So I would be using this to add a private comment to the effect of "This ticket has been reopened because a side conversation has been updated".

    Lastly, a lot of the comment here refer to a helpful instructional guide for using URL targets to do this, but the link https://support.zendesk.com/hc/en-us/community/posts/203164973-Adding-Comments-via-Triggers-and-Automations is no longer available and I would really like to see the instructions that have been seen by others as an effective workaround. 

     

     

    To change the reply from address in #2 I have a HTTP JSON PUT target set up called "Update Zendesk Ticket".  On the trigger, I use the action Notify Target with a JSON Body of {"ticket": {"recipient": "email@domain"}}

    What would the JSON Body code be to create a new private note? I imagine something to the effect of replacing "recipient with the correct attribute name.

     

    2
  • Satia Stevens
    Actions pour les commentaires Permalien

    Hi Erin,

    Thanks for following up. Reading through the threads, it seems we have the same use case as was stated by other customers: 

    • We add a private comment to the ticket if there is information about the user or Organisation that the agent should be aware of. We were finding it too easy to miss those notes and detail fields unless it’s within the body of the comment. Seeing the information within the private comment means the agents never miss the info.

    For our second use case, being able to add an internal note via trigger would speed up response time. For example, an account manager submits an inquiry without the customer on thread. A trigger could populate an internal note reminding them that the customer must be included for reporting purposes. The account manager updates the ticket, and then the support agent responds. 

    Currently there is a manual exchange between the agent and account manager, which wastes time. 

    Thanks,

    Satia

    1
  • Eric Paul
    Actions pour les commentaires Permalien

    We have a similar need.  Our current need is that customers have certain requests or requirements that are unique to them in how we support them.  For example, when we test in their instance we have to test with a certain population, etc.  These unique requirements are very difficult to manage and are easily missed when in a notes field on the organization, but if we could have the internal note put this information right in front of our agents it would greatly improve our ability to support effectively and accurately according to our customers requirements, thus improving customer satisfaction and reducing escalations and angry calls to our customer managers.

    1
  • Gary Jackson
    Actions pour les commentaires Permalien

    +1 on this!  Would love to be able to add an internal note depending on the "Organization" name.

    1
  • Aaron O.
    Actions pour les commentaires Permalien

    This would be a great feature, I sent out automated message to customers to help keep tickets moving that have been in pending status at 2 and on the 4th  day. I would like to make a note in the case letting the agent know that the system performed a custom action so they do not duplicate the message and on the 5th day they can resolve the case. 

    Right now there is no way for the agent to know in the case that the system performed any action. 

    1
  • John L.
    Actions pour les commentaires Permalien

    I would also like to have this feature within Zendesk.  We send automated followups every few days and it would be nice to be able to track them in the ticket (date/time sent) with an internal only update.  We also have other automatic updates that happen as well and again it would be great to be able to have an internal update to the ticket stating "Hey, this automation happened".

    I understand that this could be done via a manual update to the ticket, but doesn't that kind of defeat the purpose of an automation altogether?

    1
  • Graeme Carmichael
    Actions pour les commentaires Permalien

    David

    Under Settings>Extensions, it looks like you have selected an HTTP target. The article uses a URL target.

    I should say that these techniques to update tickets can be very useful but are discouraged by Zendesk. They can create race conditions that may lead to problems.

    Hope that helps,

    1
  • Debbie Guskin
    Actions pour les commentaires Permalien

    +1

    Similar to Corey, we use automations to re-open tickets. Here's our specific use case:

    We have a "required to solve" ticket field that is not always set by Agents for Pending tickets. When our automations transition a ticket from Pending to Solved after X amount of time we have an automation that checks if the required field is set. If the field isn't set, the automation automatically re-opens the ticket. However, this confuses our agents because there's no actual info in the ticket that explains why it's still open. To them it looks like the customer never replied and no additional action is needed.

    Note - Our use case could potentially be fulfilled by having a "require on ticket pending flow" option, but adding internal notes for automations is a bit of a more robust option that can be used for other use cases as well. Plus the workaround for requiring a field on other ticket update types at https://support.zendesk.com/hc/en-us/articles/227741828-Is-it-possible-to-require-a-field-be-set-before-moving-to-a-status-other-than-Solved- is not ideal.

    1
  • Jon Schlueter
    Actions pour les commentaires Permalien

    +1 for this feature request.

     

    I can't believe it's been 4 years since this thread started and Zendesk still hasn't built this into their product.  Then again, I've seen a request that went on for 10 years and when people started commenting that one of their competitors added the feature, ZD shut down the thread for any new comments.

     

    Zendesk, maybe listen to your paying customers as we have some really great ideas and want to keep using your product.  Otherwise, what's keeping us here?

    1
  • Graeme Carmichael
    Actions pour les commentaires Permalien

    Satia

    While comments cannot be added as part of the built in trigger actions, you can use a target. See Phil's tip here:

    https://support.zendesk.com/hc/en-us/community/posts/203164973-Adding-Comments-via-Triggers-and-Automations

    0
  • Lucie Debouver
    Actions pour les commentaires Permalien

    Hello!

     

    We also have a similar request. Right now, we use automations to send agents an email as a reminder that a ticket has been untouched for a certain amount of time and that action is required. Ideally, the support agent does not have to check their email to stay on top of their Zendesk queues. An internal note would cause a Zendesk app notification to go out. This is the main reason why this would be helpful for us. 

     

    Thanks!

    0
  • Vijayendra
    Actions pour les commentaires Permalien

    Any update on this? I would like the agents not to miss out any important information for the client

    0
  • Ricardo Camarena
    Actions pour les commentaires Permalien

    We are also looking for this functionality. Would love to hear if and when this would be implemented

    0
  • Patrick Harland-Lee
    Actions pour les commentaires Permalien

    +1 for this, we need a way to notify the agent that there's something about the organization that separates the workflow of all tickets coming in from them compared to other organizations.

    Though I wouldn't mind if there was some other way to do this (say, highlighting the Organization button in the top-left of the ticket).

    I would prefer this wasn't an app, because often our agents will hide the apps bar because they work on laptops and it takes up too much screen real estate.

    0
  • Bruno Roy Contancin
    Actions pour les commentaires Permalien

    +1 Same need. Thank you.

    0
  • Rick
    Actions pour les commentaires Permalien

    Same need here

    0
  • Chris Ryan
    Actions pour les commentaires Permalien

    The comments from Zendesk staff about this feature request are pretty hard to believe! 

    "No plans to support this feature" , etc.  

    Clearly a feature to allow actions to update an internal comment as a part of a trigger is in demand based on the existence of multiple threads with users scrambling to configure their own setup through the API as well as requesting this feature. 

    What is even more interesting is some of these threads have been around for a long time with inter-linking between mostly dead-end, unhelpful threads that pertain to this issue. 

    Please Zendesk help support the needs of your clients by adding this feature formally and rolling it our to our accounts.  

    0
  • Heather Rommel
    Actions pour les commentaires Permalien

    We wish we could do this natively but found the Target workaround very helpful as Graeme mentioned above:

    https://support.zendesk.com/hc/en-us/community/posts/203164973-Adding-Comments-via-Triggers-and-Automations 

    0
  • Laura
    Actions pour les commentaires Permalien

    +1 for this feature.  Thanks!

    0
  • Graeme Carmichael
    Actions pour les commentaires Permalien

    Aaron

    Just in case you are not aware. When looking at a ticket, changing the drop down from 'Conversation' to 'Events' will display all the actions taken on a ticket including triggers and automations.

    This allows Agents to check for system performed actions.

    But I totally agree that allowing an internal comment would allow greater visibility to these important actions.

    0
  • Aaron O.
    Actions pour les commentaires Permalien

    Thanks Graeme that is a good workaround but with other trigger and events that can get cumbersome. 

    0
  • Maurits Vos
    Actions pour les commentaires Permalien

    Hi,

    Just stepping in here.

     

    Our use case for this feature would be that we have different SOP's for some customers. We ship spare parts internationally and sometimes we need to make sure that certain documents are prepared for customs purposes or that there is a specific setting in the order that needs to be taken into account before the order is submitted in the system. Forgetting to do so may have financial implications for our/the customers' business 

     

    We do take notes in the user/organization profile and use the "user date" app to remind our agents, though an internal comment or similar feature would be a better safety measure in our case.

    0
  • Actions pour les commentaires Permalien

    Thanks for the details, Maurits. 

    0
  • Håkon Kippernes
    Actions pour les commentaires Permalien

    We have a case where the data from users in the ticket forms are editable by agents. Since we only have 8-10 employees most of us are admins for convenience. We therefore need a copy of the ticket fields added as text in the ticket for documentation purposes. A trigger with placeholders that spits out a comment with all the information added in the ticket form is needed for us to use the ticket forms at all for the brand.

     

    0
  • Andrea Brown
    Actions pour les commentaires Permalien

    Our use case is that we share a lot of tickets between our various Zendesk accounts (still using the Hub and Spoke over here), and we need the user's email address to appear in the ticket in the Hub. Because it doesn't come as part of the ticket, we want to have it as an internal comment. In our case, our agents can't help our customers without their email address about 90% of the time - so we'd take the email address any way it comes over, but we definitely need it.

    0
  • Vladan Jovic
    Actions pour les commentaires Permalien

    Huh, my clients really need this pretty basic feature :/ 

    0
  • Jimmy Rufo
    Actions pour les commentaires Permalien

    My Use Case:

    I'm testing the side conversation feature in the Collaboration Add-On.  When I send a side conversation to an escalation resource, I'd like to trigger an internal note to the assignee and/or the ticket group for the ticket in question, for awareness that an escalation happened and what the question was.  A reply back from the side conversation recipient would also ideally create an internal note for ticket continuity and transparency.

    Right now, triggers for email can take place with replies to side conversation, but there doesn't appear to make the comment private.

    0
  • Juz
    Actions pour les commentaires Permalien

    This is a really basic feature. Our support agents need to have all info shown to them straight up in the one screen.

    For emails from some domains, or with particular subject lines, there's a standard set of things that we need to remember or refer to.
    We therefore want tickets from those customers to get a text automatically copied in as a comment into the ticket.

    There is the workaround at https://support.zendesk.com/hc/en-us/community/posts/203164973-Adding-Comments-via-Triggers-and-Automations%C2%A0 which goes most of the way. However the slightly reproving tone from the Community Manager's comment there is not helpful. 

    The explanation of a race condition given above also seems somewhat out of place. Other ticketing systems manage to provide this function, so it's not a far-fetched or computationally impossible feature request.

    0

Vous devez vous connecter pour laisser un commentaire.

Réalisé par Zendesk