r/Zendesk • • Nov 04 '24

Zendesk is becoming too expensive for our company

108 Upvotes

My company currently uses Zendesk, and as we’ve grown from just a few users to a couple of dozen, our Zendesk bill has climbed to around $5,000 per month (not including add-ons). At this price point, we’re increasingly tempted to explore alternatives, as switching could potentially save us tens of thousands of dollars annually.

Before committing to a change, though, I’m interested to know if anyone has experience negotiating with Zendesk. I reached out to their support team, but their response was vague, suggesting only that we downgrade to a lower plan, which isn’t an option for us as we'd loose access to some of the features. Any insights on negotiating tactics or strategies that could help us secure a better rate would be greatly appreciated.


r/Zendesk • • Oct 14 '25

General discussion Receiving bunch of unsolicited support tickets from companies using zendesk

96 Upvotes

Hey all,

not sure if this is the right sub. But starting today, I received a bunch of unsolicited support ticket emails in a short amount of time from legitimate services (e.g. Discord, and other big ones). The emails are all legit and are sent using Zendesk (all mails have same structure and a few services directly like to their hosted instances on zendesk.com)

Thing is, I have no account or business with those services and I don't really want to get spammed by ticket updates (or any more unsolicited tickets).

Is there a way for me to put a stop to this without having to contact each service? I could also just filter and mark all Zendesk tickets as spam, but I'd prefer not to do that either.


r/Zendesk • • Feb 04 '26

Question: help center MORE and new spam

69 Upvotes

this is ridiculous. a few weeks ago it was a bunch of tickets now its a bunch of accounts. theres 100 more in my spam and trash from my previous filters for this crap.

Edit: spam box hit 1k 🫩🫩


r/Zendesk • • Jan 19 '26

General discussion Email spam non stop coming

39 Upvotes

Email spam non stop coming in, I’ve recieved 100+ in past 10 minutes. Is there no solution at all? This is so frustrating


r/Zendesk • • Feb 04 '26

Question: help center Stop the Spam mail

37 Upvotes

Fix your servers and block the spammers homies, 500+ in one hour is crazy work


r/Zendesk • • Feb 07 '26

Question: help center day three of spam has started!!!!!!!

36 Upvotes

this is now the THIRD separate day of spam over the last month. DO SOMETHING


r/Zendesk • • Oct 17 '25

Question: data privacy & protection We need a real explanation from Zendesk about what happened with the Discord breach and recent ticket spamming

35 Upvotes

Full disclosure: I am an admin in one of the Zendesk accounts that was used to create spam tickets. We have "band aided" the issue ourselves per the recommendation on Zendesk support.

I've burned through many hours since Wednesday morning dealing with the fall out of this with our internal team and even some of the unsuspecting victims who received the spam tickets. Some observations/questions:

  • In my initial calls to Zendesk support they seemed somewhat clueless as to what was happening and how widespread.

  • In our case, ALL of the spam tickets that were created were related to discord accounts, which was easily determined by the subject (warnings about their account)

  • During the discord breach, it is obvious that bad actors discovered vulnerabilities in how Zendesk receives new, unauthenticated tickets, and then exploited that (what else did they discover?)

  • All of the spam tickets we received came through channel "web form", how were they able to overpower the form, bypass CAPTCHA, Cloudflare, etc?

  • Communications seem very vague and treating it like a normal spam event.

Making every customer trying to get support, register for an account to the support center, is not a customer friendly approach, which is what Zendesk is recommending. I would like to see an explanation of the event and what actions are being taken.


r/Zendesk • • Jan 13 '24

Is it crazy if my employer wants a team of 3 agents to clear 11,000 email tickets in a week?

35 Upvotes

Is it crazy if my employer wants a team of 3 agents to clear 11,000 email tickets in a week (spam, refunds, cancellations, etc)? I feel like I'm getting overemployed with the amount of tickets they are asking us to do. The owner also feels passive-aggressive with her threats that if we don't meet expectations we can get fired and refuse to hire more people to help.

