{"id":3184,"date":"2023-02-01T10:00:39","date_gmt":"2023-02-01T09:00:39","guid":{"rendered":"https:\/\/help.ino.cx\/?post_type=ht_kb&p=3184"},"modified":"2026-05-26T11:41:58","modified_gmt":"2026-05-26T09:41:58","slug":"distribution-groups","status":"publish","type":"ht_kb","link":"https:\/\/help.ino.cx\/index.php\/help-center\/distribution-groups\/","title":{"rendered":"Distribution groups – Set them up"},"content":{"rendered":"\n
\"Smart<\/figure>\n\n\n\n

[Reading time: 8 minutes<\/em>]<\/p>\n\n\n\n

Overview<\/h2>\n\n\n\n

The Distribution groups<\/strong> tab, located in the Queues<\/strong> module of the Maker, lets you bundle several distribution queues together and split incoming flows across them according to a configurable load (%).<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In practice, a distribution group is used to:<\/p>\n\n\n\n

    \n
  • Share the workload<\/strong> between several teams handling similar interactions (for example, two teams with different agents but processing the same type of customer requests).<\/li>\n\n\n\n
  • Apply a fixed weighting<\/strong> between queues (for example, 70% of interactions to queue A, 30% to queue B).<\/li>\n\n\n\n
  • Group several queues<\/strong> behind a single entry point that can be referenced from a Smart Routing \u2014 instead of duplicating routing branches.<\/li>\n<\/ul>\n\n\n\n

    Each queue inside a group is associated with a load<\/strong> between 0 and 100. The sum of all queue loads in a group must always be equal to 100<\/strong>.<\/p>\n\n\n\n

    Note<\/strong>: only incoming queues<\/strong> can be added to a distribution group. Outgoing queues are not eligible. The same queue can however be associated with several different distribution groups if needed.<\/em><\/p>\n\n\n\n

    When to use a distribution group<\/h2>\n\n\n\n

    A common question is: I can already define a weight and a charge on a queue, so what does a distribution group add?<\/em><\/p>\n\n\n\n

    The answer is that the two settings act at different stages<\/strong> of the interaction lifecycle.<\/p>\n\n\n\n

    Setting<\/th>Where it applies<\/th>What it controls<\/th><\/tr><\/thead>
    Weight<\/strong> and Charge<\/strong> on a queue<\/td>After the interaction has entered a queue<\/td>Priority of that queue against other queues handled by the same agent<\/strong>. It decides which queue the agent serves first when several queues are eligible.<\/td><\/tr>
    Load (%)<\/strong> in a distribution group<\/td>Before the interaction enters a queue, at the routing stage<\/td>How incoming interactions<\/strong> are split across the queues of the group. It decides which queue the interaction lands in.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Said differently:<\/p>\n\n\n\n

      \n
    • Without a group: 1 Smart Routing \u2192 1 queue<\/em>. The queue\u2019s weight and charge govern how it competes for an agent\u2019s attention.<\/li>\n\n\n\n
    • With a group: 1 Smart Routing \u2192 1 group \u2192 split into N queues according to the group\u2019s loads<\/em>. Then each queue keeps applying its own weight and charge to compete for agents.<\/li>\n<\/ul>\n\n\n\n

      The two stages are independent and complementary: the group decides the dispatch ratio at the entry point, the queue\u2019s own settings still drive the agent-side priority once an interaction has been placed in a queue.<\/p>\n\n\n\n

      Typical use cases for a distribution group:<\/p>\n\n\n\n

        \n
      • Load balancing between equivalent teams<\/strong> (same skills, same scope) without having to duplicate branches in the Smart Routing.<\/li>\n\n\n\n
      • Distribution between teams<\/strong> located on different sites or different time zones.<\/li>\n\n\n\n
      • A\/B testing<\/strong>: send 50% of incoming interactions to a new queue (new agents, new training) to compare the results.<\/li>\n\n\n\n
      • Gradual ramp-up<\/strong>: send 10% of traffic to a new queue, then 30%, then 70%, by simply adjusting the loads of the group.<\/li>\n<\/ul>\n\n\n\n

        Prerequisites<\/h2>\n\n\n\n

        To access and configure distribution groups, the user\u2019s role must include the appropriate rights on the Distribution queues<\/strong> entity. The same set of rights covers both queues and distribution groups:<\/p>\n\n\n\n

          \n
        • Read<\/strong> \u2013 view the list and details of distribution groups<\/li>\n\n\n\n
        • Create<\/strong> \u2013 create a new distribution group<\/li>\n\n\n\n
        • Modify<\/strong> \u2013 edit a group, add or remove queues, change loads, reset the counter<\/li>\n\n\n\n
        • Delete<\/strong> \u2013 delete a single distribution group or several at once<\/li>\n<\/ul>\n\n\n\n

          These permissions are managed in the Roles<\/strong> module of the Maker.<\/p>\n\n\n\n

          The queues to be associated with the group must already exist. They are created in the Queues<\/strong> tab of the same module.<\/p>\n\n\n\n

          1. Create a distribution group<\/h2>\n\n\n\n

          The Distribution groups list is accessed from the Maker, in the Queues<\/strong> module. At the top of the page, two horizontal tabs are displayed:<\/p>\n\n\n\n

            \n
          • Queues<\/strong> \u2013 the list of distribution queues<\/li>\n\n\n\n
          • Distribution groups<\/strong> \u2013 the list of distribution groups<\/li>\n<\/ul>\n\n\n\n

            To create a new group:<\/p>\n\n\n\n

              \n
            1. Open the Distribution groups<\/strong> tab.<\/li>\n\n\n\n
            2. Click the +<\/strong> button at the top right of the page.<\/li>\n\n\n\n
            3. Fill out the form:<\/li>\n<\/ol>\n\n\n\n
              Field<\/th>Required<\/th>Description<\/th><\/tr><\/thead>
              Name<\/strong><\/td>Yes<\/td>Display name of the group<\/td><\/tr>
              Reference<\/strong><\/td>Yes<\/td>Unique identifier code used to reference the group in your configurations and integrations<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                \n
              1. Click Save<\/strong>.<\/li>\n<\/ol>\n\n\n\n

                The new group appears in the list. At this stage, the group exists but does not yet contain any queue.<\/p>\n\n\n\n

                The list itself shows two columns \u2013 Name<\/strong> and Reference<\/strong>. A search bar at the top lets you find a group by its name.<\/p>\n\n\n\n

                \"\"<\/figure>\n\n\n\n

                2. Add queues to a group<\/h2>\n\n\n\n

                Click the group\u2019s name in the list to open its details<\/strong> page. The page lands directly on the Distribution queues<\/strong> tab, which lists every queue currently associated with the group.<\/p>\n\n\n\n

                To associate queues with the group:<\/p>\n\n\n\n

                  \n
                1. Click the +<\/strong> button at the top right.<\/li>\n\n\n\n
                2. In the modal, select one or more queues from the list of available queues.<\/li>\n\n\n\n
                3. Click Add<\/strong>.<\/li>\n<\/ol>\n\n\n\n

                  The selected queues are added to the group with a default load of 0<\/strong>, except for the very first queue<\/strong> added to an empty group, which is automatically set to 100<\/strong> so that the group is immediately valid (sum = 100). When you add more queues, you will need to redistribute the loads in edit mode (see section 3).<\/p>\n\n\n\n

                  Note<\/strong>: the selection list only shows incoming queues<\/strong> that are not yet linked to this group. The same queue may be associated with several distribution groups in parallel, which is useful for example to dispatch the same queue from several Smart Routings with different load ratios.<\/em><\/p>\n\n\n\n

                  3. Manage queue loads<\/h2>\n\n\n\n

                  The Load<\/strong> column displays the percentage of interactions distributed to each queue. As soon as you have added more than one queue, you will need to redistribute the loads so that the sum stays equal to 100.<\/p>\n\n\n\n

                  \"\"<\/figure>\n\n\n\n

                  3.1. Enable edit mode<\/h3>\n\n\n\n

                  To edit the loads, click the Edit mode<\/strong> button at the top right of the table. The Load column then becomes editable for each queue.<\/p>\n\n\n\n

                  \"\"<\/figure>\n\n\n\n

                  3.2. Set the loads<\/h3>\n\n\n\n

                  For each queue, enter a value between 0 and 100<\/strong>.<\/p>\n\n\n\n

                    \n
                  • The sum of all queue loads in the group must be equal to 100<\/strong>. If the total is not 100, the form displays an error and the changes cannot be saved.<\/li>\n\n\n\n
                  • A load value must be between 0 and 100<\/strong>. Any value outside this range is rejected.<\/li>\n<\/ul>\n\n\n\n

                    3.3. Save or cancel<\/h3>\n\n\n\n
                      \n
                    • Click Save<\/strong> to apply the new loads.<\/li>\n\n\n\n
                    • Click Cancel<\/strong> to discard the changes and exit edit mode.<\/li>\n<\/ul>\n\n\n\n

                      Once saved, the Load column displays the new percentage as a progress bar.<\/p>\n\n\n\n

                      4. How loads are applied and reset<\/h2>\n\n\n\n

                      The configured loads (%) are applied on average over time<\/strong>.<\/p>\n\n\n\n

                      You may want to reset this mechanism \u2014 for example after changing the loads, after a long inactivity period, or to start a new measurement campaign on a clean state. To do so:<\/p>\n\n\n\n

                        \n
                      1. From the group\u2019s Distribution queues<\/strong> tab, click the settings<\/strong> dropdown at the top right.<\/li>\n\n\n\n
                      2. Select Reset the queue load counter<\/strong>.<\/li>\n\n\n\n
                      3. Confirm the action.<\/li>\n<\/ol>\n\n\n\n

                        The reset only clears the internal distribution counter for all queues of the group at once \u2014 the configured loads (%) are not changed. The next interactions will be dispatched as if the group had just been created.<\/p>\n\n\n\n

                        \"\"<\/figure>\n\n\n\n

                        Once a queue has been chosen by the group\u2019s algorithm, the interaction is placed in that queue and follows the queue\u2019s own distribution rules<\/strong> (weight, charge mode, agent profiles, working hours, etc.). The group\u2019s loads no longer apply at this stage.<\/p>\n\n\n\n

                        5. Edit, duplicate or delete a group<\/h2>\n\n\n\n

                        From the Distribution groups<\/strong> list, each row provides the following actions:<\/p>\n\n\n\n

                        Action<\/th>Description<\/th><\/tr><\/thead>
                        Edit<\/strong><\/td>Modify the Name and Reference of the group.<\/td><\/tr>
                        Duplicate<\/strong><\/td>Create a copy of the group, including its associated queues and their configured loads. The duplicated group keeps the same queues and load values; only the Name and Reference must be updated.<\/td><\/tr>
                        Delete<\/strong><\/td>Remove the group. The associated queues are not deleted \u2014 they simply become available again for another group.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

                        Several groups can be deleted at once by selecting them in the list and using the bulk delete<\/strong> action.<\/p>\n\n\n\n

                        To remove a queue<\/strong> from a group, click the delete icon on its row in the group\u2019s Distribution queues<\/strong> tab. A queue can only be removed if its load is equal to 0<\/strong>. Set the load to 0 in edit mode and save before removing the queue, so that the loads of the remaining queues still sum to 100.<\/p>\n\n\n\n

                        Setting a queue\u2019s load to 0<\/strong> without removing it is also a way to temporarily deactivate<\/strong> it: the queue stays linked to the group but no longer receives traffic from it, and its configuration is preserved if you decide to reactivate it later.<\/p>\n\n\n\n

                        6. Use a distribution group in a Smart Routing<\/h2>\n\n\n\n

                        Once configured, a distribution group can be used as a destination in a Smart Routing<\/strong> for all three flow types \u2014 voice<\/strong>, email<\/strong> and messaging<\/strong> \u2014 to dispatch interactions across the queues of the group according to the configured loads.<\/p>\n\n\n\n

                        In the Smart Routing editor:<\/p>\n\n\n\n

                          \n
                        1. Add a Distribution to queue<\/strong> action in the routing tree.<\/li>\n\n\n\n
                        2. In the Distribution to<\/strong> field, select Distribution group<\/strong> (instead of Queue<\/em>).<\/li>\n\n\n\n
                        3. Pick the distribution group from the list, or specify its reference.<\/li>\n<\/ol>\n\n\n\n

                          From that point onwards, every interaction reaching this branch of the Smart Routing is dispatched into one of the group\u2019s queues according to the configured loads.<\/p>\n\n\n\n

                          See the Smart Routings<\/strong> articles of the help center for the full configuration of routing trees and distribution actions.<\/p>\n","protected":false},"excerpt":{"rendered":"

                          Distribution groups allow you to group and prioritize your queues and then establish your transfer rules or use it in a Smart routing. In this article we will see how to create and configure them according to your needs.<\/p>\n","protected":false},"author":3,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[146,105],"ht-kb-tag":[147,131],"class_list":["post-3184","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-as-an-administrator","ht_kb_category-using-ino","ht_kb_tag-admin","ht_kb_tag-maker"],"_links":{"self":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/3184","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/comments?post=3184"}],"version-history":[{"count":4,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/3184\/revisions"}],"predecessor-version":[{"id":6572,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/3184\/revisions\/6572"}],"wp:attachment":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/media?parent=3184"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-category?post=3184"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-tag?post=3184"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}