Add end-user as CC via Trigger or Automation

452 Kommentare

  • Jeremy Heath
    Aktionen für Kommentare Permalink

    Ok no problem

     

    Ill keep looking. thx

    0
  • Yoram Dagan
    Aktionen für Kommentare Permalink

    @Jeremmy

    I managed to overcome this issue by using forwarding rules.

    I have an operational agent which I use for general actions such as that.

    I schedule the report/dashboard to be set to him and add forwarding rules in this user inbox to forward this report to any end-user.

     

    This also works of forwarding to mailing groups, so if a few people need the same report/dashboard, you can set your forwarding rule to a mailing group.

     

    Hope that helps

    Yoram 

    0
  • Alon Hodir
    Aktionen für Kommentare Permalink

    @Avi Is there an option to send an email to the Cc as soon as the ticket is created?

    Currently, the Cc is email only when there is a respond to the ticket.

    0
  • Kate Lim
    Aktionen für Kommentare Permalink

    Hi @Kristen,

    Would there be any updates regarding this feature?

    - Kate

    0
  • Kristen Mirenda
    Aktionen für Kommentare Permalink

    Hi @Kate, there is no further update at this time. While we're are making progress on some foundational functionality, this feature per se is not currently on the roadmap, and I do not have an estimate of if and when it will be.

    -1
  • Avi Warner
    Aktionen für Kommentare Permalink

    @alon unfortunately not that I can figure out :/ 

    The app works by adding CCs via target as the ticket is created, but by the time your 'Notify Requester of Received Request' trigger, or the internal triggers that notify CCs fire, the CC isn't yet in place. 

    0
  • Brian McGinley
    Aktionen für Kommentare Permalink

    I know there seems to be movement on this feature as recently as last year, but it is so disheartening that this feature request is over 9 years old and still hasn't come to light. My only fear is when you finally do get the option in place it will be at the low low price of $25 per user per month for the rest of our lives...

     

    That all being said, We really could use this feature for all the reasons stated above. I have Organization leaders who want to know all of the tickets their team is submitting and if they could be triggered as a CC, it makes this more fool proof than having to circle back every time. 

    1
  • David Andrews
    Aktionen für Kommentare Permalink

    Brian,

    Avi created that feature. It is a $5 one-time fee. You can get the app here https://www.zendesk.com/apps/support/carbon-copier/

    If you would also like to generate read receipts when your customers open their email, you can get this app: https://www.zendesk.com/apps/support/my-read-receipts/

     

     

    2
  • Brian McGinley
    Aktionen für Kommentare Permalink

    David, Thank you! Purchased it.  

    0
  • John Witt
    Aktionen für Kommentare Permalink

    I'll admit I have not read all the replies, but I came up with a kludge that works and adds CC emails if you have access (not sure what subscription level uses Notify Targets).

    - Go to Admin; Settings; Extensions.

    - Create a new HTTP target.

    - URL: https://trendkitehelp.zendesk.com/api/v2/requests/{{ticket.id}}.json

    - Method: PUT

    - Content Type: JSON

    - Enable basic authentication. I use my username/password (password is hidden) but I have not tried using an API token instead. I don't think admin is needed and though the user access was enough, but it failed without this.

    - Click "Update Target" at bottom right and submit.


    Now create a trigger with your required parameters and for actions choose "Notify Target" using the target you created above. For the JSON add the following:

    {

       "request": {
            "email_ccs": [
                { "user_email": "first@example.com","action": "put"},

                { "user_email": "second@example.com","action": "put"}

               ]
        }
    }

    You can add more CCs, but remember if you have just one to remove that comma.

    I'd recommend you do step-testing first. For example, replace the {{ticket.id}} with a real ID and instead of update use "Test Target" and paste your JSON. Look at the result and make sure the email CC is updated and then check the ticket CC to ensure the API PUT is working. If that works works, "Update Target" and create a Trigger that updates that Ticket, this time with a different email address to ensure the Trigger is running the API PUT. If that works, update the target back to {{ticket.id}} and update your Trigger back to the correct parameters and emails addresses.

    John

    1
  • Brett - Community Manager
    Aktionen für Kommentare Permalink

    Thanks for sharing this alternative John!

    This is great :)

    0
  • Uriel Flores
    Aktionen für Kommentare Permalink

    Any update on this?

    1
  • Christian Henkel
    Aktionen für Kommentare Permalink

    Is there any way to realize an general CC to all send tickets with the essential plan?

    John's alternative seems to be working only with the team plan. The tool of Avi is throwing an error when I try to install: Ressource ist missing. 

    1
  • Gasper Jubani
    Aktionen für Kommentare Permalink

    We also badly need this feature. We use Zendesk for internal support and need to be able to set rules to auto Cc folks based on what email address the ticket was received.

    0
  • Avi Warner
    Aktionen für Kommentare Permalink

    @Christian, that’s right, I’m not sure my app will work on Essential plan. If you were able to purchase, please reach out to me via email and I can help w a refund.

    @Gasper, take a look at my app (Carbon Copier), it should be able to take care of that use case.

    0
  • Rob Wentz
    Aktionen für Kommentare Permalink

    John Witt - 

    Thanks for posting your kludge. I'm trying this and will report back if it works out for us. 

    -Rob

    0
  • 이지훈
    Aktionen für Kommentare Permalink

    I have seen an update to the CC section as follows:
    https://support.zendesk.com/hc/en-us/articles/360002113728-Migrating-to-CCs-and-followers

    However, this update does not include updates to automation or triggers that can include end users in the CC.

    Does Zendesk have an update plan on this?

    0
  • Avi Warner
    Aktionen für Kommentare Permalink

    Quick note, my app (Carbon Copier) does not work with the new Followers feature. I'm working on an updated version compatible with both, but please don't install right now if you have activated Followers. Thanks!

    0
  • Phil Sexton
    Aktionen für Kommentare Permalink

    All I need is to be able to add 2 CC's to an automated email (Macro) to say that they have contacted the wrong department and then close the ticket. The reason that I have to add them in by CC is because they cannot see the ticket details any other way.

    If you have another way for my non agent staff to see tickets for a particular brand, that would also fix my issue.

     

    0
  • Andrew J
    Aktionen für Kommentare Permalink

    Hello Phil, there could be a way to effect what you are after without adding them as CCs. You can send me more detail or contact me on Bizstudio.co.nz, happy to discuss this.

    0
  • Rob Wentz
    Aktionen für Kommentare Permalink

    John Witt - 

    Your steps are easy enough to follow... but it's not seeming to work. I created an HTTP target (called "CC non-agents") using the instructions you provided, then call that target from a trigger that is supposed to add (as a test) my gmail address to the cc list if the word "test" shows up in the subject of the ticket. 

    I've sent some test emails to our zendesk ticket with the work "test" in the subject but my gmail address does not get cc'd 

    I see 0 successful sends on the HTTP target.. I'm curious - what username/password should I be using under Basic Authentication of the HTTP target? I'm using my zendesk login and I'm an admin. 

    If i set the combo box at the bottom to "Test target" then hit "Submit", I'm presented with a window that states "JSON body:" at the top with 1x blank line (nothing in the JSON window).. I hit "Submit again and I get: 

     

    HTTP/1.1 401 Unauthorized

    PUT /api/v2/requests/243.json HTTP/1.1
    Authorization: Basic cm9iQGFzZ2xsYy5jb206MjA4bXRoIQ==
    User-Agent: Zendesk Target
    Content-Type: application/json; charset=utf-8
    Content-Length: 0
    Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
    Accept: */*
    Connection: close
    Host: trendkitehelp.zendesk.com

     

    Under the "Response" tab I see:

    HTTP/1.1 401 Unauthorized
    Date: Fri, 16 Aug 2019 00:06:02 GMT
    Content-Type: application/json; charset=UTF-8
    Content-Length: 37
    Connection: close
    Set-Cookie: __cfduid=dc4293ae219c923d41204f53c950ce2481565913962; expires=Sat, 15-Aug-20 00:06:02 GMT; path=/; domain=.trendkitehelp.zendesk.com; HttpOnly
    WWW-Authenticate: Basic realm="Web Password"
    Strict-Transport-Security: max-age=31536000;
    Cache-Control: no-cache
    X-Zendesk-Origin-Server: app51.pod14.use1.zdsys.com
    X-Request-Id: 506f28f8ad15cf28-IAD
    X-Runtime: 0.049818
    X-Zendesk-Request-Id: 4822acad6dd01b7d2dd0
    Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
    Server: cloudflare
    CF-RAY: 506f28f8ad15cf28-IAD
    {"error":"Couldn't authenticate you"}

    what am I doing wrong here? 

     

    0
  • Andrew J
    Aktionen für Kommentare Permalink

    Zendesk email and password should be correct. You don't have SSO or anything?

    0
  • Rob Wentz
    Aktionen für Kommentare Permalink

    Yes, Zendesk log-in is SSO...isn't it??  Did you mean 24a? 

     

    0
  • Andrew J
    Aktionen für Kommentare Permalink

    I'm not sure that it works with sso. I hadn't even thought of 2FA.

    0
  • Rob Wentz
    Aktionen für Kommentare Permalink

    aren't zendesk login credentials single sign on? Am i misunderstanding you perhaps? 

     

    0
  • Andrew J
    Aktionen für Kommentare Permalink

    Sso normally means you are signing in through another system

    0
  • Rob Wentz
    Aktionen für Kommentare Permalink

    Andrew - got it.. no i'm using just my zendesk credentials, nothing out of the ordinary.. the unique username and password I use to log in to our zendesk system is what I'm filling in under the Basic Authentication section of the HTTP target i've set up per John Witt's kludge described a few posts back 

    0
  • Andrew J
    Aktionen für Kommentare Permalink

    It should be an email - not a username right?

    0
  • Rob Wentz
    Aktionen für Kommentare Permalink

    Hi Andrew, yes that's correct. my login is my email address. 

    0
  • Andrew J
    Aktionen für Kommentare Permalink

    Ok, there may be a setting you need to change. Sorry I am not at my PC to look currently. It's Saturday here 🙂

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

Powered by Zendesk