Also, the number of 11,000 tickets increases every day. It started at 10,500 then the next day it was 11,000 and so on. (This is with 400+ tickets that each agent does every day)

I would love to hear your opinion on how many emails an agent normally responds per day.


r/Zendesk • • Jan 09 '21

Parler Uses ZenDesk

35 Upvotes

h7@n6WTK*hZ


r/Zendesk • • Jun 28 '22

I recently passed my Certified Zendesk Support Admin exam and I wrote a guide with everything you need to know to pass on your first attempt.

34 Upvotes

Hi all,

I recently passed my Certified Zendesk Support Admin exam and I wrote a guide with everything you need to know to pass on your first attempt.

I hope you find this useful!

https://www.salto.io/blog/zendesk-configuration/how-to-pass-the-certified-zendesk-support-admin-exam-the-first-time 

If you have any feedback on how to make this article better, please let me know!


r/Zendesk • • Feb 08 '26

General discussion I’m done: all Zendesk mail blocked. Actively reporting to mail spam block lists

29 Upvotes

Enough.

This is the most irresponsible company I have seen.

How dare you state you have no security issues?

This is insane and embarrassing.

I am blocking all email from Zendesk and I will spend the effort of getting blocklists involved. Zendesk has proven it is not a professional company and it does mot deserve to have their email reach inboxes, let alone spam folders.


r/Zendesk • • Apr 19 '23

Why is Zendesk Help Desk So Terrible?

29 Upvotes

For a paid solution in the customer service space, this is very ironic that zendesks own support system is so terrible.

I can understand if the service level is dependent on the account size, but why is it just not made clear to the customers? Why do account managers ghost customers and not respond? Do they not have any repercussions for not handling customers properly? I would be surprised if that is indeed the case.

I have been trying to set up subscription changes for my company’s account. We have been using zendesk for over seven years. I cannot get my account manager to respond earlier than ten days after I send an email. He has not gotten back to any of us for over three weeks now!

We have had an email thread going on since the first week of February, and our request is not processed, yet we do not even know if it is being processed.

This is highly frustrating, with no solution in sight!


r/Zendesk • • Apr 29 '22

I really dislike Zendesk

28 Upvotes

It makes it all so hard. Getting reports is freaking difficult and many times it doesn't even show accurate, reliable data.

You can't integrate it with Slack directly (which it should at this point) to get notifications of important stuff. Even if I use Zapier, I can't get notifications in Slack of internal comments in Zendesk.

I can't delete tags I don't need so it messes up my reporting.

The whole UI is really non-user friendly. I wonder why they are stuck with such an terrible UI and haven't improved it in years.

They also messed up the Reporting and Admin sections. Yiu used to be able to look for macros, triggers and other and it would only open an tab within Zendesk. It now opens a whole new tab in your browser, making it all so much noisy.


r/Zendesk • • Jan 19 '26

General discussion How do I stop receiving spam ticket emails?

27 Upvotes

I'm drowning in emails, new ones every few minutes for multiple days.

Who do I contact to make it stop? Can Zendesk customer support block my email address from being used to create tickets, or provide some other solution?

I found this article, but the only advice for non-customers is "ignoring or deleting any suspicious email", which is obviously unacceptable...


r/Zendesk • • Jan 19 '26

Question: help center How to block Zendesk spam when Gmail filters fail?

24 Upvotes

I've been getting constant email spam from Zendesk for the past week. I've tried marking them as spam and creating custom filters targeting the "zendesk" keyword, but nothing seems to work. Gmail's filters are frustratingly limited—they can't filter by custom email headers, so if "zendesk" doesn't appear in the email body itself, I'm stuck manually sending each one to spam. How are other people dealing with this? https://i.imgur.com/GRVxT7l.png


r/Zendesk • • Mar 28 '25

Introducing: Dark mode

24 Upvotes

🌙 You asked for it, and we listened: Dark mode is officially here for Zendesk.

