<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tomás Baidal on Medium]]></title>
        <description><![CDATA[Stories by Tomás Baidal on Medium]]></description>
        <link>https://medium.com/@tbs89berlin?source=rss-a8b1dd4394bf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*DYoPHlpaX1t_T-pP</url>
            <title>Stories by Tomás Baidal on Medium</title>
            <link>https://medium.com/@tbs89berlin?source=rss-a8b1dd4394bf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:19:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tbs89berlin/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Balanced Workload: Proportional Ticket Distribution in Zendesk Explained]]></title>
            <link>https://medium.com/@tbs89berlin/balanced-workload-proportional-ticket-distribution-in-zendesk-explained-dbde81f7a16e?source=rss-a8b1dd4394bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbde81f7a16e</guid>
            <category><![CDATA[zendesk]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[crm]]></category>
            <dc:creator><![CDATA[Tomás Baidal]]></dc:creator>
            <pubDate>Fri, 07 Jul 2023 14:24:18 GMT</pubDate>
            <atom:updated>2023-07-12T10:52:48.408Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-SingCf-uCU5AsbLi99c1A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@marcinjozwiak?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Marcin Jozwiak</a> on <a href="https://unsplash.com/s/photos/distribution?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><ol><li><strong>Introduction</strong></li></ol><p>As organisations grow, customer support becomes increasingly critical and complex. One tool that helps manage this challenge is Zendesk, a robust customer service platform designed to streamline ticketing and help desk operations. Within Zendesk, ticket distribution is crucial. By ensuring tickets are distributed proportionally, you can manage workload effectively and boost productivity. This article will guide you through using Liquid Code and triggers to achieve a more balanced ticket distribution.</p><p><strong>2. But What Do You Mean by ‘Proportional Ticket Distribution’?</strong></p><p>When we talk about “proportional ticket distribution” in Zendesk, we’re discussing how tickets are divided among different support teams based on predefined proportions. <strong>The purpose of this method is to ensure that no single team is overwhelmed with tickets while others have significantly fewer, thereby creating a balanced workload</strong>.</p><p>Consider this scenario: Suppose your support operation consists of three teams — Team A, Team B, and Team C. You’ve analysed the strengths, specialties, and capacities of each team, and you’ve decided that you want Team A to handle 50% of incoming tickets, Team B to manage 30%, and Team C to take on the remaining 20%.</p><p>With the traditional first-come-first-serve ticket assignment method, you can’t guarantee this distribution. However, by using Liquid code in Zendesk triggers to implement proportional distribution, you can customise your ticket assignment process to adhere to these proportions.</p><p>This means that for every <strong>100 tickets</strong> that come into your support queue, 50 would be automatically assigned to Team A, 30 to Team B, and 20 to Team C, <strong>ensuring a proportional and balanced distribution according to your team’s capacities and capabilities.</strong></p><p>That’s the power and flexibility of proportional ticket distribution in Zendesk — a tailored approach to ticket assignment that allows for more efficient and effective support operations.</p><p><strong>3. Understanding Liquid Code and Triggers in Zendesk</strong></p><p>Good news, you don’t need to be a programming wizard. Well, just a bit of code savvy, but we’ve got plenty of examples lined up that you can follow and adapt to your needs.</p><p><a href="https://shopify.github.io/liquid/">Liquid code</a>, a flexible, open-source template language, allows dynamic content loading on web pages. It doesn’t need to be installed, as <strong>Zendesk natively recognises it.</strong> For our purposes, we’ll use Liquid code to distribute tickets proportionally among different support teams. While it involves some coding, the examples provided will make it easier for you to adapt Liquid code to fit your needs.</p><p>Triggers in Zendesk are <strong>business rules that run immediately after tickets are created or updated</strong>. We will use triggers to automate the activation of a webhook, effectively carrying out our proportional ticket distribution. By merging the power of Liquid code and triggers, you’ll achieve a balanced, efficient ticket assignment that aligns with your business’s unique requirements.</p><p><strong>4. Step-by-Step Guide: Setting Up Your Environment</strong></p><p><strong>STEP 1 — Creating a Custom Field in Zendesk</strong></p><p>The first step towards implementing proportional ticket distribution is creating a <strong>dropdown custom field</strong>. Follow these steps:</p><p>a. Navigate to Zendesk <em>Admin Centre</em>.</p><p>b. Under ‘<em>Objects and rules</em>’, select ‘ <em>Ticket</em> <em>Fields</em>’.</p><p>c. Click on ‘<em>Add Field</em>’ button and select ‘<em>Dropdown</em>’ as the field type.</p><p>d. Now, let’s configure the field. For the title, we will enter ‘Teams’. This will be the name for our custom field.</p><p>e. Under the ‘<em>Field values</em>’ section, add four values: ‘Team A’, ‘Team B’, ‘Team C’, and ‘Team D’. These represent the different teams tickets will be distributed to, and tags will be created automatically, but can be adapted if needed. <strong>Please note that we will use the tags created for these values when setting the JSON body.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/717/1*xu0Q49lGSe6YZdAaW4FHQg.png" /></figure><p><strong>STEP 2 — Creating the Webhook</strong></p><p>Next, we’ll create a webhook that will allow us to update tickets via API according to our requirements.</p><p>a. In the Admin Centre, navigate to ‘Apps and integrations’ and ‘Webhooks’</p><p>b. Click on ‘Create webhook’ and ‘Trigger or automation’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/859/1*u-rryRgSvLK1uNbhJ6nE1Q.png" /></figure><p>c. Now we will configure our Webhook:</p><ul><li>Add a name to the Webhook. We will name it “<strong>Update a ticket as ZD Admin</strong>”.</li><li>Add an endpoint for the Webhook (remember to add your company domain): <a href="https://mycompanyname.zendesk.com/api/v2/tickets/update_many.json?ids={{ticket.id}}">https://mycompany.zendesk.com/api/v2/tickets/update_many.json?ids={{ticket.id}}</a></li><li>Set the <strong>Request method</strong> as <strong>PUT </strong>and <strong>Request format </strong>as<strong> JSON</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/885/1*uTU8rogqd9CA6Dnm25Rt1g.png" /></figure><ul><li>Lastly, choose the <a href="https://support.zendesk.com/hc/en-us/articles/4408839108378-Creating-webhooks-to-interact-with-third-party-systems">Authentication method</a> and test the Webhook. We have created already our Webhook.</li></ul><p><strong>STEP 3 — Setting up the Trigger</strong></p><p>Finally, we’ll create the trigger that will call our Webhook, thus enabling proportional ticket distribution.</p><p>a. In “<em>Admin Centre</em>”, under triggers, click on “<em>Add trigger</em>”. First, define your conditions. These conditions determine when the trigger should activate. In our example, we will set the trigger to fire when the ticket is created only, but of course, more conditions can be added depending on your business rules.</p><p>b. Then, under ‘<em>Actions</em>’, select ‘<em>Notify active webhook</em>’ and choose the webhook you created in the previous step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/797/1*v1iGt84uin8uylJnupl5Jw.png" /></figure><p><strong>STEP 4 — Crafting the JSON Body: Scenario-based Examples</strong></p><p>The final piece of the puzzle lies in the <strong>JSON body</strong> of our webhook. This is where we’ll employ Liquid code to dictate the ticket distribution among our teams.</p><p><strong>IMPORTANT: Ignore the red error icon, as it’s a bug of Zendesk and it will not disappear.</strong></p><figure><img alt="Ignore the red error icon, as it is a Zendesk bug." src="https://cdn-images-1.medium.com/max/163/1*XpZLEsl957mkh45pMDyv_A.png" /></figure><p>Let’s explore three different scenarios:</p><blockquote>Scenario 1: Equal Distribution</blockquote><p>In this scenario, we aim for an equal distribution of tickets among all four teams. JSON Body would be something like this:</p><pre>{% assign randomizer = ticket.id | modulo:4 %}<br>{% case randomizer %}<br>{% when 0 %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_A&quot;]}}<br>{% when 1 %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_B&quot;]}}<br>{% when 2 %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_C&quot;]}}<br>{% when 3 %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_D&quot;]}}<br>{% endcase %}</pre><p>With this setup, <strong>each team will receive 25% of the tickets.</strong></p><p><strong><em>Please note that we are using the value tags of the values of our “Team” custom field and not the value name. Adding the tag will set the value in the custom field automatically.</em></strong></p><blockquote>Scenario 2: Unequal Distribution</blockquote><p>For cases where the workload needs to be distributed unevenly among<strong> teams, you can adjust the modulo and cases accordingly. For instance, if Team A should handle 50% of the tickets, and Teams B, C, and D should each handle approximately 16.67%,</strong> your JSON body would look like this:</p><pre>{% assign randomizer = ticket.id | modulo:6 %}<br>{% case randomizer %}<br>{% when 0 %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_A&quot;]}}<br>{% when 1 %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_A&quot;]}}<br>{% when 2 %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_B&quot;]}}<br>{% when 3 %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_C&quot;]}}<br>{% when 4 %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_D&quot;]}}<br>{% when 5 %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_D&quot;]}}<br>{% endcase %}</pre><blockquote>Scenario 3: Team-Based Prioritisation</blockquote><p>In this scenario, we have a small specialised team (Team D) that can only handle a limited number of tickets, while the rest are equally divided among Teams A, B, and C.</p><pre>{% assign randomizer = ticket.id | modulo:7 %}<br>{% case randomizer %}<br>{% when 0 %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_A&quot;]}}<br>{% when 1 %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_A&quot;]}}<br>{% when 2 %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_B&quot;]}}<br>{% when 3 %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_B&quot;]}}<br>{% when 4 %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_C&quot;]}}<br>{% when 5 %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_C&quot;]}}<br>{% else %}<br>{&quot;ticket&quot;: {&quot;additional_tags&quot;:[&quot;team_D&quot;]}}<br>{% endcase %}</pre><p>In this case, <strong>Teams A, B, and C each handle approximately 30% of the tickets, while Team D handles 10%.</strong></p><p>By modifying the JSON body to fit your needs, you can customise ticket distribution to almost any pattern.</p><p>Once we have choose a distribution that meets our business rules, we can create our trigger.</p><p><strong>STEP 5 — Exposing Tickets to Your Teams with Custom Field-Based Views</strong></p><p>Upon the successful creation of your custom field and the setup of your triggers, the next final step is exposing the proportionally distributed tickets to your respective teams. To achieve this, you will create dedicated views in Zendesk. The key condition to filter these views is your custom field, “Teams” with the respective team name (“Team A”, “Team B”, “Team C”, etc.) for each view. <strong>This will ensure that each view cleanly exposes only the tickets assigned to each corresponding team, thereby streamlining the ticket management process.</strong></p><p><strong>Conclusion</strong></p><p>Effective ticket distribution is key to managing customer support operations. With the versatility of Liquid code and the power of Zendesk triggers, you can customise your ticket distribution to fit your organisation’s needs. Don’t hesitate to experiment and find the configuration that suits your team best.</p><p>If you have found this guide helpful and crave more insights, f<strong>ollow me on Medium</strong>. I’ll be regularly sharing new tips, tricks, and in-depth guides to help you unlock the full potential of your Zendesk platform. Let’s continue optimising your customer support experience together!</p><p>Happy ticketing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbde81f7a16e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>