👀 Agents can now easily toggle between light and dark modes, choosing the option that best suits their eyes and allowing them to work in style and focus more effectively. Activate dark mode and enhance the employee experience for all agents.


r/Zendesk • • Jan 19 '26

General discussion Unsolicited email spam was never actually fixed

23 Upvotes

This required proper zendesk action across all zendesk clients. It's not a matter of asking individual clients to fix their settings; something should change at a higher level.

Previously:

https://support.zendesk.com/hc/en-us/articles/9833274501786-Important-notice-about-recent-spam-emails-via-Zendesk

https://www.reddit.com/r/Zendesk/comments/1o6u1ws/comment/nkjo1ja/?context=3

Yesterday:

Happened again with over 500 emails arriving in the spam of *several minutes*.

https://x.com/i/status/2012784392607821950

https://x.com/nickoates_/status/2012761746503606379

cc u/brettfromzd

https://imgur.com/a/28hMEzv


r/Zendesk • • Oct 13 '24

1 bug, $50,000+ in bounties, how Zendesk intentionally left a backdoor in hundreds of Fortune 500 companies

Thumbnail
gist.github.com
23 Upvotes

r/Zendesk • • Mar 12 '26

General discussion Zendesk's forced anonymous verification rollout is going to break workflows for a lot of businesses

22 Upvotes

Is anyone else dealing with the fallout from Zendesk's new anonymous request verification rollout?

For those who haven't seen it yet — Zendesk is now requiring email verification for anyone who submits a help center request without being logged in. If the user doesn't verify, the ticket goes straight to a suspended queue. No automations fire, no SLAs kick in, no AI agent responses. It just sits there until an agent manually recovers it.

I work at a B2C fintech company. Our customers don't sign in to Zendesk to contact us — they never have, and there's no reason for them to. We rely heavily on our help center form for both support requests and collecting secure documents from users. This change impacts us in three ways:

  1. Ticket loss risk. Users who don't complete the email verification step simply won't have their ticket created. For a financial services company, a lost ticket isn't just a bad experience — it's a potential compliance issue.

  2. Our AI agent is now useless. Zendesk confirmed that AI agents will no longer respond to users who aren't logged in. We're paying thousands a year for this feature and it's about to stop working for virtually all of our users. No warning, no adjustment to pricing, nothing.

  3. The timeline is absurd. This was announced and started rolling out almost immediately. We have days to rethink processes that have been in place for years. And for anyone whose Zendesk renewal falls right after the announcement — good luck renegotiating when you just auto-renewed for a year of features that no longer work as expected.

The community response on the Zendesk forums has been overwhelmingly negative. Customers across healthcare, education, government, and financial services are all raising the same concerns. Zendesk's response so far has been to offer an extension to May 7 and point people to help articles about managing suspended tickets.

No opt-out. No consultation. No acknowledgment that this breaks real workflows for real businesses.

Is anyone exploring alternatives? Has anyone found a workaround that actually works? Would love to hear how others are handling this.


r/Zendesk • • Feb 25 '21

Good morning!

Post image
22 Upvotes

r/Zendesk • • Apr 23 '19

Announcement Calling all startups - get the Zendesk Suite free, for a full year!

22 Upvotes

Qualifying startups can get a year of the Zendesk Suite for free. There are only a few conditions that apply:

  • You must be a new customer of Zendesk

  • Your company must be Series B or below in funding

  • Your company must have fewer than 100 employees

Ready to get started? Visit the Zendesk for Startups page, fill out the application form, and a member of our team will be in touch shortly.


r/Zendesk • • Jul 05 '24

Here is a script to download all Zendesk tickets and attachments, and make them viewable offline in a browser.

21 Upvotes

I (well mostly ChatGPT) made a script that will download and index all your Zendesk tickets and generate an HTML file for offline viewing, using Zendesk's API.

A customer wanted to avoid upgrading their Zendesk plan, and was wondering if they could just download all their ticket data in case they would need it in the future. I did some playing around with ChatGPT and came up with this.

What you need to know to make this work:

  1. Install wkhtmltopdf. This is used to generate PDFs of the tickets for easy printing. This can be disabled in the script if you wish.

  2. Be sure to set the variables at the beginning of the script, especially "$subomain", "$email", and "$api_token". Optionally, you can change "$ticketsFolder" to save the data somewhere else. By default it will save everything wherever the script is located. You can also set "generatepdfs" to "$false" if you wish (makes the process a bit quicker), and if you installed "wkhtmltopdf" in a non-default location, be sure to update this as well.

  3. Depending on the number of tickets, this may take a long time to run (hours). When it is finished, launch the index.html file by creating a batch file as follows. This is necessary because, by default, browsers do not allow access to local files, so the tickets will not load correctly otherwise.

             start msedge --allow-file-access-from-files "%~dp0index.html"
  4. Feel free to make your own tweaks and improvements. At this point, it just downloads everything, with no way to filter by date or anything. I'm sure it's possible to add this functionality, but I didn't take the time to do it because my customer doesn't care about that. If you have web dev experience, it should also be pretty easy to save the downloaded data to a web server for multiple people to use.

Anyway, here's the script. Pasting it directly from Reddit might format it wrong, so download it from GitHub if possible.

https://github.com/happy-harry/ZendeskDownload

            # Define Zendesk credentials and API token
            $ticketsFolder = ".\" # By default will download to the current folder.
            $subdomain = "subdomain"
            $email = "[email protected]"
            $api_token = "api_token_goes_here"
            $generatepdfs = $true
            $wkhtmltopdfPath = "C:\Program Files\wkhtmltopdf\bin\wkhtmltopdf.exe"
            $base64AuthInfo = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes("$email/token:$api_token"))

            # Function to download a file
            function Download-File {
                param (
                    [string]$url,
                    [string]$output
                )
                $progresspreference = 'SilentlyContinue'
                Invoke-WebRequest -Uri $url -OutFile $output -UseBasicParsing
            }

            # Create a folder for tickets
            if (-Not (Test-Path -Path $ticketsFolder)) {
                New-Item -Path $ticketsFolder -ItemType Directory
            }

            # Function to process tickets
            function Process-Tickets {
                param (
                    [array]$tickets
                )

                foreach ($ticket in $tickets) {
                    Write-Host "Processing Ticket ID: $($ticket.id)"

                    # Create a folder for each ticket
                    $ticketFolder = Join-Path -Path $ticketsFolder -ChildPath "Ticket_$($ticket.id)"
                    if (-Not (Test-Path -Path $ticketFolder)) {
                        New-Item -Path $ticketFolder -ItemType Directory
                    }

                    # Save ticket information
                    $ticketFile = Join-Path -Path $ticketFolder -ChildPath "ticket_$($ticket.id).json"
                    $ticket | ConvertTo-Json -depth 10 | Out-File -FilePath $ticketFile

                    # Fetch comments for the ticket
                    $commentsUrl = "https://$subdomain.zendesk.com/api/v2/tickets/$($ticket.id)/comments.json"
                    $commentsResponse = Invoke-RestMethod -Uri $commentsUrl -Headers @{Authorization=("Basic {0}" -f $base64AuthInfo)}
                    $comments = $commentsResponse.comments

                    $htmlContent = "<html><body>"
                    $htmlContent += "<h1>Ticket ID: $($ticket.id)</h1>"
                    $htmlContent += "<p><strong>Subject:</strong> $($ticket.subject)</p>"
                    $htmlContent += "<p><strong>Description:</strong> $($ticket.description)</p>"

                    foreach ($comment in $comments) {
                        # Save comment information
                        $commentFile = Join-Path -Path $ticketFolder -ChildPath "comment_$($comment.id).json"
                        $comment | ConvertTo-Json -depth 10 | Out-File -FilePath $commentFile

                        # Add comment to HTML content
                        $htmlContent += "<hr><p><strong>Comment ID:</strong> $($comment.id)</p>"
                        $htmlContent += "<p><strong>Author:</strong> $($comment.author_id)</p>"
                        $htmlContent += "<p><strong>Created At:</strong> $($comment.created_at)</p>"
                        $htmlContent += "<p>$($comment.body)</p>"

                        # Download attachments
                        foreach ($attachment in $comment.attachments) {
                            $attachmentUrl = $attachment.content_url
                            $attachmentPath = Join-Path -Path $ticketFolder -ChildPath $attachment.file_name
                            Download-File -url $attachmentUrl -output $attachmentPath
                            $htmlContent += "<p><a href='$attachment.file_name'>Download Attachment: $($attachment.file_name)</a></p>"
                        }
                    }

                    $htmlContent += "</body></html>"
            if ($generatepdfs -eq $true)
            {
                    # Save HTML content to a file
                    $htmlFile = Join-Path -Path $ticketFolder -ChildPath "ticket_$($ticket.id).html"
                    $htmlContent | Out-File -FilePath $htmlFile

                    # Convert HTML to PDF using wkhtmltopdf
                    $pdfFile = Join-Path -Path $ticketFolder -ChildPath "ticket_$($ticket.id).pdf"
                    
                    
                        Start-Process -FilePath $wkhtmltopdfPath -ArgumentList "$htmlFile $pdfFile" -NoNewWindow -Wait
                    
                }
                    Write-Host "Finished Processing Ticket ID: $($ticket.id)"
                }

            }
            # Initial API endpoint
            $zendeskApiUrl = "https://$subdomain.zendesk.com/api/v2/tickets.json"

            do {
                # Fetch tickets
                $response = Invoke-RestMethod -Uri $zendeskApiUrl -Headers @{Authorization=("Basic {0}" -f $base64AuthInfo)}
                $tickets = $response.tickets

                # Process the fetched tickets
                Process-Tickets -tickets $tickets

                # Update the API URL to the next page
                $zendeskApiUrl = $response.next_page

            } while ($zendeskApiUrl -ne $null)

            Write-Host "Tickets and attachments have been successfully downloaded and organized."



            # HTML template for the index file
            $htmlHeader = @"
            <html>
            <head>
                <title>Zendesk Tickets</title>
                <style>
                    body { font-family: Arial, sans-serif; }
                    .ticket { margin-bottom: 10px; border: 1px solid #ccc; padding: 10px; }
                    .ticket h2 { margin: 0; cursor: pointer; }
                    .ticket-details { display: none; padding: 10px; border-top: 1px solid #ccc; }
                    .attachment { margin: 5px 0; }
                    #search { margin-bottom: 20px; }
                    .paperclip { color: #000; margin-left: 5px; }
                    html { overflow-y: scroll; }
                </style>
                <script>
                    function loadTicketDetails(ticketId) {
                        var detailsDiv = document.getElementById('details-' + ticketId);
                        if (detailsDiv.innerHTML === '') {
                            fetch('Ticket_' + ticketId + '/ticket_' + ticketId + '.html')
                            .then(response => response.text())
                            .then(data => detailsDiv.innerHTML = data)
                            .catch(error => console.error('Error loading ticket details:', error));
                        }
                        toggleDetails(ticketId);
                    }

                    function toggleDetails(ticketId) {
                        var details = document.getElementById('details-' + ticketId);
                        if (details.style.display === 'none' || details.style.display === '') {
                            details.style.display = 'block';
                        } else {
                            details.style.display = 'none';
                        }
                    }

                    function searchTickets() {
                        var input, filter, tickets, h2, i, txtValue;
                        input = document.getElementById('search');
                        filter = input.value.toLowerCase();
                        tickets = document.getElementsByClassName('ticket');
                        var filterAttachment = document.getElementById('filterAttachment').checked;

                        for (i = 0; i < tickets.length; i++) {
                            h2 = tickets[i].getElementsByTagName('h2')[0];
                            txtValue = h2.textContent || h2.innerText;
                    
                            // Check if the ticket contains the filter text
                            var matchesSearch = txtValue.toLowerCase().indexOf(filter) > -1;

                            // Check if the ticket contains the 📎 character
                            var hasAttachment = tickets[i].querySelector('.paperclip') !== null;

                            // Apply filter logic
                            if (matchesSearch && (!filterAttachment || (filterAttachment && hasAttachment))) {
                                tickets[i].style.display = '';
                            } else {
                                tickets[i].style.display = 'none';
                    }
                }
            }

                </script>
            </head>
            <body>
                <h1>Zendesk Tickets</h1>
                <input type="text" id="search" onkeyup="searchTickets()" placeholder="Search for tickets...">
                <input type="checkbox" id="filterAttachment" onchange="searchTickets()" />
                <label for="filterAttachment">Filter by Attachment 📎</label>

            "@

            $htmlFooter = @"
            </body>
            </html>
            "@

            # Initialize the HTML content with the header
            $htmlContent = $htmlHeader

            # Function to read JSON files and convert to objects
            function Read-JsonFile {
                param (
                    [string]$filePath
                )
                Get-Content -Path $filePath | Out-String | ConvertFrom-Json
            }

            # Enumerate tickets and sort numerically by ticket ID
            $ticketFolders = Get-ChildItem -Path $ticketsFolder -Directory | Sort-Object { [int]($_.Name -replace 'Ticket_', '') }

            # Total number of tickets to process
            $totalTickets = $ticketFolders.Count
            $currentTicket = 0

            # Generate HTML content with progress bar
            foreach ($ticketFolder in $ticketFolders) {
                $ticketId = $ticketFolder.Name -replace 'Ticket_', ''
                $ticketFile = Join-Path -Path $ticketFolder.FullName -ChildPath "ticket_$ticketId.json"
                $ticket = Read-JsonFile -filePath $ticketFile

                # Check for attachments
                $hasAttachments = $false
                foreach ($commentFile in Get-ChildItem -Path $ticketFolder.FullName -Filter "comment_*.json") {
                    $comment = Read-JsonFile -filePath $commentFile.FullName
                    if ($comment.attachments.Count -gt 0) {
                        $hasAttachments = $true
                        break
                    }
                }

                # Add paperclip symbol if there are attachments
                $paperclip = ""
                if ($hasAttachments) {
                    $paperclip = "<span class='paperclip'>&#128206;</span>"  # Unicode for paperclip symbol
                }

                # Add ticket link
                $htmlContent += "<div class='ticket'>"
                $htmlContent += "<h2 onclick='loadTicketDetails($($ticket.id))'>Ticket ID: $($ticket.id) - $($ticket.subject) $paperclip</h2>"
                $htmlContent += "<div class='ticket-details' id='details-$($ticket.id)'></div>"
                $htmlContent += "</div>"

                # Generate individual ticket HTML file
                $ticketHtmlContent = "<div>"
                $ticketHtmlContent += "<p><strong>Description:</strong> $($ticket.description)</p>"

                foreach ($commentFile in Get-ChildItem -Path $ticketFolder.FullName -Filter "comment_*.json") {
                    $comment = Read-JsonFile -filePath $commentFile.FullName
                    $ticketHtmlContent += "<hr><p><strong>Comment ID:</strong> $($comment.id)</p>"
                    $ticketHtmlContent += "<p><strong>Author:</strong> $($comment.author_id)</p>"
                    $ticketHtmlContent += "<p><strong>Created At:</strong> $($comment.created_at)</p>"
                    $ticketHtmlContent += "<p>$($comment.body)</p>"

                    # Add attachments links
                    foreach ($attachment in $comment.attachments) {
                        $attachmentPath = Join-Path -Path Ticket_$($ticket.id)/ -ChildPath $attachment.file_name
                        $ticketHtmlContent += "<p class='attachment'><a href='$attachmentPath'>Download Attachment: $($attachment.file_name)</a></p>"
                    }
                }

                # Add PDF link to individual ticket HTML content
                if ($generatepdfs -eq $true)
                {
                $pdfLink = "<p><a href='Ticket_$($ticket.id)/ticket_$($ticket.id).pdf'>Click here to view printable PDF</a></p>"
                $ticketHtmlContent += $pdfLink
                $ticketHtmlContent += "</div>"
                }

                # Save individual ticket HTML file with UTF-8 encoding
                $ticketHtmlFilePath = Join-Path -Path $ticketFolder.FullName -ChildPath "ticket_$ticketId.html"
                [System.IO.File]::WriteAllText($ticketHtmlFilePath, $ticketHtmlContent, [System.Text.Encoding]::UTF8)
                
                # Update the progress bar
                $currentTicket++
                $percentComplete = [math]::Round(($currentTicket / $totalTickets) * 100)
                Write-Progress -Activity "Generating HTML" -Status "Processing ticket $currentTicket of $totalTickets" -PercentComplete $percentComplete
            }

            # Close the HTML content with the footer
            $htmlContent += $htmlFooter

            # Define the output HTML file path
            $htmlFilePath = Join-Path -Path $ticketsFolder -ChildPath "index.html"

            # Save the HTML content to the file with UTF-8 encoding
            [System.IO.File]::WriteAllText($htmlFilePath, $htmlContent, [System.Text.Encoding]::UTF8)

            Write-Host "HTML index has been successfully generated at $htmlFilePath"

r/Zendesk • • Apr 22 '26

Big update: Zendesk Academy has a fresh new home 🚀

20 Upvotes

Hey folks! 
Zendesk Academy just got a big upgrade, and we’re pretty excited about it.
We’ve been listening to your feedback and pulled everything into one updated learning hub at academy.zendesk.com, with:

  • new courses

  • refreshed learning paths

  • more interactive learning experiences

  • 10+ hours of AI content

  • and 20+ new learning experiences launched over the past year

If you’ve been learning through training.zendesk.com, don’t worry, your progress carries over, so you won’t lose your place.
We’re just getting started — in the coming weeks, we’ll be launching new updates, including rolling this out across languages, more ways for people to learn and level up, and a new way to show off progress along the way. If you’re curious, go take a look and see what’s new:
academy.zendesk.com


r/Zendesk • • Apr 24 '24

How to optimize your help docs for the new AI support chatbots

20 Upvotes

Given most of the big customer support live chat providers (Zendesk included) are adding AI chatbots to their products, I thought it would help to share a few tips on how you can optimize your help documentation/center to ensure your AI gives users the best answers.

(generally speaking, it will also mean it is easier to access for people too!)

AI isn't a magic pill, it really is a case of garbage in, garbage out, so it's worth spending the time to think about how to address these points in your docs if you want to get the best bang for your buck when working with AI.

(For context, I have been working every day on this kind of thing for the last 18 months so have gotten to learn quite a few ins and outs over that time that I thought might be worth sharing!)

On with the tips:

  1. Be clear, concise and unambiguous

Each article or question you answer should be short, to the point, and use language specific to the issue being addressed.

Think overly specific rather than general. Spell things out as if you are writing to someone who has never seen or heard of your product or business or understands what it does. Don’t worry too much about repetition across articles.

It is worth pointing out here too that having less “personality” or “brand” to your help content will likely be a good thing for the AI’s understanding (you have lots of other opportunities across your product to get this across!).

2. Think about formatting

You can’t go overboard when formatting for AI.

Think of it as ‘sign-posting’. Use lots of headings and subheadings to identify each section of the content or guide and use bullets or numbering to show the steps of a process.

This type of formatting helps the AI to ‘read’ and interpret what each piece of help content is about without it having to ‘read’ more information around it.

Also, make sure you use full stops at the end of sentences and bullet points, as otherwise when the text is extracted it will be harder for the AI to determine where sentences and phrases begin and end.

3. Drop the jargon, but think about keywords

AI won’t understand your company jargon or acronyms, but a lot of the time, your users won’t either.

So limit the use of it to improve the likelihood that your AI will understand what you are talking about.

Use a plain English explanation with jargon in brackets afterwards (if you want to educate your users), rather than the other way around.

Think about the words you can use to make it clear what the help article is about for the AI. Think about what a user might search for if they were asking the question.

If you had to summarize the help article in 2-3 words, what would they be and are they mentioned several times throughout the article?

4. Take care when using tables and images

Most of the time, the AI won’t read a table as a table, it will just take all the text from it, without knowing which text comes from which column.

So the fewer tables you use, the better, or, if you have to use them, keep them smaller, with 2-3 rows maximum.

The same goes for images, most AI chatbots won’t be able to interpret them, so don’t use them to explain core concepts or show diagrams or screenshots without explaining them in text format in the body of the article.

(Added bonus here - it will only help make your articles more accessible for those with visual impairments).

5. One help article, one topic

The less ‘overlap’ between help articles, the easier it will be for the AI to identify which article it should use to answer the user’s question.

Try not to put articles that cover different parts of the product or business in one article, but do make sure that anything about a specific topic is in one place as it gives the AI more contextual understanding for answering questions.

6. Answer in full, using context

When writing out help articles and FAQs, they are often framed as questions with a “yes” or “no” response. AI needs more context than this, so instead of just saying “yes” update answers to be “yes, it can <whatever your question was>”.

This will make it far easier for the AI to find these answers when searching.

In addition, if an answer or help article is a little longer, it helps if you can provide some more context or background to the problem the article solves or question it is answering. This will help the AI discover it, but also give it more background when it comes to actually answering the question.

7. Avoid conflicting or contradictory information

You shouldn’t have outdated information in your help content. This is especially important if you use AI as the chatbot finds it nearly impossible to distinguish between the old and the new content and therefore can give outdated responses.

The same principle applies if your business has multiple versions or products.

Unless each article specifically calls out which version or product it relates to, the AI will have no broader knowledge to draw from to determine the correct answer.

So make sure, when giving context, if there are product or version-specific differences, that you call these out explicitly in your help content.

If you find these useful let me know and I can share a blog post with examples and a bit more background with you too.

Feel free to ask any questions too, no AI questions are too dumb, we're all learning right now!

Read more here.


r/Zendesk • • Oct 23 '25

Cool tips & tricks Triggering Comments - Available At Long Last!

19 Upvotes

Today I learned that Zendesk quietly added a new feature that lets you use triggers to automatically add both public comments and internal notes to tickets.

If you haven’t seen it yet, this is a fairly recent addition to the trigger actions menu. In the past, you could update fields, assign groups, or send notifications, but you couldn’t have Zendesk itself write a comment into the ticket. Now you can, and it opens up some interesting possibilities.

How it works
In Admin Center under Objects and rules > Business rules > Triggers, you’ll see two new actions:

  • Ticket: Add comment – posts a public reply visible to the requester and agents

  • Ticket: Add internal note – posts a private note visible only to agents

A few practical uses

  • Add a pre-written internal reminder when a ticket includes certain keywords like “refund” or “outage”

  • Automatically tag, assign, and leave a note for follow-up when tickets meet specific conditions

  • Pull data into the comment therad from your custom ticket fields using {{ticket.placeholders}}

Good to know

  • Internal notes are posted by the system user

  • Public comments appear from the assignee, or from the system user if unassigned

  • Light agents can’t add public comments, so triggers won’t fire that action for them

  • Only one public comment and one internal note can be added per ticket event, even if multiple triggers meet the conditions

Why it’s a big deal
This might sound small, but it fills a long-standing gap. You can now use Zendesk’s built-in automation to communicate with both customers and agents in a more dynamic way, without relying on macros or third-party apps. It’s especially useful for standardizing responses and reinforcing internal processes.

Here’s the full article from Zendesk Support explaining how to set it up:
Automatically adding comments and notes to tickets using triggers